Nobody can connect to the server this morning

[craigr]

All of a sudden this morning, nobody in the office can connect to the Vault server.

Running Vault Standard 5.1.1.19215.

I can get to <vaultdomain>/VaultService just fine in my browser.

When I try to go to http://<vaultdomain>/VaultService/VaultService.asmx I get nothing. The browser acts like it's waiting for the page to load forever.

Same when I try to log into the Web client at http://<vaultdomain>/VaultService/VaultWeb/login.aspx. Nothing.

The log in /Windows/temp/sgvault ends with our last activity from yesterday. No entries for today despite many login attempts.

Craig

[Beth]

Can you get to the http://<vaultdomain>/VaultService/VaultService.asmx from right on the Vault server?

Open your IIS Manager and see if the website is turned off.

In the IIS Manager, go to Application Pools and make sure that the VaultAppPool is not turned off.

Next, find your IIS Logs. Their location will depend on the OS of the machine.
Windows 2003 IIS Logs: C:\Windows\System32\LogFiles
Windows 2008 IIS Logs: C:\Inetpub\logs\LogFiles

In there you should see some codes that look like 200 0 0. Look for error codes that are not 200 (200 means success). What error codes do you have? Feel free to post the log or to email it to me (support at sourcegear.com).

[craigr]

I cannot get to VaultService.asmx from the browser on the Vault server.

If I'm understanding IIS Manager, the website and the Application Pool for Vault are both running.

The LogFiles folder (Win 2003) has lots of log files. It appears our attempts to access VaultService.asmx are not producing any log entries. If I look at yesterday's log, I see lots of lines like this:

2014-04-14 05:08:40 <server IP> POST /VaultService/VaultService.asmx - 80 - 70.57.222.174 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5477) - 200 0 0

Today there are no lines that mention VaultService.asmx. This is as close as we come:

2014-04-15 16:43:43 <server IP> GET /Default.asp - 80 - <server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) - 302 0 0
2014-04-15 16:43:43 <server IP> GET /VaultService - 80 - <server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) - 301 0 0
2014-04-15 16:43:43 <server IP> GET /VaultService/index.html - 80 - <server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) - 200 0 0
2014-04-15 16:43:43 <server IP> GET /VaultService/sg_logo.gif - 80 - <server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) http://<vault domain>/VaultService/ 200 0 0
2014-04-15 16:43:43 <server IP> GET /favicon.ico - 80 - <server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) - 404 0 2

[Beth]

Make sure the 4.0 items listed in the CGI/Isapi restrictions are enabled (allowed). To do that open IIS Manager - click on the Server name - go to the IIS group in the center and go into CGI & Isapi restrictions - Select the 4.0 .NET framework and click allow in the right pane.

Does that help?

If not, then could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[Beth]

I have received your email. Thanks.

HS: 229955

[Beth]

Update: End result is somehow the 2.0 .NET framework became unregistered and Vault defaulted back to the 1.1. .Net framework. Changed Vault back to 2.0 .Net framework and reregistered the framework with IIS.