Connection error

tmilton · Post by **tmilton** » Wed Dec 09, 2009 3:09 pm

I have Vault version 5.0.2(18753) loaded on server and client.
When I try to connect to my sever I get this error.

Unable to connect to http://192.168.1.3/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>

--.

Thanks
Tim

lbauer · Post by **lbauer** » Wed Dec 09, 2009 3:54 pm

Is this a new error? Was Vault working before?

If Vault was working properly before, did you recently install any Windows Updates?

Are there any errors in the Vault Server log that correspond to the failure? It's called sgvault.log and is in %windir%\temp\sgvault on the server machine.

Any error in the Event Viewer that might be related?

tmilton · Post by **tmilton** » Thu Dec 10, 2009 9:29 am

No we have been working for a long time with no problems. We where on version 5.0.2(18729) and I found out Vault was upgraded last week (12/2) to the new 18753 version and was working fine until 12/09.

The server does automatic update every night at 3AM..

So there could have been an update.

There are no errors in the log file, this is what in the log file.

----12/8/2009 2:51:56 PM sgvaultsystem--()--
System Started
Version 5.0.2.18753
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = NT AUTHORITY\NETWORK SERVICE

When I run the Admin Web Client I also get this error.

HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.
Internet Information Services (IIS)

Thanks
Tim

sbalki · Post by **sbalki** » Thu Dec 10, 2009 11:57 am

I too have experienced a long lived working installation (2 days short of 1 year maint expiring!

) I know for a fact that windows update installed 7 updates yesterday.

Do I just try to uninstall each KB until I find the culprit?

Code: Select all

Windows Server 2003 Update for Windows Server 2003 (KB955759)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Security Update for Windows Server 2003 (KB974392)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Cumulative Security Update for Internet Explorer 7 for Windows Server 2003 (KB976325)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Update for Windows Server 2003 (KB973917)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Update for Windows Server 2003 (KB971737)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Security Update for Windows Server 2003 (KB973904)  Wednesday, December 09, 2009 Automatic Updates  
Windows Server 2003 Security Update for Windows Server 2003 (KB974318)  Wednesday, December 09, 2009 Automatic Updates

Here is the only information I can find on the problem:

Code: Select all

Event Type:	Warning
Event Source:	W3SVC
Event Category:	None
Event ID:	1009
Date:		12/10/2009
Time:		11:33:31 AM
User:		N/A
Computer:	C31672-103491
Description:
A process serving application pool 'VaultAppPool' terminated unexpectedly. The process id was '6172'. The process exit code was '0xffffffff'.

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

I go in to IIS and start the VaultAppPool and if I try to connect to webadmin or thru gui client, the app pool fails and stops.

(Should I have started a new thread?)

sbalki · Post by **sbalki** » Thu Dec 10, 2009 2:30 pm

(This post to help forum lurkers!)

Two of those updates (KB973917 & KB971737) had to do with "strengthening authentication credentials", so I uninstalled them. The uninstall process recommended that I also uninstall KB955759, KB974392 and KB976325, so I did.

After a reboot, Vault is working again.

FYI,
This morning, I did uninstall Vault (5.0.1.18729) and install the current version (5.0.2.18753) to try and fix this error, which did not help.

lbauer · Post by **lbauer** » Thu Dec 10, 2009 3:14 pm

A recent Microsoft update, KB973917 adds "extended protection for authentication." Unfortunately, IIS becomes so protected that the Vault App Pool is disabled. See this link for details.
http://support.microsoft.com/?kbid=973917

We're trying to reproduce the problem by downloading the update, but haven't experienced the problem yet. From the KB article, it looks like you might be able to make a registry change to turn off the "protection."

In the meantime, users can uninstall the update to get Vault/Fortress working again.

Beth · Post by **Beth** » Thu Dec 10, 2009 3:22 pm

I wanted to add results from a user I spoke to that appeared to have a similar issue. That user resolved their issue by rebooting their server and in addition, recycling their Vault App Pool.

sbalki · Post by **sbalki** » Thu Dec 10, 2009 3:41 pm

Would it help to reproduce on my server? Do you want a remote connection?

tmilton · Post by **tmilton** » Fri Dec 11, 2009 8:10 am

I’m working again.
I uninstalled the update that sbalki posted and rebooted the server.
Thanks for the help

lbauer · Post by **lbauer** » Fri Dec 11, 2009 9:54 am

According to Microsoft, the update causes a problem on Windows Server 2003 SP 2 with Service pack 2.

To resolve this problem, reinstall Service Pack 2 for Windows Server 2003 on the web server. This will bring all IIS 6.0 components up to the correct file versions, and will maintain the installation of the KB973917 update. Reinstalling the KB973917 update should not be necessary.

See the full Microsoft KB article explaining the problem:

http://support.microsoft.com/kb/2009746

SourceGear Support

Connection error

Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error

Re: Connection error