We have 20 SQLServer Express databases and we have been getting the same behavior on ~5 of these servers in the past 25 days.

Although it does not happen every time, there has been deadlocks at the same time that a database is "AutoStarting". After the deadlock the 9001 error starts showing up in the log. Taking the database Offline then Online fixes on the short term, but they are prone to repeating the error.

Setting AutoClose to False has fixed the problem, so far.

04/17/2014 14:52:59,spid59,Unknown,Starting up database 'xyzDB'.

04/17/2014 14:52:59,spid17s,Unknown,The log for database 'abcDB' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

04/17/2014 14:52:59,spid17s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

04/17/2014 14:52:59,spid24s,Unknown,The log for database 'abcDB' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

04/17/2014 14:52:59,spid24s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

04/17/2014 14:52:59,spid59,Unknown,Starting up database 'xyzDB'.

04/17/2014 14:46:55,spid18s,Unknown,The log for database 'abcDB' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

04/17/2014 14:46:55,spid18s,Unknown,Error: 9001<c/> Severity: 21<c/> State: 5.

04/17/2014 14:46:55,spid26s,Unknown,Transaction (Process ID 26) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

04/17/2014 14:46:55,spid26s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.

04/17/2014 14:46:55,spid26s,Unknown,Transaction (Process ID 26) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

04/17/2014 14:46:55,spid26s,Unknown,Error: 1205<c/> Severity: 13<c/> State: 51.

04/17/2014 14:46:53,spid65,Unknown,Starting up database 'xyzDB'.

04/17/2014 14:46:53,spid65,Unknown,Starting up database 'abcDB'.