ASPDBPro - ISSUE (URGENT)
Hi Frank,
Our system administrator found some problem with the new version of ASPDB component (ASPDB2003-PRO-NT4-101403.DLL). It is found that this component is utilizing high percentage of CPU and crashes the IIS server. Following is the report given by our system administrator:
--------------------------------------------------------------
Unrelated issue "DLLHost spikes on occasions"
Problem: On occasions, a DLLHost.exe instance on these nodes (machines) will spike to 25-75% CPU usage.
Diagnosis: Root cause is data access done by ASP pages through the ASPDB2003-PRO-NT4-101403.DLL component. In our understanding, this component has been introduced recently and approximately since then, the problems of DLLHost spiking and Inetinfo crashing have increased.
--------------------------------------------------------------
To give you brief on system setup:
We have 4 nodes (machines) in AC2K (Application Center 2000) environment, with one machine as Active cluster node. All these machines are WINDOWS 2000 ADVANCED server with latest service pack installed on them. The ASPDB component (ASPDB2003-PRO-NT4-101403.DLL) is installed in Component services in all the 4 machines. There are total of 15 web applications, which use this component. We had no problem when these applications were using the older version of ASPDBPro component. After we changed the code to use the latest version of ASPDB, it is found the IIS server crashes and dllhost.exe (which runs the ASPDBPro dll) consumes upto 75% of CPU.
We also have .NET framework (Version 1.0 and 1.1) installed on all the 4 machines.
Please treat this as URGENT issue and let us know how to correct the problem. We have to close on this as it is burning issue here. It is also brining down other web applications, which is highly used.
Frank, I have mailed the same information to Mark also, for faster reply from your side.
Regards,
Shailesh
ASPDBPro - ISSUE (URGENT)
Frank,
Can we have telephone conference, so we can clear the problem? I feel we can get the solution when we discuss.
regards,
Shailesh