After a reboot, the Archive Manager services do not start automatically.
In the Event log, there are errors like:
The Exception message was: [Cannot open database "ArchiveManager" requested by the login. The login failed.
Login failed for user 'Example\ArchiveMgr_Service'.] and it occurred at:
System.Data.SqlClient.SqlException: Cannot open database "ArchiveManager" requested by the login. The login failed.
Login failed for user 'Example\ArchiveMgr_Service'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owni
System.Data.SqlClient.SqlException (0x80131904): Cannot open database "ArchiveManager" requested by the login. The login failed.
This is generally caused when the Archive Manager server is also the SQL server.
When the server is rebooted, The Archive Manager services try to start before the SQL service
This is normal behaviour. As soon as the SQL service is running it will also be possible to start the Archive Manager services.
To avoid the issue in the future, you can follow this microsoft article to set dependencies so that the Archive Manager services wait for the SQL service to start before attempting to start themselves.
http://support.microsoft.com/default.aspx?scid=kb;en-us;193888
If your SQL is on a different machine, then this solution does not apply to you.
