Hello,
While talking to one of my application developers, he encountered Fatal Error 9001 while connecting to the database from .NET Application. In the past , he had similar issues and he mentioned that taking the database offline and bringing it back online fixed the problem. So we did the same this and the problem got fixed.
I asked the question why are we having this problem in first place?.I used the SQL Credentials our .NET App uses and I was able to connect to the SQL Server using those credentials and execute the stored procedure.
Doing some online searching, sometimes, turning on Auto close property causes this problem. This particular database had that property turned on and I turned it off. I am not sure how it got turned on in the first place. By default it should be off.
My question is Whats causing this behavior ?. How can I avoid getting 9001 Errors?.
I am tying to figure out the root cause and better undestand whats going on with the server?.
I understand the pros/cons of the auto close property but it shouldn't cause 9001 error.
Your help would be much appreciated.
My SQL Server Version:
select @@version
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64)
Sep 21 2011 22:45:45
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)
Thanks,
I90Runner