 08-11-2003, 12:00 AM
|
webadmin@datadynamics.com
Joined on 12-12-2005
Posts 0
|
Crash IIS 4.0 server when 2 PDFs are exported at same time
|
|
|
|
|
Originally Posted By: Anonymous Rat<rockoisnot@hotmail.com>
We have uncovered a peculiar problem with AR1 sp2.
We added code to create log files to the same folder where the .pdf files
are being exported and discovered that when 2 .pdf files are exported at the
exact same time the IIS hangs.
We added code to create the .pdf export with the following naming
convention:
userLanID_date_timestamp.pdf [eg.: gracem00_20030811_084416.PDF]
Today, after IIS became hosed we found 2 files:
HollaD00_20030811_073414.PDF
eidenj00_20030811_073414.PDF
which were the last 2 files created before the IIS hung. This tell me that
at 7:34am 2 files were exported at the exact same time.
We looked at previous days when we had IIS problems and found similar
pairings around the same time the application log on the server detailed a
problem.
When I tried to log in at 7:35am I received a COM error:
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object
/Default.asp, line 41
and no one could access the server, not even the NT admin. We had to reboot.
I looked at the application log after the server was rebooted and found the
following errors:
Failed on creation from object context: CoCreateInstance (ProgId:
DailySalesReport.clsAimDailySalesItems) (CLSID:
{A5072E66-8B53-4568-9341-7776E26C4251}) (Microsoft Transaction Server
Internals Information: File: i:\viper\src\runtime\context\ccontext.cpp,
Line: 1347)
We are not using MTS but I believe IIS uses it to manage resources and
connections.
We've been having nightmares with AR1 since we upgraded our SQL servers to
W2k and SQL2k but kept our web servers at NT4.
Any ideas on how to keep IIS from crashing?
Any suggestions would be appreciated.
FYI: we've been monitoring this newsgroup since March and have implemented
all of the suggestions for error handling and debugging from past postings
but the logs show no errors from the AR components.
Also, we have been testing service pack 4 for AR but have run into a
different set of problems which we are working to resolve.
|
|
|
|
|
Report
|
|
|
|