Failed to generate certificate during install of SRM

[vSeanClark]

I'm installing SRM update 1 on the server with Virtual Center 2.5 Update 3. I get following error (or see attached screenshot):

Failed to generate certificate.

Details:

Error: Invalid argument : DR_CERT_SERVER certificate filed is too long (>32)

I

I can recreate the error on both my Virtual Center servers.

Thoughts? Will update my findings after dinner. I need to eat.

If you value your karma, please consider awarding points for "Correct" or "Helpful".

Sean Clark - vExpert, VCP - http://twitter.com/vseanclark - http://seanclark.us

[Smoggy · Accepted solution]

your vCenter server FQDN > 32 characters would cause this error. are they > 32 chars?

cheers

Lee Dilworth

PS: if you want to use self signed certs also see: http://kb.vmware.com/kb/1008390

[vSeanClark]

Thanks, Lee!

protectedesx.allianctechnologies.net = 36 Chars!!

I'm an idiot. At least we have this quick hitting solution out there for easy searching for future folks. If you value your karma, please consider awarding points for "Correct" or "Helpful".

Sean Clark - vExpert, VCP - -

[vSeanClark]

So I can correct my Virtual Center's FQDN. My ESX servers will also be in the same boat. Think I'll run into the same problem? I'm going to try quick and see what happens.

If you value your karma, please consider awarding points for "Correct" or "Helpful".

Sean Clark - vExpert, VCP - http://twitter.com/vseanclark - http://seanclark.us

[vSeanClark]

I changed the computer name of Virtual Center and still had probs. Virtual Center Server service would not start. Since I"m using SQL 2005 Express database on my Virtual Center VM. I had to follow these instructions: http://www.ccirrus.per.sg/rfc13109/2008/08/virtualcenter-service-error/

Basically tweak the DSN for connecting to the database so it works for the new computer name.

If you value your karma, please consider awarding points for "Correct" or "Helpful".

Sean Clark - vExpert, VCP - http://twitter.com/vseanclark - http://seanclark.us

[Erik_Bussink]

Also run in the same issue, unfortunately I cannot change the corporate naming policy for the client. So we are now using a 'short name' FQDN for the certificate. It's messy and I'm not happy about it.

Can this please be fixed in the next release of SRM.

Erik

[dellboy]

Hi Sean

In the case where SRM won't install due to the FQDN being too long when SRM generates the certificate, you don't actually have to change the FQDN of the ESX hosts - just rename vCenter and reboot.(as a precautionary measure I backed up the databases etc first)

... I ran into this issue a while back, and resolved it by shortening the computername of vCenter (vCenter FQDN Too Long)

Don't forget that if the databases are stored locally on vCenter, you will need to update the DSN with the new computername (unless it's pointing to (local)).

Matt