Enterprise Vault services do not start

[bagrationi]

 Hello,

I have a problem in my Enterprise Vault environment.

So, the problem is that E-vault services do not start. In "Administrators Guide" i've seen that If Enterprise Vault services do not start and report a login failure, the most likely cause of the problem is that the password that has been supplied for the Vault Service account is wrong. If you supply an incorrect password, there will be login failures from all Enterprise Vault services.

It's clear all and understood.
Really i've forgotten my user account password and i accordingly change it. After this behavior the problem still persist in my production. I need very quick response  and resolution of this issue.

How to make it, how to solve this problem that all services still were worked in a normal mode.. ?


Any suggestion will be appreciated,  thanks in advance.

[Liam_Finn1]

So you set a new password on the service accout

Then you went to each service and modified the properties to match the new password

Can you get the Admin service to start. If yes then try this
http://seer.support.veritas.com/docs/283722.htm

[Liam_Finn1]

Dtrace the index broker service and then try to start

can you get the admin server to start? If yes try this to do a force reset on all the EV services to force them to reapply the service account and password

http://seer.support.veritas.com/docs/283722.htm
 

[bagrationi]

 As to the admin service,... no admin service and nor another vault services i cannot start.

...... And second issue:  Do you really recommend me that if i set a new password  on the service account all services will work correctly ?

[bagrationi]

.... I can give you more info, that i cannot open the E-vault administration console.

It displays a following message: Could not connect to the Enterprise Vault Directory on <machine name>
                                                            Check that <machine name> is available on the network and that the Enterprise Vault Directory Service is running.

In event viewer i see the following two event id: Error numbers 7000 and 7038

[Liam_Finn1]

Please post the contents of the two above errors

[bagrationi]

 So, as i mentioned about the error numbers, they are two event id - 7000 and 7038.

Error event id: 7000, Source: Service Control Manager  

The Enterprise Vault Admin Service service failed to start due to the following error:

The service did not start due to a logon failure.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


 

Error event id: 7038, Source: Service Control Manager 

The EnterpriseVaultAdminService service was unable to log on as HELP\evtest with the currently configured password due to the following error:

Logon failure: unknown user name or bad password.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Liam_Finn1]

Did you check each service and ensure that it is configured to logon as your service account as DOMAINNAME\SERVICE ACCOUNT and the password is correct

Also check to see if the EV service account is locked out or not

[GertjanA · Accepted solution]

Hello Bagrationi.

Sounds like a system down to me. You might be better of calling support.

Try this:

1. Open services.msc on the ev-server
2. get the properties of the ev admin service and the ev-directory service.
3. goto logon tab
4. set the password to what you changed it to.
5. Start adminservice
6. Start Directory service
7. Open Vault console, logging in as Vault Service Account
8. Right click the line " Directory on ' directory server' "
9. Choose properties, then tab Service Account
10. Change password there, apply.
11. Verify that password is changed correctly (eventviewer etc)
12. restart admin service

If you have multiple EV-servers, then do step 1 to 6 on the other servers also.

If this is production, do call support.

Gertjan

[bagrationi]

 Thank you very much guys,

your suggestions and responses was very convenient for me.

The problem is solved.