VaultService: Service is unavailable (error 503)

[gannet]

Hi,

We had a long overdue windows update on our vault server this morning. Once the server came back online we can no longer access our Repository. It consistently fails with the following error:

Unable to connect to http://dbserver01/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 503: Service Unavailable.

On further investigation the VaultAppPool in IIS is 'stopped', simply starting it again does start but as soon as anyone tries to logon it stops again.

Version is: 10.0.2

Any ideas?

Thanks,

-- Peter.

[Tonya]

Hi Peter,

Do you have the AppPools set to automatically recycle based on any events? If so, this can cause the IIS service to go down. If this doesn't help, please try the following and let us know the outcome:

In a web browser, load the page http://VAULTSERVER/VaultService/, where VAULTSERVER is the hostname that you entered into the Vault client's login dialog. If your server is properly configured, you will see the Vault Home Page.

We'd also like to see your Vault Server log.

Thanks,

Tonya

[gannet]

No Recycling is set, pretty default setup.

browser also returns:

Service Unavailable
HTTP Error 503. The service is unavailable.

Where do I find the log you would like to see?

Thanks,

-- Peter.

[Tonya]

Please email your Vault Server log to support@sourcegear.com. The Vault Server log is in %windir%\temp\sgvault\sgvault.log on the server machine.

Thanks,

Tonya

[gannet]

on its' way.

[gannet]

Just thought I'd update this:

We have just managed to resolve this...

We eventually noticed a series of Warnings and Errors in the Windows 'System' logs. The most informative of these was this one:

The identity of application pool VaultAppPool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

Having checked the relevant account the 'Logon as a batch job' right was assigned to the domain account. However using 'secpol.msc /s' on the server itself revealed that the local PC didn't have that account as having that right. Once added to this right under:

Security Settings\Local Policies\User Rights Assignment\Log on as batch job

and restarting the Application Pool, the Vault system magically came back online

[Tonya]

Hello again,

Glad to hear you were able to resolve the problem. Thank you for the update and posting the resolution.

Tonya