Kbase 19258: Basic Troubleshooting for Webspeed on NT 2.x / 3.x
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/12/2008 |
|
Status: Verified
GOAL:
Troubleshooting Guide on WebSpeed Issues
FACT(s) (Environment):
WebSpeed 2.x
WebSpeed 3.x
Windows NT 32 Intel
FIX:
Use this guide as a starting point to debug WebSpeed Broker start issues or when there are problems with the SpeedStart Script. The information applies to Microsoft IIS.
1. Stop and restart your WebServer after installation?
2. Is the WebSpeed broker connected to a database, if so, then start up the broker with no database connection
3. Try to start the default broker, wsbroker1, setup when WebSpeed is installed. This broker has all the default settings, and no database connection.
If the default broker does not exist, create a TEST broker with 1 agent. Do not alter the TEST broker's default configuration. If the TEST broker/agent start with no problem, change the field (entry) that has been changed on broker originall being started.
4. Perform the SpeedScript Test using ?WSMAdmin. Make sure the WebSpeed broker is set to development and the messenger has "Allow msgncmd" allowed.
5. Remember to change host-name to your host machine's name, SampleSrvc to the name of your WebSpeed service and also Webspeed-Messenger to cgiip.exe or wsisa.dll.
6. During the installation, was the option to "create virtual directory" within the Web Server's Script and Document Root directories? If so, check the web server properties and see that these virtual directories are present.
There should be a /scripts that points to the scripts directory of your web server (ex. c:\inetpub\scripts) and a /webpseed that points to the WebSpeed files (ex. c:\program files\webspeed\webspeed).
-OR-
Was the choice "copy the static WebSpeed files into the Web server's root directory" made? If so, check for the existence of these files (ex. c:\inetpub\wwwroot\webspeed). If these files are not there, they can be copied from the WebSpeed installation area to this root directory (ex. copy c:\program files\webspeed\webspeed to c:\inetpub\wwwroot. You will now have c:\inetpub\wwwroot\webspeed).
7. If not using the WebSpeed folder within the Progress Explorer, verify the PATH of the Progress DLC installation being used.
8. If you are using a DOMAIN\USERNAME, verify that the user has the correct privileges (See kbase 19244). Try to use another user
9. Verify that the port is open via the NetStat command
10. Verify log files, broker and server logs
11. Increase loggining for more detailed information