Article ID: 5821, created on Dec 2, 2008, last review on May 1, 2014

  • Applies to:
  • Helm 4

Symptoms

After update Parallels Helm Control System to 4.1 on Windows 64-Bit
systems, "Parallels Helm 4.1 Network Service" service stops working (it
doesn't listen on socket and doesn't produce any log files).

Affected systems

Parallels Helm 4.1.0
Microsoft Windows Server 2003 64-Bit
Microsoft Windows Server 2008 64-Bit

Problem explanation

There is a weak in Helm4to4.1UpgradeTool which switch "Parallels Helm
4.1 Network Service" service into 32-Bit mode, but does not synchronize
"SOFTWARE\WebHostAutomation" registry keys for 32 and 64-Bit modes.

Resolution

You can workaround the problem manually or using special utility.
Manual fix:
1.Export "SOFTWARE\WebHostAutomation" registry key using 64-Bit
"regedit" utility:
a) Type "regedit" in the Run dialog (Start menu->Run)
b) Select "HKEY_LOCAL_MACHINE\SOFTWARE\WebHostAutomation" key
c) Export the key using File->Export menu
d) Close "regedit" utility
2.Import exported data using 32-Bit "regedit" utility:
a) Type "%systemroot%\SysWOW64\regedit.exe" in the Run dialog (Start
menu->Run)
Note: c:\windows - is Windows installation location
b) Import exported file using File->Import menu
3.Restart "Parallels Helm 4.1 Network Service" using Parallels Helm
Configuration Tool.

Using utility:
1.Download extract and run "SyncWOW6432Node.exe" utility.
2.Restart "Parallels Helm 4.1 Network Service" using Parallels Helm
Configuration Tool.

Attachments

0331e0e4efc12686c3f22fc2cdda9f03 152090ff5e9a05ea7e1cf0c248449638 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF