Hello. I've been having issues doing a get latest on files from either the Vault client or the Vault API. It seems to happen when doing a recursive get latest on large number of files. When I do this through the Vault client, it starts getting files then errors out. It does get a fair number of the files, but not all of them. The error that's seen in the Vault client is:
3/20/2009 9:16:29 AM] An exception was encountered during the get latest operation. 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><span style="font-family:Verdana;color: #ff3300">Server Application Unavailable
</span></h1>
<p>
<span style="font-family:Verdana;">
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.
</span></p>
<p>
<b>Administrator Note:
</b> 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.
</p>
</body>
</html>
Additionally, when I run a tracing tool against the Vault client I get these messages:
POST /VaultService/VaultService.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.3082)
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.sourcegear.com/schemas/vault/GetRepositoryStructure"
Host: sourcegear
Cookie: ASP.NET_SessionId=0r4au145tz4ktyee1vvjsjyo
Content-Length: 891
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue
Server: Microsoft-IIS/5.0
Date: Fri, 20 Mar 2009 14:27:02 GMT
X-Powered-By: ASP.NET
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><VaultAuth xmlns="http://www.sourcegear.com/schemas/vault"><Token>8bd924a7-1df5-4f17-87f1-5474678206celFmlBcamzSbt/8pcesVWrA==</Token></VaultAuth></soap:Header><soap:Body><GetRepositoryStructure xmlns="http://www.sourcegear.com/schemas/vault"><nRepID>30</nRepID><nBaseRevision>869541</nBaseRevision><nTargetRevision>-1</nTargetRevision><dtLastClientSecurityCheck><Ticks>633722124149000000</Ticks></dtLastClientSecurityCheck><dtLatestServerSecurityCheck><Ticks>583644276000000000</Ticks></dtLatestServerSecurityCheck><nReturnTargetRevision>-1</nReturnTargetRevision><bUseDBDeltaOnCacheMiss>true</bUseDBDeltaOnCacheMiss></GetRepositoryStructure></soap:Body></soap:Envelope>
HTTP/1.1 500 Internal Server Error
Server: Microsoft-IIS/5.0
Date: Fri, 20 Mar 2009 14:27:02 GMT
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 372
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>1011 : FailInvalidSessionToken</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>
When I try getting the same files via the Vault API (which is what I'm really trying to do) I see these same messages in the tracing tool I'm using. So it seems like doing a get latest on a largeish number of files is crashing the Vault service. I'm trying to get my hands on some logs from the Vault server itself, and I can provide them as soon I get them. In the meantime, have you seen any issues like this, where getting latest on a large number of files crashes the service? It's 169,000 files, or about 5.5 GB of data.
I'm using version 4.1.3.18336 of the Vault client and service.
Errors getting files from Vault client and Vault API
Moderator: SourceGear
Re: Errors getting files from Vault client and Vault API
I don't know that large gets would "crash" Vault server, but we'll need see a copy of the The Vault server log to see what's happening on the server end.
Send the logs zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Send the logs zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager