SQL Server Installation Failure due to Cabinet File (SQL.CAB) Error
As a DBA it is common to install SQL Server and related components. Most often or not the SQL Server installation is easy and completes without any errors. But sometimes when SQL Server installation fails, it makes it very difficult to identify the problem and to find a solution for the same.
There are various reasons why SQL Server installation fails and below is one such error which you may receive while trying to install SQL Server instance using the setup media from DVD mounted drive.
The following error has occured:
The cabinet file ‘Sql.cab’ required for this installation is corrupted and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.
Looking at the above error, first thing which can think about is that this error has something related to the corrupt media and some problem with the installation media. So, we can try below steps to see if we can get around the error.
– Launch the Setup by choosing “Run as Administrator”
– Copy the SQL Server Installation media to local disk instead of DVD drive or Network.
– Make sure the Setup media is not corrupt, one way to verify this is to try and install the SQL Server instance on another test server to see if the issue still persists.
– Try downloading the media again from the MSDN site using download manager.
– Extract the contents of SQL Server Media ISO file using MagicISO and then try to install from the extract media.
– Turn off or Uninstall any Anti-Virus software running on the system. Reboot of the server is required after making this change.
– Sometimes this error may be returned of the windows installer file is corrupt, so if above did not work, then it is good option to try and uninstall the Windows installer and reinstall it. Reboot the server and then attempt to install again.
Hopefully one of the above solution should help you in resolving this issue.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.