Kbase 19347: Webspeed 3 - TCP configuration, why cgiip might not work
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/02/2002 |
|
Webspeed 3 - TCP configuration, why cgiip might not work
Can not run cgiip from unix or NT - local or in distributed configuration.
Possible errors reported by the web server are:
Messenger failed to communicate with the name server at localhost:port
The web server has encountered an internal error that prevents it from fulfilling your request.
The messenger failed to generate an appropriate response, etc.
You may also receive a core file caused by the cgiip executable in the cgi-bin or scripts directory of your web server.
You have verified the following:
The web server is using the cgiip messenger to generate the appropriate html output.
The admin service, name server, broker, and agents are running.
You are using the host names in the ubroker.properties file and not the IP addresses.
If in a distributed configuration, you have verified your firewall is allowing the communication between the systems and checked the ports they are using.
If you are using Internet Information Server, you find the wsisa.dll works properly but cgiip.exe fails.
Ensure the host name in the TCP configuration is the same as the computer name. It is possible to setup a different host name other than the computer name for your system. If you do, you may encounter this problem.
Verify that the transaction servers hostname is present within the HOST file of the webserver.
Kbase 19347