Back

Topic

[KB24]Troubleshooting WebVue (Previous version)

Tags: Webvue

14 years ago
By RM
Options
Print
Applies to:

WebVue


Summary:

A summary of known problems and solutions for running WebVue. Note that this article has been superseded by KB605 which can be viewed by clicking here.


Details:

Basic tests before starting WebVue

  1. Verify you have no error report when you install Pcvue server (WSE installation error due to bad Xp/Vista rights for example)
  2. Be sure IIS is well installed
    1. Type http://localhost : You must obtain default IIS page. Otherwise Web default site is not started.
  3. Ensure that the Web service WebPropertyServer is set to framework 2.0. (ASPNET panel of IIS conf)
  4. Type http://localhost/webpropertyserver/webpropertyserver.asmx
    1. You must obtain the web service pages with 2 invocation methods (Set and Get methods)
  5. Check that there is no other server using the http port 80.
    1. You can use wireshark(a freeware) to watch exchanged messages on tcp port 80.
    2. For test purpose, you can also change default 80 tcp port in IIS conf. For example, if you choose 8081 tcp port, when you test url type http:localhost:8081
  6. Verify you have a compatible Java runtime. (To be 100% sure you can install the latest as Java always has backwards compatibility)
  7. Purge the cache of Java runtime and temporary internet files.
  8. If you are unsure about the original sequence of installation, reinstall .Net for IIS (aspnet_regiis.exe –i) in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\
  9. In there was a previous PcVue installation change virtual directories path to map the new server path.
    1. You can also manually delete the virtual path (In IIS conf: classes, webpropertyserver) and use the PcVue WebVue Server configuration to remap the virtual directories.

Connection failure on some networks using a firewall

On some networks with a firewall, reading of IP addresses and obtaining the client hostname fails causing WebVue to fail.

To solve this problem a property (IpQueryLevel) has been added to WEBVUE.DAT file which allows WebVue to be configured so that it stops trying to read the IP address.

By Default, IpQueryLevel = 7. This is a combination of these three options.

  • – IP_APPLETQUERY=1 – Read IP of the client station by the applet
  • – IP_HOSTQUERY=2 – PcVue tries to obtain the name of the host from IP_APPLETQUERY
  • – IP_HOSTNAMEQUERY=4 – Web service tries to obtain the IP of the client.

To disable these requests you can set the IpQueryLevel to 0.


Security issue under Windows 2003 Server

The symptom of this problem is a “Server not responding” message box when attempting to connect to WebVue. This problem occurs because the Deny access to this computer from the network policy setting is applied to the Guests group on the server where WebVue is installed.

To confirm that this is the problem first try to access the URL using the IP address:

  • – http://localhost => you’ll obtain the IIS default page
  • – http://127.0.0.1 => you’ll have a system dialog box asking you for user name and password.

To work around this problem use one of the following methods.

First method:

  1. In the Local Security Settings window, expand the Local Policies folder.
  2. Click User Rights Assignment.
  3. Select Deny access to this computer from the network and remove Guest group and the Anonymous Logon account

Second method:

  1. Remove the IUSR_ComputerName  account from the Guests group and add it to the Local Users group

Connection impossible due to Windows security configuration

On some PCs with specific security configuration you get a message similar to the following when trying to connect to WebVue:

<<Server Application Unavailable. The web application you are attempting to access on this web server is currently unavailable. Please hit the Refresh button in your web browser to retry your request.

An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error.>>

Solution:

Add the users IUSR_[Hostname], IWAN_[Hostname] and ASPNET to the Administrator group of the PC.

Connection impossible due to Applicom initialization and appusr.ini

WebVue and WebServices do not work if PcVue is launched by appusr.ini file after Applicom initialization.

Solution:

To start PcVue from Applicom use WINEXEC in appusr.ini to execute a batch file located in the Bin directory of PcVue.

For example: WINEXEC “C:\Program Files\ARC Informatique\PcVue 8.10\bin\start.bat”

In the file “start.bat” in the PcVue Bin directory add the following 3 command lines.

  • cd\
  • cd “C:\Program Files\ARC Informatique\PcVue 8.10\bin”
  • sv32.exe -s

If all else fails

You have checked everything and still WebVue doesn’t work and you are still getting the “Server not responding” message.

Solution:

You must unitsall everything associated with PcVue and WebVue and start from scratch.

  1. Uninstall all versions of PcVue and all associated third party components that were installed as part of the PcVue instalation process. (Sentinel, WSToolkit, WSTPortal, OPC Core Components…)
  2. Uninstall all versions of of Microsoft .NET Framework.
  3. Uninstall IIS.
  4. Reboot the machine.
  5. Install IIS using an official Windows distribution. Do not use a distribition supplied by the PC manufactuere because sometimes their IIS components are not correct or complete. Don’t forget to select the Frontpage 2000 server extension.
  6. Then install PcVue. It should work correctly.

Created on: 17 Sep 2010 Last update: 04 Sep 2024