Wednesday, March 7, 2012

Error 3624 after getting to 100% complete, restoring sql2k db to sql2k5?

Hi All,
Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
sql2k db gets almost all the way thru, shows 100%, and then I get this 3624
error below.
Any ideas and/or suggestions?
The disk is not full.
Is there any way I can say "don't restore the log file" to isolate a bit?
I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
process of a restore".
I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
Thanks in advance!
Derrick
===================================
Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
--
Program Location:
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
at
Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
===================================
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Program Location:
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
sqlCommand, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection
sqlCommands, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection
queries)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection
queries, ServerMessageEventHandler dbccMessageHandler, Boolean
errorsAsMessages)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
server, StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
===================================
A system assertion check has failed. Check the SQL Server error log for
details. Typically, an assertion failure is caused by a software bug or data
corruption. To check for database corruption, consider running DBCC CHECKDB.
If you agreed to send dumps to Microsoft during setup, a mini dump will be
sent to Microsoft. An update might be available from Microsoft in the latest
Service Pack or in a QFE from Technical Support. (.Net SqlClient Data
Provider)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3624&LinkId=20476
--
Server Name: localhost\sql2005
Error Number: 3624
Severity: 20
State: 1
Line Number: 1
--
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection)
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.SqlCommand.RunExecuteNonQueryTds(String
methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
sqlCommand, ExecutionTypes executionType)And here is a little more detail from the event log.
SQL Server Assertion: File: <container.cpp>, line=3380 Failed Assertion ='pFcb && pFcb->IsOpen ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
"Derrick" <derrick@.noreply.com> wrote in message
news:OTJYC$RgHHA.3388@.TK2MSFTNGP02.phx.gbl...
> Hi All,
> Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
> sql2k db gets almost all the way thru, shows 100%, and then I get this
> 3624 error below.
> Any ideas and/or suggestions?
> The disk is not full.
> Is there any way I can say "don't restore the log file" to isolate a bit?
> I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
> process of a restore".
> I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
> Thanks in advance!
> Derrick
>
>
> ===================================> Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
> --
> Program Location:
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> at
> Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
> ===================================> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
> sqlCommand, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection
> sqlCommands, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection
> queries)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection
> queries, ServerMessageEventHandler dbccMessageHandler, Boolean
> errorsAsMessages)
> at
> Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
> server, StringCollection queries)
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> ===================================> A system assertion check has failed. Check the SQL Server error log for
> details. Typically, an assertion failure is caused by a software bug or
> data corruption. To check for database corruption, consider running DBCC
> CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini
> dump will be sent to Microsoft. An update might be available from
> Microsoft in the latest Service Pack or in a QFE from Technical Support.
> (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3624&LinkId=20476
> --
> Server Name: localhost\sql2005
> Error Number: 3624
> Severity: 20
> State: 1
> Line Number: 1
>
> --
> Program Location:
> at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
> Boolean breakConnection)
> 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.SqlCommand.RunExecuteNonQueryTds(String
> methodName, Boolean async)
> at
> System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
> result, String methodName, Boolean sendToPipe)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
> sqlCommand, ExecutionTypes executionType)
>
>

No comments:

Post a Comment