Knowledge Base for Windows

Description/Problem:
Some weeks ago we used the HP Insight Server Migration Pack (HP ProLiant Server) for migration of server from old to new hardware. Migration process finished successfully and everything seems fine. After standard system checks and tests we identify small problem related to execution of some EXE files. Each try to execute EXE file failed with error message: Application error: The instruction at “0×10015026″ referenced memory at “0×00000000″. The memory could not be “read”.

Solution:
Based on our investigation we identify that problem is related to the Windows Management Instrumentation (WMI). We resolved the issue by running below script.

@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End
:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer
:SkipSrv
goto End
:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End

Description/Problem:
Several users inform us that they have problem on Microsoft Windows 2003 – Terminal Servers with latest version of HP Universal Print Driver (4.7). Installation of this driver was not finished successfully and now after each user login to the system the installer tries to continue with installation of “32 Bit HP CIO Components”. This installer is running for a long time without success and blocked also installation of another applications which are using Microsoft Installer (MSI). We identify that Microsoft Installer related to the “32 Bit HP CIO Components” creates thousands registry API calls as a result of over 2000 – 4000 subkeys created in the registry for every mapped printer. The HP Support provides to us information that issue will be fixed in next update for HP Universal Print Driver (version 4.7.x).

Solution:

• Stop Print Spooler service
• Remove manually all HP Universal Print Driver (4.7) from Print Server
• Client side – delete all the registry keys that were created by the 32 Bit HP CIO Components Installer
  
  • HKEY_USERS\.DEFAULT\Software\Hewlett-Packard
• Server side – delete all the registry keys that were created by the 32 Bit HP CIO Components Installer
  
  • HKEY_USERS\.DEFAULT\Software\Hewlett-Packard
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows NT\CurrentVersion\ Terminal Server\Install\Software\ Hewlett-Packard
• Reinstall old version of HP Universal Print Driver on Print Server
• Restart server

More info about this issue is described on HP IT Resource Center Forum.