I did a backup of our WSS 3.0 site. While I was trying to restore it, I kept
getting an error on the content database. The error is below. I don't
understand why it tells me it can't login because I have admin rights on the
SQL Server. Also, it had no problem restoreing the Search database. I just
don't understand.

[3/4/2007 9:13:23 PM]: Error: Object STS_iis-in01_599050834_19650 failed in
event OnRestore. For more information, see the error log located in the
backup directory.
SqlException: Login failed for user 'vincent.wright'.
[3/4/2007 9:13:23 PM]: Debug: 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.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
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreConnection.ConnectMaster()
at
Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreConnection.Connect()
at
Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.Run(SPBackupRestoreInformation args)
at
Microsoft.SharePoint.Administration.Backup.SPSqlRestoreHelper.Run(SPBackupRestoreInformation args)
at Microsoft.SharePoint.Administration.SPDatabase.OnRestore(Object
sender, SPRestoreInformation info)
at Microsoft.SharePoint.Administration.SPContentDatabase.OnRestore(Object
sender, SPRestoreInformation info)
--
Vincent Wright

Re: Restore problem with stsadm and WSS 3.0 by callahan

callahan
Wed Mar 14 00:55:13 CDT 2007

I've seen this during restores as well. What happened in my case is the
restore attached the database to SQL but did not actually give the correct
login accounts dbo rights to the database. You need to go into SQL on the
server (I assume you are using SQL 2005?), and add the correct accounts as
dbowners in order for the database to work.

I take it that vincent.wright is your farm account? That's often the one
that messes up for me on restore. You can also have the wrong content
database account as well.

Once you've ensured that the correct accounts have ownership of the database
in SQL, go to sharepoint, go to the content database page for the web
application(s) you are trying to restore and either manually add the content
database to the correct web app, or make certain that is is set to Ready
status.

I have also seen the database look fine, connected to the correct web app,
and Ready. But it doesn't work until I set it Offline, then wait a moment,
and reset its status to Ready, which seems to rebuild the connection between
the web application and the database on the SQL server.

I hope this helps. It's actually reassuring to see someone else have the
same problems I have.
-callahan
"vincentw56" <MSDNNospam252@nospam.nospam> wrote in message
news:8C6C3AA8-9765-42C8-9AD7-2BF1EDCE4190@microsoft.com...
>I did a backup of our WSS 3.0 site. While I was trying to restore it, I
>kept
> getting an error on the content database. The error is below. I don't
> understand why it tells me it can't login because I have admin rights on
> the
> SQL Server. Also, it had no problem restoreing the Search database. I
> just
> don't understand.
>
> [3/4/2007 9:13:23 PM]: Error: Object STS_iis-in01_599050834_19650 failed
> in
> event OnRestore. For more information, see the error log located in the
> backup directory.
> SqlException: Login failed for user 'vincent.wright'.
> [3/4/2007 9:13:23 PM]: Debug: 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.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
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
> owningConnection, DbConnectionPool pool, DbConnectionOptions options)
> at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
> owningObject)
> at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
> owningObject)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreConnection.ConnectMaster()
> at
> Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreConnection.Connect()
> at
> Microsoft.SharePoint.Administration.Backup.SPSqlBackupRestoreHelper.Run(SPBackupRestoreInformation
> args)
> at
> Microsoft.SharePoint.Administration.Backup.SPSqlRestoreHelper.Run(SPBackupRestoreInformation
> args)
> at Microsoft.SharePoint.Administration.SPDatabase.OnRestore(Object
> sender, SPRestoreInformation info)
> at
> Microsoft.SharePoint.Administration.SPContentDatabase.OnRestore(Object
> sender, SPRestoreInformation info)
> --
> Vincent Wright