WebClient most common installation problems
WebClient is not functioning properly. Troubleshooting steps are required.
Below are some of the more common problems that Technical Support runs into when troubleshooting a WebClient installation.
Microsoft DCOM settings
This is the most common problem that TSD runs into. There are two areas that these settings need to be set in are, “Access Permissions” and “Launch and Activation permissions”. Incorrect DCom settings in WebClient will cause many different problems. It could cause problems with logging into the system, opening graphics, seeing the Active Alarm view, etc… The users that should be in there are below for Windows 2000 IIS and Windows XP IIS servers:
- ComputerName\IUSR_ComputerName (Internet guest account)
- ComputerName\IWAM_ComputerName (Launch IIS process account)
- ComputerName\ASPNET (ASP.NET)
Additionally for Windows 2003 IIS servers this additional user is needed:
To help pinpoint the DCOM permission that is not set properly, consult the steps at Identify which DCOM permission are causing DCOM errors when trying to use WebClient.
Microsoft .Net Frame work Zone Permissions
This is another one of the more common problems in WebClient installs. Not setting the .Net Zone permissions correctly will cause problems with opening schedules in the WebClient browser machines. The .Net zone permissions has to be set on each client browser. See the section in the WebClient install guide on setting the .Net Zone permissions.
Microsoft .Net Framework is installed before the IIS is installed
This is becoming more common with Windows 2003 server installs. If .Net is installed prior to IIS you will see problems with logging into the system, editors may not work, schedules will not be able to be opened. If there is any doubt to whether or not .Net was install before the IIS then open a Windows command prompt and run the below commands.
- For Windows 2000 Professional it is:
- For Windows XP Professional, Windows Server 2003 it is:
Microsoft .Net 2.0
This is not supported until V1.74 and will cause problems with WebClient. You will see problems with reports, schedules on earlier versions. SQL Authentication methods with WebClient The only authentication method for SQL server that WebClient supports is SQL Server and Windows. Due to the methods we use to access data in the SQL database with WebClient the authentication must be set this way.
Internet Information Server Secure Sockets Layer (IIS SSL)
Currently using SSL with WebClient is not supported in versions prior to V1.74. Remote installs of WebClient Due to underlying Microsoft Security a WebClient cannot be installed through any kind of remote terminal services, Windows or others. If the system is installed through remote services there will be security problems with accessing WebClient. The correction to these problems is to be directly on the WebClient / IIS machine and uninstall all the WebClient apps, Microsoft .Net, and Microsoft IIS then re-install the applications per our instructions while directly on the WebClient machine.
Remote reboots of a WebClient IIS server
If you use a remote terminal service and reboot and log on to an IIS server running WebClient you will run into problems with logging into WebClient.
Multiple Network cards in the IIS server
Using multiple network interface cards in an IIS server is not supported. Doing this will cause problems with opening graphics through WebClient.
Installation of files on the Client browsing machines
The first time WebClient is accessed through a browser, either in new installs or upgrades, files need to be installed on that client browser machine. You will need to be logged in with a Windows user that has the permissions to install software. Install of WebClient on the IIS computer while virus scan software is running. Make sure that when installing WebClient, either new installs or upgrades, that any virus scan software is disabled. In some instances virus scan software has caused problems with WebClient installs or upgrades.
"&" characters in names of objects
Ampersands are special characters in web browsing and should not be used in anything in Continuum that the WebClient browser will have access to. Some of the problems that have been seen are alarms not showing up in the Active Alarm view and not being able to add areas to personnel objects.
Setting up WebClient graphics
Once WebClient is installed on the IIS server you need to make sure you open CyberStation Pinpoint and set the “Web Locations” for your graphics sharing. If you do not set this you will not be able to access graphics through WebClient. When these are set incorrectly you will see a red “X” next to the path.
Ports used in WebClient
Until V1.74 we only support the use of Port 80 in WebClient. CyberStation on the IIS WebClient server. In order for WebClient to function properly the CyberStation that is installed as part of the WebClient install on the IIS server must be running. You do not need to be logged on to the CyberStation it just needs to be running.
WebClient graphics and firewalls
Prior to 1.73 there were some special installation considerations when dealing with customers that had browsing machines both inside and outside a firewall. In the 1.73 WebClient there is no special installation/configuration that needs to be done. The system can be set up as if all the browsers are on the local network.
Renaming or changing the Domain of the IIS Server after IIS is installed
Renaming or changing the Domain that the IIS server was initially installed with will cause problems with IIS which in turn will cause problems with WebClient. If this has to be done then you will need to uninstall the applications before the change then re-install the applications.
Directory Browsing setting for WebClient graphics
In some instances where the Windows security on the IIS server is restrictive you will need to add “Directory Browsing” to the NewGraphicsFiles share in the web site configuration on the IIS Server.
Using underscores or hyphens in the name of the IIS Server
This will cause problems with the operation of WebClient because those characters are special characters in the application.