April 8, 2007 at 11:49 pm
I was successfully able to install sql server 2005 developer edition all peices except the "Workstation Component, Book Online, Development Tool", the last item in the installation list. It gave errror for bad "sql.cab" file. Although this developer edition came directly of the box this error came up in many attempts. Upon "Ignore" it gives error 2350.
As a result I am able to run sql server's all the services and able to access it via VS.Net server browser. I can create and change tables etc. but there is no "Management Studio" installed. There is no icon for it either on the desktop or in the Start->SQL Server 2005 menu.
Is it possible to get and copy sql.cab file or entire client component from somewhere else? --Freed download or something? I searched for sql.cab file but it was not in the CD. It could be inside some other file or cmpressed.
I have used local CD-ROM drive and original 2 CDs the software came in. I have uninstalled VS.Net 2005 and attempted to install Sql Server 2005 first but the result is the same.
Any suggestion.
April 10, 2007 at 6:37 am
i believe the cab files are compressed files that have a lot of other files in them, kind of like a zip file.
have you tried to copy all the files to a network location or locally on that PC/server and install from there? any time we install sql 2005 we always do it from hard disk or network location.
April 10, 2007 at 10:34 am
Problem solved now.
I had a bad media CD.
A different CD fixed the problem.
September 26, 2008 at 8:43 am
Hi,
I have the same issue. - Can't install management studio and other client tools.
when installing the MS SQL Server 2005 developer edition included with VS 2005. The drive image includes a fresh install of XP Pro SP 2, IIS, VB6, VS 2005(without SQL Express!)
Using the install disks provided to install the client tools yields an error:
The cabinet file 'Sql.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM or a problem with this package.
I've done extensive Googling, but no one seems to be able to resolve this without a new disk. Any help would be greatly appreciated.
Thanks,
Dave
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply