Author |
Topic |
hummy
Starting Member
32 Posts |
Posted - 2007-04-11 : 06:18:47
|
Hi there. Could someone help me out. I'm performing a log restore and getting the following error within the SQL Server Error Log.During restore restart, an I/O error occurred on checkpoint file 'G:\MSSQL.1\MSSQL\Backup\dxsh.CKP' (operating system error 1784(error not found)). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.IT's a very basic Restore command and i do have not specified it to Restart. Having checked the MS website for 1784 it suggests the following:The supplied user buffer is not valid for the requested operationCan anyone tell me what is wrong here and why it is creating a checkpoint file or even what it is and how to overcome the error message. TIA |
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-04-11 : 09:56:51
|
Checkpoint files are used more for log shipping, I believe. Are you restoring the database with no_recovery? Or trying to make it read only? Can you supply the restore command? |
|
|
hummy
Starting Member
32 Posts |
Posted - 2007-04-11 : 11:38:37
|
The restore is being done using a thrid party tool so the syntax is slightly different. @DBName is populated with current database restore@DiskFile is populated to point to the next restore fileDECLARE @DBName varchar(50)DECLARE @DiskFile varchar(100)--full restore as followsEXEC master.dbo.xp_restore_database @database = @DBName, @filename =@DiskFile, @with = 'NORECOVERY', @with='REPLACE', @logging = 2--transaction log restore as followsEXEC master.dbo.xp_restore_database @database = @DBName, @filename =@DiskFile, @with = 'NORECOVERY' |
|
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
Posted - 2007-04-11 : 11:57:17
|
is this backup from an older version of sql?If so, you will have to get it out of recovery mode, update its compatibility to 90 and then turn it into norecovery or standby mode as needed. All previous logs will hence be useless.Hope this helps. Please respond promptly to let us know if it worked or not.RegardsParesh MotiwalaBoston, USA |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-04-11 : 13:46:10
|
So this is SQL Litespeed, right? Did you verify that the path is correct for the checkpoint file?Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
hummy
Starting Member
32 Posts |
Posted - 2007-04-11 : 17:14:41
|
Yes you are right it is SQL LiteSpeed. I am trying to restore a SQL2005 DB back onto a SQL 2005 DB.The only difference is that is that the source DB was 64 bit and the destination DB is 32 bit. But i don't think that is an issue. I never specified a checkpoint file path as you can see from my script but just wanted to find out what it is and why it is getting created and how to overcome the problem. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-04-11 : 17:23:48
|
The checkpoint is needed when you are using norecovery, which you are in your script. Try running the sp_restore_database stored procedure by specifying the parameters directly rather than through variables. And no it doesn't matter that the source is 64-bit and destination is 32-bit. We have this same scenario and it works fine.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
|
|
sulie
Starting Member
2 Posts |
Posted - 2008-03-17 : 04:46:37
|
Hi there Did You sort the problem above out as i am getting the same error.and cannot seem to get anywhere.RegardsSulie |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-03-17 : 23:19:57
|
If you use litespeed too, better to check with Quest. |
|
|
sulie
Starting Member
2 Posts |
Posted - 2008-03-18 : 08:30:11
|
Hi I am going to check with quest however i just want to know if Hummy found a solution that could maybe help me or is there something i could try. thanks |
|
|
claire
Starting Member
19 Posts |
Posted - 2008-05-30 : 11:32:18
|
Hi Sulie,Did you get any answer from Quest Soft?We got the same error message today as well. |
|
|
shinoj_r
Starting Member
1 Post |
Posted - 2011-01-07 : 13:11:36
|
I had the same error.. Contacted Quest and they were not able to help. They asked to contact Microsoft. Will be checking with MS shortly |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2011-01-07 : 15:44:01
|
shinoj_r:this is a very old thread, if you need help on this issue you need to start a new thread. This is a straight permissions issue on the directory where SQL Server is trying to create the checkpoint file. Your service account for SQL Server does not have rights to that directory.Jeff |
|
|
|