I run a web service on a Windows Server 2003 SP2 box running ASP.net 2.0 accessing Pervasive 220.127.116.11 via ODBC.
I have several installations with a similar configuration but on this particular one, it seems that when more than one person tries to access the Web service at a time I get an IIS Worker Process - error (see attachment) This shuts down the ODBC connection to Pervasive SQL for a time, and then without intervention it will start working again.
There is a variance from this installation compared to all of my working installations, as follows:
On this installation IIS is running on the Pervasive server, on all other installation I have used two separate machines. So normally I specify the ip address of the data server in my connection string. For this one I am using 127.0.0.1.
Also because I normally use 2 machine on the network to accomplish this connection I normally have a DSN Client ODBC interface on the IIS Server and an DSN Engine ODBC Interface on the Data server. So on this installation I am only using the DSN Engine ODBC Interface.
The other thing that this installation has that others do not is large records compared to the other installations. 200000 records compared to 20000.
The error points me to some log files that do not exist:
accompat.txt and w3wp.exe.mdmp they are supposed to be in my profile's directory.
This is from the system event viewer:
The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID: 1[ODBC][Env ea814e8]
Method Name: IDispenserDriver::CreateRe
Process Name: w3wp.exe
w3odbcci!ConnectDlg + 0xffea