Windows 2003 Server 32bit w/SP2 Going into Add/Remove programs Windows components, I receive this error message Setup library ocwss.dll could not be loaded, or function OcEntry could not be found Error code 0x7e How do I fix this

Hi, This problem occurs because the Path system variable has changed. To resolve this issue, we can modify the system variables. For the similar steps, please refer to the following Microsoft KB article: You receive a "Setup Library wbemupgd.dll could not be loaded" error message when you use Add or Remove Programs in Windows Server 2003 http://support.microsoft.com/kb/838860 If the issue persists, please also run System File Checker (SFC /Scannow) to scan and repair the system files. For more information, please refer to the following Microsoft KB article: Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe) http://support.microsoft.com/kb/310747 Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

great thanks for the reply, I have change the system path and that didn't fix the issue so will proceed with SFC

Yes, I was going to suggest the SFC /scannow option. I did a bit of research before I came to this thread, and had already come to that conclusion. Good luck!If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer".

Hello all, finally had a chance to get back to this server issue. We just ran SFC /scannow, restarted the server and still we have the same error... "Setup library ocwss.dll could not be loaded, or function OcEntry could not be found Contact your system administrator. The specific error code is 0x7e" we are trying to install IIS on this Windows 2003 server and when we go into the add/remove windows components, this is where we get the error message.

Hi there, I forgot to get back to you on this. We could not resolve the issue with this server ourselves so we called MS Support. After 2.5 hours, the MS tech suggested that we reinstall the operating system which we did not want to do because this is a production server. We decided to leave this issue alone and install another system for the meantime.

I have a fix for this one that worked for me when none of the suggested ones did and I had plenty of other entries in my path besides the wbem. Go into the registry and rename the existing HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment REG_SZ Path to Path_OLD and copy the details to a newly created REG_EXPAND_SZ Path - I put the %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem; at the beginning of the statement and made sure that there was no ; at the end of the statement -- then just close regedit and reboot the server. To be sure the path is being read OK, re-register the dll i.e. from the Run command type "regsvr32 wbemupgd.dll" and if it's seeing the path ok it will find the dll OK and register it.