Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Log not available error 9001 Expand / Collapse
Author
Message
Posted Monday, December 20, 2010 7:31 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 10:17 AM
Points: 1,420, Visits: 736
Came in to work this morning to face a bunch of alerts for severity 21 errors.

"DESCRIPTION: The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database."

Hmm.. The drive the log is on was available and logs for other DB were on it. Plenty of space left. Window Application event log showed no errors other than the one listed above. Windows System log showed no errors. I ran dbcc checkdb on the database and the only error reported was that the log was not available.

I took the database offline, then brought it online again and all seems good now. DBCC Checkdb gives no errors. DBCC loginfo(0) gives info, so I'm assuming the log is available. Now just trying to figure out what happened.

Took a closer look at the SQL error log and I see this:

12/20/2010 02:30:01,spid20s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
12/20/2010 02:30:01,spid20s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.
12/20/2010 02:20:29,spid18s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
12/20/2010 02:20:29,spid18s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.
12/20/2010 02:00:14,spid217,Unknown,Recovery completed for database NetPerfMon (database ID 18) in 6 second(s) (analysis 1 ms<c/> redo 1212 ms<c/> undo 4437 ms.) This is an informational message only. No user action is required.
12/20/2010 02:00:13,spid217,Unknown,1 transactions rolled back in database 'NetPerfMon' (18). This is an informational message only. No user action is required.
12/20/2010 02:00:09,spid217,Unknown,21 transactions rolled forward in database 'NetPerfMon' (18). This is an informational message only. No user action is required.
12/20/2010 02:00:03,spid19s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
12/20/2010 02:00:03,spid19s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.
12/20/2010 02:00:03,spid212,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
12/20/2010 02:00:03,spid212,Unknown,Configuration option 'user options' changed from 0 to 0. Run the RECONFIGURE statement to install.
12/20/2010 02:00:03,spid15s,Unknown,Transaction (Process ID 15) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
12/20/2010 02:00:03,spid15s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.
12/20/2010 02:00:03,spid15s,Unknown,Transaction (Process ID 15) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
12/20/2010 02:00:03,spid15s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.
12/20/2010 02:00:02,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/20/2010 02:00:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.
12/20/2010 01:30:01,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/20/2010 01:30:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.
12/20/2010 01:00:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/20/2010 01:00:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.
12/20/2010 00:30:01,spid206,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/20/2010 00:30:01,spid206,Unknown,Starting up database 'SpotlightManagementFramework'.
12/20/2010 00:00:23,spid18s,Unknown,This instance of SQL Server has been using a process ID of 1788 since 12/7/2010 9:47:54 PM (local) 12/8/2010 3:47:54 AM (UTC). This is an informational message only; no user action is required.
12/20/2010 00:00:01,spid295,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/20/2010 00:00:01,spid295,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 23:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 23:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 23:00:01,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 23:00:01,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 22:30:02,spid210,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 22:30:01,spid210,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 22:00:01,spid223,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 22:00:01,spid223,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 21:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 21:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 21:00:01,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 21:00:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 20:30:02,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 20:30:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 20:00:01,spid222,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 20:00:01,spid222,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 19:30:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 19:30:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 19:00:03,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 19:00:02,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 18:30:01,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 18:30:01,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 18:00:01,spid218,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 18:00:01,spid218,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 17:30:01,spid196,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 17:30:01,spid196,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 17:00:02,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 17:00:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 16:30:01,spid214,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 16:30:01,spid214,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 16:00:01,spid229,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 16:00:01,spid229,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 15:30:02,spid205,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 15:30:02,spid205,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 15:00:02,spid219,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 15:00:01,spid219,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 14:30:01,spid213,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 14:30:01,spid213,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 14:00:01,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 14:00:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 13:30:01,spid208,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 13:30:01,spid208,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 13:00:02,spid223,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 13:00:01,spid223,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 12:30:01,spid222,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 12:30:01,spid222,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 12:00:02,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 12:00:01,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 11:30:01,spid203,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 11:30:01,spid203,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 11:00:01,spid220,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 11:00:01,spid220,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 10:30:01,spid206,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 10:30:01,spid206,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 10:00:02,spid212,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 10:00:02,spid212,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 09:30:02,spid214,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 09:30:01,spid214,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 09:00:03,spid225,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 09:00:01,spid225,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 08:30:01,spid199,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 08:30:01,spid199,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 08:00:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 08:00:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 07:30:02,spid204,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 07:30:01,spid204,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 07:00:01,spid216,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 07:00:01,spid216,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 06:30:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 06:30:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 06:00:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 06:00:00,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 05:30:01,spid201,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 05:30:01,spid201,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 05:00:01,spid217,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 05:00:01,spid217,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 04:30:01,spid207,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 04:30:01,spid207,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 04:00:04,spid215,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 04:00:04,spid215,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 04:00:00,spid207,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 04:00:00,spid207,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 03:30:01,spid198,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 03:30:01,spid198,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 03:00:05,spid234,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 03:00:04,spid234,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 02:52:32,spid78,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 02:52:32,spid78,Unknown,Starting up database 'SpotlightManagementFramework'.
12/19/2010 02:52:29,spid71,Unknown,CHECKDB for database 'SpotlightManagementFramework' finished without errors on 2010-12-17 02:50:42.070 (local time). This is an informational message only; no user action is required.
12/19/2010 02:52:29,spid71,Unknown,Starting up database 'SpotlightManagementFramework'.


2 AM is when my maintenance jobs run. It looks like, for some reason, checkdb got stuck in a loop on this database and had tons of spids working. The first "log uinavailable" error occurs at 12/20/10 2:00:03 with a state value of 5. The subsequent ones all have a state value of 1. I haven't been able to find out what the state value represents. I also noticed that the DBCC CHECKDB messages are appearing at times when DBCC is not scheduled to be run - at roughly half hour intervals through out the day. My transaction log backups run then, but I have verified that job does not perform dbcc.

It looks like the clusters of checkdb messages started happening on 12/7/10 at 10 PM, which is just after I restarted the server after applying SQL 2008 SP2.

Anyone have any ideas?
Post #1037190
Posted Monday, December 20, 2010 10:11 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, November 5, 2014 10:17 AM
Points: 1,420, Visits: 736
Figured out part of this.. Still don't know why the logfile was not available, but the repeated DBCC messages were due to the database having autoclose enabled. Each time the db is accessed, the db is started up and dbcc is run against it.
Post #1037274
Posted Tuesday, June 12, 2012 1:25 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Sunday, November 23, 2014 11:23 PM
Points: 1,281, Visits: 1,761
Was this ever resolved? I've had the exact same issue:

Midday: Restored a database which had autoclose enabled.
to
1:31:43 pm: Starting up database 'xxxxxxxx'. (repeatedly due to auto-close)
1:31:45 pm: Error: 1205, Severity: 13, State: 51.
1:31:45 pm: Transaction (Process ID 19) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
1:31:46 pm: Error: 9001, Severity: 21, State: 5.
1:31:46 pm: The log for database 'xxxxxxxx' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Interesting that it's basically the same problem.. the log is corrupt, but the data is SELECTable. UPDATE or INSERTs fail with the message:
Msg 9001, Level 21, State 1, Line 1
The log for database 'TopCat_Mater_CYMH' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Database is in simple recovery and no maintenance or backup tasks had been run as this was on a test server.
Post #1314237
Posted Tuesday, June 12, 2012 1:43 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Sunday, November 23, 2014 11:23 PM
Points: 1,281, Visits: 1,761
To resolve, I took the database offline, brought online, DBCC CHECKDB and found no alllocation or consistency errors. Very weird.
Post #1314248
Posted Monday, July 16, 2012 4:01 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, November 23, 2014 3:41 AM
Points: 238, Visits: 1,108
Thanks for your post.. I've just fixed a database with exactly the same error using this method Have you had anymore thoughts as to why it occurred in the 1st place ?

I've checked the logs etc but can't see clues to why it happened! Would be good to get to the root cause to prevent it from happening again.

Cheers

Vultar
Post #1330010
Posted Monday, July 16, 2012 4:15 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:13 PM
Points: 40,428, Visits: 36,879
Usually IO related, someone fiddled with permissions or the drive with the log file on didn't come online/failed/etc.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1330013
Posted Thursday, January 10, 2013 6:34 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 4, 2014 11:29 PM
Points: 466, Visits: 1,925
I had this issue and found that the database had 'autoclose' option enabled and while trying to open that database it messed up with some system process and got killed. not sure what all happened there. I just disabled this option, took the database offline and back online and it fixed the issue.

Thanks
Chandan
Post #1405387
Posted Tuesday, September 10, 2013 11:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 11, 2014 10:50 AM
Points: 7, Visits: 470
Thanks, that was exactly what I needed!
Post #1493306
Posted Saturday, September 28, 2013 4:08 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 7:27 AM
Points: 2, Visits: 98
We faced exactly the same issue and found Database Auto_Close Option is set to 'True'. We set it False and put database offline and online. The error message stopped popping up soon after this. Still don't know why this option when set ON lead started triggering this error message because log was not corrupted and we were able to query on the database.
Post #1499665
Posted Wednesday, October 2, 2013 11:23 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 7:54 PM
Points: 1,569, Visits: 2,631
.. How it works when taken to offline and then online again, any idea ?
Post #1500864
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse