VMware Cloud Community
jeffoutwest
Contributor
Contributor
Jump to solution

Broken plugins: The remote name could not be resolved

vCenter 4.0 update 2

Windows 2003 R2 32 bit Standard

I changed the hostname, (not the domain), of the Windows server hosting the vCenter server and it broke the following plugins:

VMware Service Status

vCenter Hardware Status

The error is:

The following error occured while downloading the script plugin from https://nnn:8443/cim-ui/scriptConfig.xml: The remote name could not be resolved: 'nnn.nnn.nnn'

I can ping and resolve correctly from the OS

Port 8443 is open.

The correct vCenter Server Managed IP and vCenter Server name have been updated in; Administration > vCenter Server Settings > Runtime Settings

An entry for this new hostname has been added in WIndows > System32 > Drivers > etc, althought I think this seems unnecessary.

The vCenter server has been restarted after each change.

The error message is showing that vCenter is still using the old hostname in the \cim-ui\scriptConfig.xml file.

I found the C:\Program Files\VMware\Infrastructure\tomcat\webapps\cim-ui\scriptConfig.xml file, but this does not contain the hostname values I was expecting.

Can someone point me in the write direction to correct this issue? Thanks, -Jeff

0 Kudos
1 Solution

Accepted Solutions
2 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

0 Kudos
jeffoutwest
Contributor
Contributor
Jump to solution

Thanks Troy, that's the ticket.

Next time I will do a better job of searching the KB's

0 Kudos