The code is C. Trying to get all the files together to
post would take some work. We've done a couple days of
tests, and we're pretty sure the problem on the front end.
The problems we're seeing look much like the bug reported
in KB Q191268. ms-
I went through all our code yesterday looking for open
cursors. Found four. Closing and deallocating them didn't
have any affect on this bug. <sigh>
SQL Server starts isolating SQL code in their own
connections after one particular stored procedure is
fired. One connection after another is opened and closed.
I'm going to start looking at it this morning.
>What does your code that handles the transaction look
>like? It may be doing something to cause the audit
>>Looking at Profiler, we are looking at
>> Audit Login
>> BEGIN TRAN
>> Audit Logout
>> Error: Commit doesn't have a corresponding Begin
>>The logout (session/connection disconnect) apparently
>>We have looked long and hard at how to keep SQL Server
>>from automatically logging us in and out of a session
>>that. We're trying a couple of solutions, but any hints
>>would be welcome.