Veritas Volume Replicator Security Service is not started automatically after rebooting Win2003 server
Updated: 21 May 2010 | 1 comment
This issue has been solved. See solution.
Hi,
I have Veritas Cluster for Exchange 2003 with GCO (Global Cluster Option). The Veritas Volume Replicator Security Service does not start automatically despite the startup type of service is automatic. The only way to start it is to change its login account to local then start it and then change the login account to domain user and start it again. The user name which is I am using is Domain/Administrator.
When this service does not start the Lanman resource fails and the exchange service group fails too.
Any help please?
Regards,
Abdallah Alsaleh
discussion Filed Under:
Comments
Hi Abdallah, You should be
Hi Abdallah,
You should be using the VVR Security Services Configuration Wizard to configure all nodes in your GCO configuration to use the same domain user account. This wizard will restart the VVR Security Service on all nodes as it is changing the startup account. Then try rebooting the nodes to see if the service starts automatically.
It sound like you might be having multiple problems. Lanman uses the VCS HADHelper service to do AD and DNS updates. If this service is not running then Lanman will fault in Exchange clusters.
If you the service you are having problems with is the VCS HADHelper service then you should be using the following command to change it's startup account.
hadhelper /configure /user:Domain/Administrator
It will then prompt you for the password and will set the correct permissions/rights that are needed on the account for Lanman to work correctly. Sometimes additional configuration is needed in DNS security to allow for DNS updates to work correctly.
If you continue to have problems please open a case with Symantec Technical Support.
Thanks,
Wally
Would you like to reply?
Login or Register to post your comment.