Error when restoring an SQL database

Hello,
Not sure if I've hit the right newsgroup, my apologies if not.
I work with a small software firm, whereby we predominantly develop Point of
Sale software, which can typically contain very large membership databases
(used at Universities and Sporting Venues).
I have received a backup from one of our clients, but am having issues
trying to restore it via Enterprise Manager. I am selecting a device, as I
have the .bak file sitting on my local hard drive, and selecting one device
only.
From the Restore database window, when I click on the Options tab, I get the
following error:
"Error 3205: Too many backup devices specified for backup or restore; only
64 are allowed. RESTORE FILELIST is terminating abnormally."
I can then click on OK and see the rest of the options screen, yet the
Logical file name and Move to physical file name options are left blank.
Even if I try to enter these fields manually and click on OK, I get a
similar error but with RESTORE DATABASE is terminating abnormally.
Is something going wrong with the way the client is backing up the data? I
don't know exactly what procedure they are using, but I'm assuming they are
just using the backup function from with Enterprise Manager.
Could something be going wrong with the way they are sending me the
database? I have received to copies, one as a spanned Zip file and one as a
spanned Winrar file, but I have the same issue with both copies.
Any advise would be appreciated.
Adrian Robertson
CENTAMAN SystemsAdrian,
from your description it seems like the fileheader of the backup file
is corrupt. The restore process can't read the information about the
logical name and the physical path. You can try to run RESTORE
HEADERONLY but I suspest that you get the same error.
Markus|||Hi Marcus
I tried the "View Contents" option and got a similar error, but I can't see
any option to restore headers only (though I agree, I think I'll have the
same issue).
Should I see this in the same area somewhere?
I'm using Microsoft SQL Enterprise Manager version 8.0 if that's any help.
In the event that the header record is corrupt as you suggest, is there
anything I can suggest the client do to improve their backup procedure, or
is this likely to be an issue in the underlying database?
Adrian
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1144220472.886147.50950@.u72g2000cwu.googlegroups.com...
> Adrian,
> from your description it seems like the fileheader of the backup file
> is corrupt. The restore process can't read the information about the
> logical name and the physical path. You can try to run RESTORE
> HEADERONLY but I suspest that you get the same error.
> Markus
>|||Hi,
I think it might be a version compatibility issue. The client is running SQL
Server 2005 9.00.1399
Typically I am running SQL Server 2000
I have a developers edition of SQL Server 2005 9.00.1116, but even when
using this I am unable to restore a backup created in 9.00.1399.
Are there any options in SQL Server 2005 that allows you to take a backup
that will be backward compatible?
Adrian
"MarkusB" <m.bohse@.quest-consultants.com> wrote in message
news:1144220472.886147.50950@.u72g2000cwu.googlegroups.com...
> Adrian,
> from your description it seems like the fileheader of the backup file
> is corrupt. The restore process can't read the information about the
> logical name and the physical path. You can try to run RESTORE
> HEADERONLY but I suspest that you get the same error.
> Markus
>sql