webspeed install
- Thread starter richs
- Start date
Rich-
The following Progress KB entry should help you out: http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/kbase3.w?Sol_Id=17298
Note the entry says may problems associated with this error are problems with WebSpeed 2.0, and an upgrade to 2.1 (or even better to 3.0) may fix the problem.
<BLOCKQUOTE><font size="1" face="Arial, Verdana">quote:</font><HR>
The following error
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805)
means the WebSpeed Messenger was unable to connect to an agent.
This may be caused by several reasons, including agents dying or
the WebSpeed broker not running.
The trouble shooting process should include these steps:
1) check to make sure the WebSpeed broker is running
* in UNIX, use the ps command and grep for _wtb or the wtbman -i
broker-name -q script
* in NT, use the task manager looking for _wtb.exe or use the
configuration utility
2) check to make sure agents are available
* in UNIX, use the ps command and grep for _wta or the wtbman -i
broker-name -q script
* in NT, use the task manager looking for _wta.exe or use the
configuration utility and check the status tab and show details
button
3) check the "broker-name_errs.log" for errors
* in here you may see errors like
WTB: Received a SIGCHLD from a child process. The dying
process PID=xxx. ( 5743 ). ***[this means the agent died]***
* look for other errors like
Your license for <product name> has expired. (4782)
Unable to find server <name> with protocol TCP in file
SERVICES or SERVICES not found in expected location (5192)
4) check to make sure the messenger is configured correctly
* in UNIX, check the messneger, be sure the following variables are
set correctly DLC, PROMSGS, PROCFG, and WEBSPEEDCNF
5) If you cannot get your agents to spawn correctly, suggest starting
them with just the default parameters
-p web/objects/web-disp.p -cpstream iso8859-1 -weblogerror
if the agents starts now, start trouble shooting the other parameters
on the agent.
6) Another thing to try is to start the _wta on UNIX or the _wta.exe
on NT. This will bring up a progress procedure editor. Now try to
connect to the database. Any errors will display immediately. Fix
those problems. Once you can connect cleanly to the database use the
connection parameters that worked to connect to the database in the
webspeed.cnf file or the startup parameter line in the Configuration
Utility.
***NOTE***if you are still on WebSpeed 2.0, upgrade to 2.1 for some
fixes to problems associated with this error.
<HR></BLOCKQUOTE>
The following Progress KB entry should help you out: http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/kbase3.w?Sol_Id=17298
Note the entry says may problems associated with this error are problems with WebSpeed 2.0, and an upgrade to 2.1 (or even better to 3.0) may fix the problem.
<BLOCKQUOTE><font size="1" face="Arial, Verdana">quote:</font><HR>
The following error
Msngr: Failure sending WEB_CGIIP_GET_PROG message. (5805)
means the WebSpeed Messenger was unable to connect to an agent.
This may be caused by several reasons, including agents dying or
the WebSpeed broker not running.
The trouble shooting process should include these steps:
1) check to make sure the WebSpeed broker is running
* in UNIX, use the ps command and grep for _wtb or the wtbman -i
broker-name -q script
* in NT, use the task manager looking for _wtb.exe or use the
configuration utility
2) check to make sure agents are available
* in UNIX, use the ps command and grep for _wta or the wtbman -i
broker-name -q script
* in NT, use the task manager looking for _wta.exe or use the
configuration utility and check the status tab and show details
button
3) check the "broker-name_errs.log" for errors
* in here you may see errors like
WTB: Received a SIGCHLD from a child process. The dying
process PID=xxx. ( 5743 ). ***[this means the agent died]***
* look for other errors like
Your license for <product name> has expired. (4782)
Unable to find server <name> with protocol TCP in file
SERVICES or SERVICES not found in expected location (5192)
4) check to make sure the messenger is configured correctly
* in UNIX, check the messneger, be sure the following variables are
set correctly DLC, PROMSGS, PROCFG, and WEBSPEEDCNF
5) If you cannot get your agents to spawn correctly, suggest starting
them with just the default parameters
-p web/objects/web-disp.p -cpstream iso8859-1 -weblogerror
if the agents starts now, start trouble shooting the other parameters
on the agent.
6) Another thing to try is to start the _wta on UNIX or the _wta.exe
on NT. This will bring up a progress procedure editor. Now try to
connect to the database. Any errors will display immediately. Fix
those problems. Once you can connect cleanly to the database use the
connection parameters that worked to connect to the database in the
webspeed.cnf file or the startup parameter line in the Configuration
Utility.
***NOTE***if you are still on WebSpeed 2.0, upgrade to 2.1 for some
fixes to problems associated with this error.
<HR></BLOCKQUOTE>
Similar threads
