IIS6 and ADO

External Since: Oct 12, 2004 Posts: 4

Hi!

I am aware of the problem using Access databases on IIS6.0, is there anyway
to work around the locking issues that occur sometime? Take a look at a
piece of the iisstate log below, is an app-recycle the only thing that helps
here. Can I write the ADO code differently to avoid this type of locking.
I've talked to Microsoft dev support about this and they recommend
converting to msde instead, but today that isn't possible the way that this
system is build. It's not one database, but about 200 and they are build
dynamically depending on how the user adds components.

Thanks
/Johan

*************************************************************
Thread ID: 65
System Thread ID: 11c8
Kernel Time: 0:0:3.875
User Time: 0:0:5.125
Other information: Thread is waiting for a lock to be released. Looking for
lock owner.
Owning thread System ID: 1628
Thread Type: Jet DB Query. Possible ASP Page
Executing Page: <the physical path>

# ChildEBP RetAddr
00 1148ed7c 77f43741 SharedUserData!SystemCallStub+0x4
01 1148ed80 77f5d64e ntdll!ZwWaitForSingleObject+0xc
02 1148edbc 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
03 1148edc4 1b005784 ntdll!RtlEnterCriticalSection+0x46
04 1148ee40 0a4d4602 msjet40!WZSchemaChangesReceived+0x1c
05 00000001 00000000 oledb32!CDBInitialize::DoInitialize+0x32

*************************************************************
Thread ID: 39
System Thread ID: 1628
Kernel Time: 0:0:7.875
User Time: 0:0:12.93
Other information: Thread is waiting for a lock to be released. Looking for
lock owner.
Owning thread System ID: 11c8
Thread Type: Jet DB Query. Possible ASP Page
Executing Page: <the physical path>

# ChildEBP RetAddr
00 1076dc94 77f43741 SharedUserData!SystemCallStub+0x4
01 1076dc98 77f5d64e ntdll!ZwWaitForSingleObject+0xc
02 1076dcd4 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
03 1076dcdc 1b812ee4 ntdll!RtlEnterCriticalSection+0x46
04 1076dcec 1b812ec4 msjtes40!`string'
05 1076dcf8 1b8131f6 msjtes40!`string'
06 1076dd1c 771752f4 msjtes40!`string'+0x2
07 1076dd3c 771751a0 ole32!CreateInprocInstanceHelper+0x1a
08 1076de18 77175231 ole32!ICoCreateInstanceEx+0x89
09 1076de40 77175202 ole32!CComActivator::DoCreateInstance+0x26
0a 1076de64 77175271 ole32!CoCreateInstanceEx+0x21
0b 1076de94 1b039dcf ole32!CoCreateInstance+0x3a
0c a0007687 00000000 msjet40!UtilRegQueryValueW+0x1f

External Since: Dec 23, 2003 Posts: 905

Try this -
FIX: Web applications that use the Jet database engine may stop responding
under heavy load
<a style='text-decoration: underline;' href="http://support.microsoft.com/?id=838306" target="_blank">http://support.microsoft.com/?id=838306</a>

--
Regards,
Bernard Cheah
<a style='text-decoration: underline;' href="http://www.tryiis.com/" target="_blank">http://www.tryiis.com/</a>
<a style='text-decoration: underline;' href="http://support.microsoft.com/" target="_blank">http://support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.msmvps.com/bernard/" target="_blank">http://www.msmvps.com/bernard/</a>

"Johan Karlsson" <johan.karlsson*no-/(/spam*@adnome.se> wrote in message
news:Oo4DPyOsEHA.1988@TK2MSFTNGP11.phx.gbl...
> Hi!
>
> I am aware of the problem using Access databases on IIS6.0, is there
anyway
> to work around the locking issues that occur sometime? Take a look at a
> piece of the iisstate log below, is an app-recycle the only thing that
helps
> here. Can I write the ADO code differently to avoid this type of locking.
> I've talked to Microsoft dev support about this and they recommend
> converting to msde instead, but today that isn't possible the way that
this
> system is build. It's not one database, but about 200 and they are build
> dynamically depending on how the user adds components.
>
> Thanks
> /Johan
>
>
> *************************************************************
> Thread ID: 65
> System Thread ID: 11c8
> Kernel Time: 0:0:3.875
> User Time: 0:0:5.125
> Other information: Thread is waiting for a lock to be released. Looking
for
> lock owner.
> Owning thread System ID: 1628
> Thread Type: Jet DB Query. Possible ASP Page
> Executing Page: <the physical path>
>
> # ChildEBP RetAddr
> 00 1148ed7c 77f43741 SharedUserData!SystemCallStub+0x4
> 01 1148ed80 77f5d64e ntdll!ZwWaitForSingleObject+0xc
> 02 1148edbc 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
> 03 1148edc4 1b005784 ntdll!RtlEnterCriticalSection+0x46
> 04 1148ee40 0a4d4602 msjet40!WZSchemaChangesReceived+0x1c
> 05 00000001 00000000 oledb32!CDBInitialize::DoInitialize+0x32
>
> *************************************************************
> Thread ID: 39
> System Thread ID: 1628
> Kernel Time: 0:0:7.875
> User Time: 0:0:12.93
> Other information: Thread is waiting for a lock to be released. Looking
for
> lock owner.
> Owning thread System ID: 11c8
> Thread Type: Jet DB Query. Possible ASP Page
> Executing Page: <the physical path>
>
> # ChildEBP RetAddr
> 00 1076dc94 77f43741 SharedUserData!SystemCallStub+0x4
> 01 1076dc98 77f5d64e ntdll!ZwWaitForSingleObject+0xc
> 02 1076dcd4 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
> 03 1076dcdc 1b812ee4 ntdll!RtlEnterCriticalSection+0x46
> 04 1076dcec 1b812ec4 msjtes40!`string'
> 05 1076dcf8 1b8131f6 msjtes40!`string'
> 06 1076dd1c 771752f4 msjtes40!`string'+0x2
> 07 1076dd3c 771751a0 ole32!CreateInprocInstanceHelper+0x1a
> 08 1076de18 77175231 ole32!ICoCreateInstanceEx+0x89
> 09 1076de40 77175202 ole32!CComActivator::DoCreateInstance+0x26
> 0a 1076de64 77175271 ole32!CoCreateInstanceEx+0x21
> 0b 1076de94 1b039dcf ole32!CoCreateInstance+0x3a
> 0c a0007687 00000000 msjet40!UtilRegQueryValueW+0x1f
>
>