God hates me

StuartHemming · Post by **StuartHemming** » Mon Oct 08, 2007 4:43 am

I've been away for a week.

I come back, trawl through endless mail and finally get to a point where I can do some work.

I start vault (which was working just fine before I went away). I try and connect to the server and get this ...

Unable to connect to http://ecs0063.qube.local/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: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1>Server Application Unavailable
</h1>


The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.


Administrator Note:
 An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

</body>
</html>

The event log contains 2 relevent entries, I think ...

aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.

followed by

aspnet_wp.exe could not be started. The error code for the failure is 80004005. This error can be caused when the worker process account has insufficient rights to read the .NET Framework files. Please ensure that the .NET Framework is correctly installed and that the ACLs on the installation directory allow access to the configured account.

I've had a look around in here and I've tried all the suggestions I could track down up to and including uninstalling and reinstalling there vault server.

HELP!

Beth · Post by **Beth** » Mon Oct 08, 2007 7:44 am

It could be that an update to .NET was applied since you were gone. A previous user was fixed by uninstalling and reinstalling their .NET framework. If you look in your IIS manager on your server, view the properties of Vault Service, and go to the ASP.NET tab and identify which .NET framework is being used. Then, using a command prompt, run the following to uninstall and reinstall:

C:\WINDOWS\Microsoft.NET\Framework\v<whichever version you've identified>\aspnet_regiis -u

then

C:\WINDOWS\Microsoft.NET\Framework\v<whichever version you've identified>\aspnet_regiis -i

Let me know the results afterwards.

StuartHemming · Post by **StuartHemming** » Mon Oct 08, 2007 7:55 am

It seems unlikely as the machine was sat, unplugged, on a chair in my study all week. However, I'll give it a shot.

StuartHemming · Post by **StuartHemming** » Mon Oct 08, 2007 9:08 am

No joy.

Attached, on the off chance that they offer anything useful, are the uninstall and install logs for the commands you asked me to run.

Beth · Post by **Beth** » Mon Oct 08, 2007 1:48 pm

Is it possible that the password for the account the Vault IIS process is running under has changed?

In order for me to be able to tell more, I'll need more information. Can you provide me with your Vault install log, Vault Server Log, and web.config file? The Vault install log is located in %username%\local settings\temp and is called vault_install.log. The Vault server log is in the Windows temp directory, and the web.config is in the Vault service directory that is by default in C:\inetpub\wwwroot\vaultservice.

Please zip them up. You can either post them here, or send me an email at support at sourcegear.com (attn: Beth) with a link to this forum thread.

StuartHemming · Post by **StuartHemming** » Tue Oct 09, 2007 1:04 am

OK. It appears that the problem isn't of you making.

I don't know why it never occured to me to mention this, and for the life of me I can't figure out why it should matter but ...

I am running a single user set up here; the server and client are both on my local machine, a laptop running under WinXP Pro.

Before my holidays I installed and was running connected directly to my company network. Everything was fine.

Yesterday, I was working from home connecting to the network via our VPN. Yesterday Vault wouldn't connect.

Today, I'm in the office and guess what? Yep. It's working.

Thing is, I have a friend who installed and runs Vault but he only ever connects to the network via the VPN.

I will check which account my friend selected to run under but I am running with the ASPNET account.

StuartHemming · Post by **StuartHemming** » Tue Oct 09, 2007 1:12 am

Beth,

Here are the files you asked for.

Just to clarify, I installed and tried to connect to the repository yesterday connected to the network via the VPN but failed. Today I have connected to Vault when connected directly to the network. So I'm not so sure that it is how I'm connected at install time that is relevant.

Beth · Post by **Beth** » Tue Oct 09, 2007 2:53 pm

When on the VPN, what does browsing to http://vaultserver/vaultservice/vaultservice.asmx show? What's the address listed?

If you are on the Vault server itself, what happens if you use "localhost" for the Vault server name (using the same URL as above)? Does it keep the address the same or not connect or something else?

Does the VPN change the DNS name of either what you are connecting to or your computer?

Do you know of the process model that Vault was installed under? (If you want you can zip up and send your Vault_install.log.)

One of the logs mentions aspnet_wp.exe could not be run. Do you know what you have configured within .NET Framework's CONFIG\machine.config file? You could also just zip that up and send it to me if you wish.

Anything that may contain confidential information you can send to support at sourcegear.com (attn: Beth) and include a link to the forum thread.