Cgi Error after update of WS2003...

ClayGoss

Member
I have Progress 9.1c27 on Windows 2003 R2 with WebSpeed apps that use the cgiip.exe. Over the weekend, I updated Windows and these web scripts stopped. I can replace cgiip.exe in the call with wsisa.dll, and they work.

Stopping and starting IIS, the WebSpeed agent, the Progress NameServer agent makes no change.

Restarting the machine will allow the script with cgiip.exe to work for a minute or two - but then it goes back to giving the following error:

The specified CGI application misbehaved by not returning a complete set of HTTP headers.

Any leads much appreciated.
 

ClayGoss

Member
Yes, unknown cgi applications are allowed. Remember, this WAS working, but stopped after a re-boot after Windows updates.

I have installed WebSpeed on another server and got things working, but I need to resolve this so I can switch back.
 

ClayGoss

Member
Yes, cgiip.exe is executable - that would be a logical thing to check. Funny thing is that if I use wsisa.dll, the script runs - but changing to that would mean a whole bunch of user links would break - not a pretty picture.
 

ClayGoss

Member
Boy, I wish there was - might give a body a lead! The only stuff in there of any negitive nature is some fussing about a fax driver for an RDC connection and a W32Time warning. Otherwise, squeeky clean.
 
Sorry to ask the obvious, but presumably there's been no firewall changes?

What happens when you disable any firewalls affected by the updates?
 
Grasping at straws here...

There's a KB entry for multiple versions of messenger listed against your OS, but I suspect it's a red herring, because I don't see why OS should be relavent, and your update therefore should not have made a difference.

KB P73117
Title: "CGI application misbehaved & Error Processing commands errors when two version of the messengers are installed"

http://tinyurl.com/mz6dr


 

ClayGoss

Member
I have not found an answer to this problem. I am currently running WebSpeed from our "sand-box" machine. I have determined this problem has nothing to do with Windows updates as the same updates are applied to this "sand-box" machine, and it still works!

If I reboot the problem box, webspeed works for some period of time (less than 30 minutes and greater than 10 minutes) and I find this peculiar, and perhaps therein is a lead. What if something eventially starts on this box that uses the port(s) webspeed is trying to use?

I have done some experimenting in this regard, but have not found a solution yet.
 

Casper

ProgressTalk.com Moderator
Staff member
What if something eventially starts on this box that uses the port(s) webspeed is trying to use?

I have done some experimenting in this regard, but have not found a solution yet.

You should know which ports are used by which programs.

But anyway, I don't think that's the problem. Since you haven't got a firewall between the messenger and the agents (are they on the same machine as the database?) I assume you haven't changed the port range which are default assigned. (agent 3203-3502). The broker runs at a single port, so that can't be an issue (it starts or it doesn't start).

The nameserver uses default the whole range of UDP respons ports).

The messenger must be able to talk to the nameserver, broker and agent respectively.

If you do a verify config at the moment the error occurs does it go wrong and where does it go wrong?

Messenger:
Code:
[URL]http://host-name/scripts/cgiip.exe?VerifyConfig&Level=1[/URL]


Broker:
Code:
[URL]http://host-name/scripts/cgiip.exe?VerifyConfig&Level=2[/URL]

Roudtrip:
Code:
[URL]http://host-name/scripts/cgiip.exe/ping[/URL]


Further:
Does every page returned give this error? ("The specified CGI application misbehaved by not returning a complete set of HTTP headers")


Did you try looking at Lee Curzon's solution?

Regards,

Casper.
 

ClayGoss

Member
Casper wrote:
>Does every page returned give this error? ("The specified CGI application misbehaved by not returning a complete set of HTTP headers")

Yes, including the two VerifyConfig and Ping command you suggested.

>Did you try looking at Lee Curzon's solution?

Yes, there is only one messanger.

If replacing cgiip.exe with wsisa.dll for my scripts makes it all work, then does that mean the messenger is able to talk to the nameserver, broker and agent respectively?
 

Casper

ProgressTalk.com Moderator
Staff member
Nothing in the IIS log files? ("C:\windows\system32\Logfiles")

There was an issue with IIS 4.0 and IIS 5.0: KB 92659: http://tinyurl.com/ofu7t

Are you absolutely sure you haven't got MS firewall client installed on the machine?

KB P46902: http://tinyurl.com/hjsre

Is the windows2003 machine just webserver or also database server?
Anf if it's just acting as webserver are the agents running on the windows machine or on the database server?


Casper.
 
Top