A Web Client checklist for v7.5.2 that Sage Support uses frequently

[#1]

Have you ever thought, "What are the easy things that I should check?" when troubleshooting a v7.5.2 Web Installation?  Perhaps this will help.  These are the most common things a Support Analyst will check when facing a troublesome Web Client installation.  This of course is not an all-encompassing or complete list, but it certainely helps us in not "skipping the simple stuff" when troubleshooting a Web Client issue:

7.5.2 Web checklist

ü  Install SQL Native Client 2005 or 2008 depending on SQL server version (Installation of web host will fail if this is not installed)

ü  Check identity on application pool and make sure it matches the user that is set as the “anonymous access” user in the directory security tab of virtual directory. Also, make sure the virtual directory\website is assigned to the correct application pool

ü  Default.aspx is added to web client virtual directory ‘doc tab’

ü  Webdll user is part of local ‘Administrators’ and ‘IIS_WPG’ security groups

ü  Local Security settings for Webdll are set…

o   Allow log on locally

o   Log on as a service

o   Access this computer from the network

o   Per the documentation ‘act as a part of the operating system’ is optional for web host installs

ü  Check SLX version of application architect and other SLX applications that are installed. Also, check systeminfo.version for the DB version and make sure the appropriate bundles have been applied

ü  Create a new project workspace in the application architect and use the out of the box 7.5.x project backup to test build\deployment issues

ü  Check to make sure virtual directory ‘Home Directory’ is set to the folder you are deploying the website to

ü  In each user’s browser, make the Web site a Trusted site with the Default Level of security (Low)

ü  In multi web host environments ensure that the secondary Web Hosts have network access to the primary Web Host so that the necessary HTML and JavaScript files are available

IIS 7

ü  ASP.NET is installed and enabled

o   IIS7 this is done through the ‘Programs’ area under ‘Turn Windows Features on or off’

ü  IIS7 – Under the Application pool’s basic settings ‘Managed pipeline mode’ is set to ‘Classic’

ü  IIS6 compatibility mode installed. The install is done from the Control Panel > Programs and Features > Windows Components Area

ü  Firewall has either been configured to allow SLX ports to be open or disabled (for testing purposes you can disable the windows firewall from Control Panel > System and Security > Windows Firewall) See the chart below:

Server	Port	Open on
Database Server	1433 (MS SQL)	Inside firewall
Web Host	1706 (OLEDB)	Inside firewall
	1025 and/or other higher (HTTP portconfigured for each Web site)	Outside firewall
Web Reporting Server	1706 (OLEDB)	Inside firewall
	1025 or other higher (port configured for Web Reporting)	Outside firewall
Synchronization Server*(Shared Documents &Library folders)	NetBIOS138 (UDP)139 (TCP) If using Domain Name Service (DNS), also open these:135 (TCP/UDP - Remote Procedure Calls)137 (TCP - DNS)445 (TCP/UDP - DS)	Inside firewall

 *The Documents and Library folders may be located on another machine, such as the Administrative Workstation (for example, if your organization does not use synchronization). Be sure to open the ports on the correct machine.