Jump to content

Oh4Sh0

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Oh4Sh0

  • Rank
    Newbie
  1. Oh4Sh0

    SQLVDI Error attempting to restore a db

    The only result googling that gets me is a msdn link on building Transact SQL statements. I tried a restore of the "master" db in single user mode, that generates an instant failure (-1) message when "Restore Database" is clicked. I have tried both methods, as SA and with a user account. Both produce the same result.
  2. Oh4Sh0

    SQLVDI Error attempting to restore a db

    - 8/11/2008 3:09:36 AM: Restoring from Teambase Data A [011] Restore type: Full T-7: RestoreStart: id='retrospect' T-7: TWDBSqlDatabase::execSqlRestore: sqlCmd='RESTORE DATABASE [Teambase] FROM VIRTUAL_DEVICE='dantz_retrospect_vd_TeamDB' WITH MOVE 'ae_Version6_0_dat' TO 'C:\TeamDB\Teambase.mdf', MOVE 'ae_Version6_0_log' TO 'C:\TeamDB\Teambase_log.ldf', NORECOVERY' T-7: execSqlOdbcCommand: id='retrospect' T-7: execSqlOdbcCommand: Error on SQLExec. T-7: processSqlMessages: Msg 5,133, SevLevel 16, State 1, SQLState 42000 T-7: (5,133) - Directory lookup for the file "C:\TeamDB\Teambase.mdf" failed with the operating system error 2(The system cannot find the file specified.). T-7: processSqlMessages: Msg 3,156, SevLevel 16, State 3, SQLState 42000 T-7: (3,156) - File 'ae_Version6_0_dat' cannot be restored to 'C:\TeamDB\Teambase.mdf'. Use WITH MOVE to identify a valid location for the file. T-7: processSqlMessages: Msg 5,133, SevLevel 16, State 1, SQLState 42000 T-7: (5,133) - Directory lookup for the file "C:\TeamDB\Teambase_log.ldf" failed with the operating system error 2(The system cannot find the file specified.). T-7: processSqlMessages: Msg 3,156, SevLevel 16, State 3, SQLState 42000 T-7: (3,156) - File 'ae_Version6_0_log' cannot be restored to 'C:\TeamDB\Teambase_log.ldf'. Use WITH MOVE to identify a valid location for the file. T-7: processSqlMessages: Msg 3,142, SevLevel 16, State 99, SQLState 42000 T-7: (3,142) - File "sysft_TmbInfoSearch" cannot be restored over the existing "E:\MSSQL.1\MSSQL\FTData\TmbInfoSearch0000". Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location. T-7: processSqlMessages: Msg 3,142, SevLevel 16, State 99, SQLState 42000 T-7: (3,142) - File "sysft_TmbBlobSearchables" cannot be restored over the existing "E:\MSSQL.1\MSSQL\FTData\TmbBlobSearchables0000". Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location. T-7: processSqlMessages: Msg 3,119, SevLevel 16, State 1, SQLState 42000 T-7: (3,119) - Problems were identified while planning for the RESTORE statement. Previous messages provide details. T-7: processSqlMessages: Msg 3,013, SevLevel 16, State 1, SQLState 42000 T-7: (3,013) - RESTORE DATABASE is terminating abnormally. T-7: MapError: unknown Windows error 5,133 is the error log retrospect produces when I try to restore the db to a different location, and with a different name. You say something might be wrong with how SQL is configured - but this is a newly created server, with sql05 + sp2 in mixed mode and no other db's on it. Nothing the original server didn't have.
  3. Oh4Sh0

    SQLVDI Error attempting to restore a db

    edit: double post, sorry.
  4. Oh4Sh0

    SQLVDI Error attempting to restore a db

    is what I get. Really doesn't give me much of a hex error code. 0x00000000
  5. Oh4Sh0

    SQLVDI Error attempting to restore a db

    The operations log says: T-7: MapError: Unknown Windows error 3,142 Trouble writing files, error -1004 (Database Backup/Restore error) If I try to restore just the full db, the same thing happens. Same thing happens if I change the name of the db, put it in a different location, and uncheck making the database operational. I've tried them all without luck. The SQL Server Error logs are empty - it shows no errors. I had a second administrator double check this to make sure I wasn't crazy. The only place the error log shows up is in the Event Viewer, and after it shows up the retrospect job fails without beginning the restore process. If you have any other thoughts, or are willing to get on the phone with me, please let me know. The situation is becoming quite an emergency. Thanks!
  6. We had a server that booted off of our SAN that corrupted, and I am now trying to restore a db from that server to a newly built one. It has SQL05 SP2. When I attempt to restore the differential+full backup, I get: Event Type: Error Event Source: SQLVDI Event Category: None Event ID: 1 Date: 8/8/2008 Time: 11:12:15 PM User: N/A Computer: TEAMBASE-SQL Description: SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$TEAMBASE-SQL. ErrorCode=(1060)The specified service does not exist as an installed service. . Process=1884. Thread=1892. Client. Instance=TEAMBASE-SQL. VD=. For more information, see Help and Support Center at And a -1004 error/failed on the retrospect client. Anyone know how to resolve this issue? Thanks
×