Share via

The client was unable to reuse a session with SPID 443, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this

  • Article
  • 05/29/2020

Question

Friday, May 29, 2020 2:17 PM

Hi Everyone

Since upgrading from SQL Server 2016 to Microsoft SQL Server 2019 (RTM-CU4) (KB4548597) - 15.0.4033.1 

I have been seeing a lot of the following errors in the logfile.

The client was unable to reuse a session with SPID 443, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

Login failed for user xxxxxx'. Reason: Failed to open the database 'xxxxx' configured in the login object while revalidating the login on the connection. [CLIENT: xxx.xxx.xx.xxx]

Please can someone help to find a resolution.

Regards

Clive

All replies (7)

Friday, June 5, 2020 8:40 AM ✅Answered

Found issue to be the way a developer had set his C# API to connect to the database, changes made have now stopped the errors.

Friday, May 29, 2020 9:34 PM

I think a start is reading the error message.

Is the login in the error message actually permitted to access the database?

I guess this could happen in a web application which uses connection poolin and runs as the actual login and not an application login. If a user who is not authenticated comes along and is given a connection in the pool, something like this could happen.

Are there any errors in the application?

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Monday, June 1, 2020 4:03 AM

Does this message come when SQL Server was shutting down or windows was shutting down ?

Cheers,

Shashank

Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

My TechNet Wiki Articles
MVP

Monday, June 1, 2020 6:29 AM

Hi Clive,

Please read this document How It Works: Error 18056 - The client was unable to reuse a session with SPID ##, which had been reset for connection pooling. 

Best regards,
Cathy 

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to  MSDN Support, feel free to contact MSDNFSF@microsoft.com

Thursday, June 4, 2020 8:48 AM

Hi

User has access, API Login, and the API is working and the login does work but I also get the error against other attempts, so not every time this account tries to login.

Thursday, June 4, 2020 8:49 AM

No, is happening throughout the day, but not every time that login makes an attempt.

Thursday, June 4, 2020 8:53 AM

Hi Cathy

I have tried this,

Deleted the user from the database security and re-added still get the error.

if I need to delete totally from SQL, then I'm going to need to sort out downtime again with the users as will stop customers from booking with us.

Clive