Title: 502 error occurred in IIS 4.0 log
It takes less than 5 seconds to run the script for all except those mysterious users who call the script and it will not finish until timeout( I set the timeout to 20 minutes and no luck).
The script query database and print the news items on page, relatively simple. Either we or our ISP window experts failed to duplicate the problem.
 
Thanks.
 
-----Original Message-----
From: Peter Guzis [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 5:50 PM
To: Sun, Eric
Subject: RE: 502 error occurred in IIS 4.0 log

If you indeed using NT 4.0 Workstation, as opposed to NT 4.0 Server, the answer from Ward Vuillemot is likely the correct one.  The question, then, is what your scripts are doing that is taking so long.
 

Peter Guzis
Web Administrator, Sr.
ENCAD, Inc.
- A Kodak Company
email: [EMAIL PROTECTED]
www.encad.com

-----Original Message-----
From: Sun, Eric [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 2:45 PM
To: Peter Guzis
Subject: RE: 502 error occurred in IIS 4.0 log

Sorry. The database is open in shared mode.
 
Thanks.
Eric
-----Original Message-----
From: Peter Guzis [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 3:52 PM
To: [EMAIL PROTECTED]
Subject: RE: 502 error occurred in IIS 4.0 log

How are you running your scripts?  (CGI, PerlIS.dll, etc.)  Is your Access database configuration making use of the single-user option?  Please provide some source code and maybe one of us can help.
 

Peter Guzis
Web Administrator, Sr.
ENCAD, Inc.
- A Kodak Company
email: [EMAIL PROTECTED]
www.encad.com

-----Original Message-----
From: Sun, Eric [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: 502 error occurred in IIS 4.0 log

Hi,
We are running IIS 4.0 Win NT 4.0 box with Perl 5.6 building 633, connect to Access data file using ODBC.
The script is too large so I split it into several smaller files and "require" used in the main script file.

When a few clients connect to our web server, 502 error occurs. More than 10 instance of perl.exe sit in the memory and http and ftp service is not accepting any request until the cgi timeout(about 10 minutes).

We tried to duplicate the error but failed. Initially our ISP blamed Perl script. When I request them to duplicate the error and they failed also. Our ISP contacted Microsoft for trouble shooting and got back to us with this:

MS has verified all possible areas of IIS settings that would cause the timeout issue. At this time no other variables are found and can be configured on IIS to prevent the timeout issue. MS has analyzed and reviewed the provided IIS logs and Perfmon files.

Please contact the Perl software vendor for any assistances or work with the particular remote users to troubleshoot the issues since only those particular users could duplicate the issue.

It's mystery to me why the error only happened to 4(I mean from 4 IP addresses) of them. It has been a while since the problem occurred.

Any body had this kind of problem?

Thank you very much.

Eric
 



The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer.
Thank you,
Standard & Poor's

Reply via email to