Errors in setting up PowerCLI on Windows server 2008

Asked By 10 points N/A Posted on -
qa-featured

Hello,

 Today I tried to set up PowerCLI on a fresh installed Windows 2008 R2 server.

But I found the following error message:

Error:

VMware vSphere PowerCLI Installer Information

Error 1406.Could not write value InstallPath to key SoftwareVmware,Inc.Vmware vSphere SDK Runtime. Verify that you have sufficient access to that key,or contact your support personnel.

Need a solution.

Thanks in advance

SHARE
Best Answer by Sharath Reddy
Go To Solution
Best Answer
Best Answer
Answered By 590495 points N/A #100411

Errors in setting up PowerCLI on Windows server 2008

qa-featured

I’m not sure if you have an incompatible system or an incompatible VMware environment. Your operating system seems very much compatible with this application so I doubt that the problem maybe is with your version of VMware environment. But before installing vSphere PowerCLI 5.0 (I’m not sure if this is your version since you did not include any information about it), you need to install first Microsoft .NET Framework 2.0 Service Pack 1 and Windows PowerShell 1.0 or 2.0. If you already have both of these applications installed on your system, you can now proceed on installing vSphere PowerCLI 5.0. VMware vSphere PowerCLI 5.0 can be installed on a computer that is running on Windows Server 2003 Service Pack 2, Windows Server 2008, Windows XP Service Pack 2 32-bit and 64-bit, Windows Vista 32-bit and 64-bit, or Windows 7 32-bit and 64-bit platforms.

vSphere PowerCLI 5.0 supports these VMware environments:

  • VMware ESXi 4.1
  • vCenter Server 5.0
  • VMware ESXi 5.0
  • VMware ESX 4.1 or vCenter Server 4.1
  • VMware ESX 4.0 Update 2 or vCenter Server 4.0 Update 2
  • VMware ESX 4.0 Update 1 or vCenter Server 4.0 Update 1

Since I think there should be no problem with your operating system, you better check the version of the VMware environment you are using. It is possible that the version is not applicable with this version of vSphere PowerCLI. And also, if you are installing the software from an installer disc of vSphere PowerCLI, check if the disc is not damaged. Check the data side of the disc if it doesn’t have any deep scratches that might affect the data it contains. To be sure that the disc is working, try installing it on a different computer then see what happens.

About Sharath Reddy
Questions
1
Answers
14599
Best Answers
2290
Answered By 10 points N/A #100412

Errors in setting up PowerCLI on Windows server 2008

qa-featured

Hello Homer,

The error that you are getting is commonly caused by a corruption or issue with the manifest file as detailed in the error message that you are getting.

To resolve it, you will need to do the following:

  • You will need to go into the manifest file for the repository (GlobalManifest.metadata)
  • After accessing it, you will need to ensure that all trailing brackets are closed.
  • After that you will need to add </vRangerGlobalManifestFile > at the end of the document.
  • Once you have done that, save vSphere and then test it again.

Hope this helps.

Regards,

Carl

About Carl Jack
Questions
1
Answers
1657
Best Answers
417

Wedding invitation creator you can recommend

Previous

Video chat using Samsung Galaxy S2

Next

Related Questions