Start a Conversation

Unsolved

This post is more than 5 years old

1540

February 28th, 2017 00:00

OMIVV 4.0 can not register to Windows based vCenter Server when vCenter Default locale is de-de

Hey guys,

had a lot of trouble updating our OMIVV Installation from 3.1.1 to 4.0. First problem was that the old webclient plugin files were still in place after updating to 4.0. Like in the OMIVV 4.0 release notes described we simply deleted them. Afterwards there was no Dell Management Plugin in the Webclient anymore because the new OMIVV 4.0 had not registered correctly to the Webclient.

Now the real fun began, reregistering to our vcsa based vsphere server was no problem. But sadly the reregistration to our Windows based vSphere Server didn't work as expected, we got the error message 'failed to register extension' everytime we tried to register the appliance.

After a look in the Console of the Webclient we could see that an Alarm could not be created, I think it has something to do with spezial characters used in the german names of the alarm (like Ä Ö Ü).

That in mind I stumbled over the KB Article 2121646 from VMware. After changing the locale from 'de-de 'to 'en-us', as described in the KB Article, on the 'Local System' User and a reboot of the vCenter Server we could finally register the OMIVV Plugin to our Windows based vCenter Server.

I hope someone finds this usefull and maybe this can be fixed in OMIVV in one of the next Releases.

Best regards,
Bjoern Roth

March 2nd, 2017 00:00

Hi Bjoern,

your post is great. It´s the same issue like we had!

THANK YOU SO MUCH!

Best regards, Tom

No Events found!

Top