Can anyone assist with SRM set up

[NewEnglandPatri]

Hi ,

I'm trying to set up a 5.5 SRM environment and I'm having a few problems:

The production site is set up with VC and SRM installed and was working.

When I log on now though I can't connect to VC. ( this is a timeout error and I have reset the timeout in the registry so this may be solved)

On the production site I have installed both the VC and SRM.

But on trying to start VC again  I get the error attached and the event log shows the error.

One other issue is that after installing SRM on the reocvery site I cannot download and install SRM from the plug in manager.

The error states that 'it cannot connect to the vsphere client'

Any ideas on this would be appreciated.

Patsfan

[basher · Accepted solution]

Hello,

On the first problem it would seem that vCenter cannot connect to its database and therefore cannot start. Some things to check:

1. Have you installed VC and SRM on the same machine

2. Have you created a separate database for SRM if you are using a shared database server?

Stefan

[NewEnglandPatri]

Hi Stefan,

The answer to both your questions is yes.

SRM and VC are both installed on the same server - one at the Prod site and another at the Recovery site.

I have managed to get the Prod up and running with SRM working.

I think the problem here was a timeout error when trying to start the VC services and I reset the timeout in the registry for this.

I'm going to try the same alteration for the VC on the Recovery site.(this did not work - see screen shot)

Both SRM instances are able to connect to their respective DBs.

The problems remaining are that VC cannot connect on the Recovery site but I hope this will be fixed with adjusting the timeout.

The only outstanding issue after that and it's the most irritating one is the Plug in manager not being able to download and install SRM.

Apologies on this one - I don't have a screen shot to hand.

Regards,

Patsfan

[NewEnglandPatri]

VC now up and running on both sites.

You were  right on this one Stefan - the DB was not connected on the Recovery site which is frustrating as this was working last night.

However I am still stuck with the Plug In error.

Please see attached.

Patsfan

[NewEnglandPatri]

After getting the Plug In to install I get hit with this error.

See attached.

[NewEnglandPatri]

All good - Both sites are now up and running.

The initial error was that the DB was connected on the Recovery side.

Patience was probably something I was lacking here and I had to go back and double check all the services and give them time to kick in.

Thanks Stefan.

Patsfan

[basher]

Hi,

Great to hear that everything is now running. Is the Plug-In also running at both sites?

Stefan

[NewEnglandPatri]

Hi Stefan,

Yes

The Plug In is running on both sides now.

When I disconnected from the vSphere Client and then reconnected the Client , it downloaded and installed the plug in.

From my little experience of working with SRM it appears to be a lesson in patience and doesn't like to be powered on and powered off.

Good experience though and ultimately very satisfying to get it up and running.

Thanks for your help

Patsfan