April 9, 2009 at 11:17 am
Hi,
While restoring a database i am getting an error as
"Specified Cast is not valid (SqlManagerUI)"
Why is this so.Please advice!!!!!!!!
I am attaching a screenshot of error.
[font="Comic Sans MS"]+++BLADE+++[/font]:cool:
April 9, 2009 at 11:24 am
Might be a management studio bug. Try restoring using T-SQL?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 9, 2009 at 11:25 am
what messge do u get when u run this command on ur backup:
RESTORE VERIFYONLY FROM DISK = 'C;\BlahBlah\urDatabase.bak'
where 'C;\BlahBlah\urDatabase.bak' is location of ur database.
Its nothing to do with the error u posted, but its the 1st step to identify if ur Backup file is valid for retoration or not.
July 8, 2009 at 1:58 pm
I had the same issue as posted.
This is related to a faulty backup.
I tested it again a good one versus a corrupted copy. Both were check each time with a md5sum. The corrupted one always showed the screenshot error and failed the VERIFYONLY test while the good one not.
If trying to restore the faulty backup through SSMS, it can report it as a tape backup or an invalid media backup and refuse to restore it.
I've not try through t-sql however.
In other words, go get another backup.
December 21, 2009 at 8:52 am
Megistal (7/8/2009)
I had the same issue as posted.This is related to a faulty backup.
I tested it again a good one versus a corrupted copy. Both were check each time with a md5sum. The corrupted one always showed the screenshot error and failed the VERIFYONLY test while the good one not.
If trying to restore the faulty backup through SSMS, it can report it as a tape backup or an invalid media backup and refuse to restore it.
I've not try through t-sql however.
In other words, go get another backup.
I know this is an old thread but i just ran into this problem, and the backup isnt faulty.
I got the specified cast is not valid trying to restore a 2.5 TB native backup file from data domain (network backup device) using the SSMS, if you build the tsql script it works just fine, just figured i would comment on that
December 23, 2009 at 4:13 am
If this works in a script but the same command fails in SSMS, then I suggest you raise this as a bug with Microsoft.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
August 10, 2010 at 12:29 pm
Try to see if any resolution on this. Still getting this error when use ssms to restore, and get backup "created using Microsoft Tape Format version 1.240. SQL Server supports version 1.0." message when use tsql to restore with or without move, filelistonly, etc. The backups are fine, but taken from 2008R2 on Win2k8 server, and try to restore to 2008R2 on Win2k3 server. Any issue possibly?
Thanks for any helps, suggestions..
August 11, 2010 at 2:42 am
I think you need to talk to Microsoft about this.
If your backup gts created using Tape Format 1.240 on one operating system and canot be restored on another, using the same version of SQL Server, then this is by definition a bug.
If you confirm that this is in fact happening, please ensure it gets raised on Connect as a bug.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 26, 2012 at 11:08 am
did you get an answer for this ?
I am encountering the same problem.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply