Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

SQL restore failed with the operating system error 3

Created: 25 Oct 2012 • Updated: 31 Jan 2013 | 1 comment
This issue has been solved. See solution.

 

 
Hi fellas
 
I faced a problem doing SQL restore.plz help. source server win 2008, destination server  win2008, database name = comm , source server n destination server are different.restore script is absolutely correct. plz check attached dbclient logs as well.
NBU SQL agent client GUI logs:
 
CONTINUATION: - An abort request is preventing anything except termination actions.
DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <5133><[Microsoft][ODBC SQL Server Driver][SQL Server]Directory lookup for the file "F:\MSSQL10_50.sourceserver_2\MSSQL\DATA\comm.MDF" failed with the operating system error 3(failed to retrieve text for this error. Reason: 15100).>.
DBMS MSG - SQL Message <3156><[Microsoft][ODBC SQL Server Driver][SQL Server]File 'comm_Data' cannot be restored to 'F:\MSSQL10_50.sourceserver_2\MSSQL\DATA\comm.MDF'. Use WITH MOVE to identify a valid location for the file.>
DBMS MSG - SQL Message <5133><[Microsoft][ODBC SQL Server Driver][SQL Server]Directory lookup for the file "F:\MSSQL10_50.sourceserver_2\MSSQL\Data\comm.LDF" failed with the operating system error 3(failed to retrieve text for this error. Reason: 15105).>
DBMS MSG - SQL Message <3156><[Microsoft][ODBC SQL Server Driver][SQL Server]File 'comm_Log' cannot be restored to 'F:\MSSQL10_50.sourceserver_2\MSSQL\Data\comm.LDF'. Use WITH MOVE to identify a valid location for the file.>
DBMS MSG - SQL Message <3119><[Microsoft][ODBC SQL Server Driver][SQL Server]Problems were identified while planning for the RESTORE statement. Previous messages provide details.>
DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.>
ERR - Error found executing <restore database "comm" from VIRTUAL_DEVICE='VNBU0-10048-9476-1351145153' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery, move 'comm_Data' to 'F:\MSSQL10_50.sourceserver_2\MSSQL\DATA\comm.MDF', move 'comm_Log' to 'F:\MSSQL10_50.sourceserver_2\MSSQL\Data\comm.LDF', replace>.
ERR - Error in VDS->Close: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\restorecommision.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 25(25) seconds.
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\restorecomm.bch>: 

 

Comments 1 CommentJump to latest comment

wr's picture

  missing encryption key?

 

01:40:36.711 [10420.5884] <16> DB_CryptAcquireContext: ERR - Error in CryptAcquireContext : 2148073494.
01:40:36.711 [10420.5884] <1> DB_CryptAcquireContext:     CONTINUATION: - Keyset does not exist
...

01:43:05.666 [10420.5884] <32> CUserLogin::ModifyDefaultSQLUseridAndPasswordInReg: ERR - Error in CryptExportKey (for determining size): 2148073475. The text follows:
01:43:05.666 [10420.5884] <1> CUserLogin::ModifyDefaultSQLUseridAndPasswordInReg:     CONTINUATION: - Bad Key.
 

Will Restore -- where there is a Will there is a way

SOLUTION