VMware vCenter Site Recovery Manager Server services stop auto

[nareshunik]

VMWARE VCENTER SITE RECOVERY MANAGER SERVER, service stops automatically.

Section for VMware vCenter Site Recovery Manager, pid=2084, version=4.0.0, build=build-192921, option=Release
[2010-12-19 08:39:33.595 06868 warning 'App'] Failed to create console writer
[2010-12-19 08:39:33.611 04220 info 'App'] Set dump dir to 'C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Site Recovery Manager\DumpFiles'
[2010-12-19 08:39:33.611 04220 info 'App'] Intializing the DBManager
[2010-12-19 08:39:33.736 04220 info 'App'] Current working directory: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin
[2010-12-19 08:39:33.736 04220 verbose 'ThreadPool'] TaskMax=10, IoMin=1, IoMax=21
[2010-12-19 08:39:33.736 04220 verbose 'ThreadPool'] Setting COM threading model to MTA
[2010-12-19 08:39:33.736 04220 info 'App'] Trying DrExternalRecoveryApi
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 0 path: dr-external-recovery-api.dll
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 0 absolute path: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin\dr-external-recovery-api.dll
[2010-12-19 08:39:33.736 04220 info 'App'] Trying RecoverySecondary
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 1 path: dr-secondary-recovery.dll
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 1 absolute path: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin\dr-secondary-recovery.dll
[2010-12-19 08:39:33.736 04220 info 'App'] Trying SanProvider
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 2 path: dr-san-provider.dll
[2010-12-19 08:39:33.736 04220 verbose 'App'] Plugin 2 absolute path: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin\dr-san-provider.dll
[2010-12-19 08:39:33.767 04220 info 'Locale'] Locale subsystem initialized from ./locale/ with default locale en.
[2010-12-19 08:39:33.783 04220 info 'SrmServiceInstance'] DrExtApi Service Instance is initialized.

Message was edited by: a.p. (VMware Community Moderator)

Moved to the "Site Recovery Manager" forum and edited the subject line to fix the formatting

[idle-jam]

can you ensure that the mssql service is up and running? also was it ever running properly before this?

[nareshunik]

Thanks for the reply.

I just checked my MSSQL server on the SQL server. Please find the attachment for services already enabled.

Please provide your input..

[mal_michael]

Hi,

Is this a fresh installation of SRM that never worked or this something that stopped working?

Do you have SRM on the second site? Is it working?

Michael.

[nareshunik]

It is was working fine without any issues.The SRM service is working fine on second site  without anyissues.The only issues is on primary site. I am able to start the services and with an second it stops.

[vijayagce]

Hi,

Did you check whether any other service running which is odd from recovery site? Do you have any anti-virtus software installed in that server?

Thanks,

Vijaya

[mal_michael]

Can you attach the complete logfile. There is nothing "suspicious"  in what you have published already.

[BrianStarks · Accepted solution]

While I cannot give you a solution, I can share that I had a similar issue with an SRM install.  Just like yours, mine was a working install that for some odd reason started exhibiting the same symptoms.  Start service, within a second or two, service stopped.

I opened a ticket with VMware on the issue, and over the course of over three months of back and forth exchange with various support techs I never got a satisfactory answer on what was causing it.  The "solution" I was given was to delete the SRM SQL database and re-install SRM.  This "solution" did work, but should this issue return, I'm probably going to have to get unpleasant in insisting they solve the issue.

I wish I could be more help, but there it is.  I feel your pain.

[rubensluque]

Hi,

Have you opened a ticket with VMware or you,ve found a way to fix this problem by yourself ? It seems I have the same situation here.

rgds,

[BrianStarks]

I opened a ticket about it. It got bounced around for about 3 months with absolutely no resolution from VMware. Their only suggestion was to completely uninstall SRM, blow away the database and reinstall from scratch.

Of course, that worked, but it didn't solve the problem or assure me that it wouldn't happen again. Sorry I don't have better news for you, but there it is.

From: Rubens Sanches <communities-emailer@vmware.com>

To: <bstarks@fmbnc.com>

Date: 05/02/2011 04:16 PM

Subject: New message: "VMware vCenter Site Recovery Manager Server services stop auto"