Corrupt WMI Causing SharePoint Provisioning to Fail

Recently our team ran into an issue where SharePoint where solution deployment is failing with following errors.
After troubleshooting and going through the forums it was suspected that WMI might be corrupt on the Windows 2003 Server hosting SharePoint.

To confirm the suspicion that WMI was indeed corrupt, we used the wbemtest.exe utility to check connectivity.
Click Connect:
Click Connect, using the default values:
If no error is thrown, you have successfully connected to the local machine via WMI. If “Not Found” error message is received, you indeed have a corrupted WMI instance. To further test, you could execute the following WMI query to test the specific class SharePoint is querying during search provisioning, using the following example:
If you received an error message when trying to connect, you can attempt to re-register the WMI .dll’s and .exe’s using the following seven steps:
1. Disable and stop the Windows Management Instrumentation service.
2. Right-click Command Prompt and select Run as Administrator.
3. In the Command Prompt, type cd %windir%\system32\wbem and press Enter.
4. Type for /f %s in ('dir /b *.dll') do regsvr32 /s %s and press Enter to re-register WMI DLL files.
5. After completed, type for /f %s in ('dir /b *.mof') do mofcomp %s and press Enter to re-compile WMI mof files.
6. After that, type the command wmiprvse /regserver and press Enter.
7. Start the Windows Management Instrumentation service and change the Start-up Type back to Automatic.
After following above steps Solution was deployed successfully.

Comments

Popular posts from this blog

WCF WSDL location address Issue resolved when hosted over HTTPS with basicHTTPBinding

Yellow Background issue in Word to PDF conversion

Gmail tricks - create unlimited siblings of your Gmail address