Thursday, May 27, 2010 1:56 PM
I am trying to install SharePoint Server 2010 in Windows Server 2008 R2. I have a serparate server for SQL server 2008. I have selected 'Server Farm' installation with Server Type 'Complete'.
I am getting following error, "The cabinet file 'OSRCHWFE.CAB" required for the installation is corrupt and cannot be used. This could indicate network error, an error reading from the CD-ROM, or a problem with this package". Network is working fine.
Appreciate any help provided. Thanks.
Thursday, May 27, 2010 3:07 PMAre you installing from a network drive? If so can you copy the install to a local folder and try from there?
- Marked As Answer by Jie Li - SharePointMicrosoft Employee Thursday, May 27, 2010 5:22 PM
Monday, October 25, 2010 6:27 PM
Installing from a local folder does not resolve the issue. I am doing a standalone setup - not a Farm - so the setup launches immediately after selecting Standalone (I have never seen this issue with a Farm deployment - using the exact same deployment bits).
Just before the error, the Application Log shows
Type: Information, Source: MsiInstaller, Event ID: 1040 - Beginning a Windows Installer transaction \localPathToBits\OSRCHWFE.MSI. Client Process Id: 2420
Within a minute at the most you get the error:
Type: Error, Source: MsiInstaller, Event ID: 11335 - Product: Microsoft Search Server 2010 Core -- Error 1335. The cabinet file 'OSrchWFE.CAB' required for this installation is corrupt or cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with the package.
I cancelled the setup and let it roll back. Then bounced the host (otherwise you'll receive a restart required notice when you try to install again).
I copied a fresh ISO image to the VM this is being conifgured on.
Running in elevated Administrator permissions, I extracted the contents of the ISO to a local folder.
I launched the SETUP.CMD as Administrator
Entered the license key, selected Standalone as the deployment, to start the process again.
The exact error is displayed roughly 50% through the installation process.
I located the actual CAB in quetion, using WinRAR - attempted to extract the contents and roughly 3/4 of the way through I get an error that it's corrupt.
Acknowledging that it's 'possible' that when I copy the installation bits, and later an ISO that I extract on the VM - could get buggered while copying from my local file system to the VM's file system - I decided to download fresh ISO bits directly from MSDN - from on the VM directly.
Once the download completed, I extracted the contents using WinRAR, and launched the SETUP.CMD as Administrator.
This time the installation ran all the way through without an error.
NOTE To self: Copying from a Windows Explorer view to a VM Windows Explorer view may appear to go just fine, but it obviously can bugger files. The fresh download of the exact same ISO bits should not have worked, if my ISO was the same build date (and it was). I double-checked myself by running the ISO on a Hyper-V VM by using FTP to push the ISO to the Hyper-V VM host, and it deployed just fine without the error noted above.
So - when you receive these errors - try another means of getting the bits to the host - assuming the host is a VM.