GUIClient and Command line clients hang on EndDownloadFiles

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
evermeire
Posts: 4
Joined: Wed Sep 26, 2007 10:40 am

GUIClient and Command line clients hang on EndDownloadFiles

Post by evermeire » Wed Sep 26, 2007 10:50 am

I am able to successfully login and am presented with the "Choose Repository" dialog window. Once I select the "Available Repository", the GUI client's status message displays the following:

"Retrieving repository structure information from the server..."

The client becomes unresponsive at this point. I can't even "Abort Current Operation". I have to kill the VaultGUIClient.exe process.

I enabled logging and my VaultGUIClient.txt log file has the following last dozen entries or so.

9/26/2007 9:43:01 AM <refresh>: [GUIClientWorkerThread:2044] Refresh started
9/26/2007 9:43:01 AM <refresh>: [GUIClientWorkerThread:2044] delta passed in was null, retrieving one
9/26/2007 9:43:01 AM <refresh>: [GUIClientWorkerThread:2044] calling GetRepositoryStructure(2, 0, -1, ref, 7/1/1850 12:00:00 AM)
9/26/2007 9:43:01 AM <refresh>: [GUIClientWorkerThread:2044] GetRepositoryStructure started
9/26/2007 9:43:01 AM <refresh>: [GUIClientWorkerThread:2044] Calling client service GetRepositoryStructure(2, 0, -1, 7/1/1850 12:00:00 AM, ref, ref, ref)
9/26/2007 9:43:04 AM <refresh>: [GUIClientWorkerThread:2044] Client service GetRepositoryStructure returned: dtLatestCheck 9/25/2007 11:18:59 AM, nReturnDestRevision 17264, rd not null True
9/26/2007 9:43:04 AM <refresh>: [GUIClientWorkerThread:2044] We got a compressed delta we have to download, getting download file stream
9/26/2007 9:43:04 AM <refresh>: [GUIClientWorkerThread:2044] Get download file stream and response stream
9/26/2007 9:43:04 AM <refresh>: [GUIClientWorkerThread:2044] Reading delta from stream
9/26/2007 9:43:05 AM <refresh>: [GUIClientWorkerThread:2044] Completed reading delta from stream, calling EndDownloadFiles


I have uninstalled/reinstalled the Vault client, rebooted, etc. Windows Firewall is not enabled. I am able to view all the SOAP web service methods and see their descriptions, via the page
http://<ourvaultserver>/vaultservice/vaultservice.asmx

This also returns its description.
http://<ourvaultserver>/vaultservice/vaultservice.asmx?op=EndDownloadFiles

Everything was fine just a day ago. The last thing I did with the Vault Client before having problems was attempting to creating a subdirectory. It said beginning transaction and then froze. I have done an iisreset on the vault server, restarted SQL server, there are no open transactions that DBCC opentran reports.

My Vault account works fine on other client machines. Other vault accounts to not work on my machine. The problem is isolated to just my machine. I am running Windows 2003 SP2 Standard Edition. The Vault Client 2.0.6 (2219)

Any ideas?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Sep 26, 2007 11:00 am

Could you try Clearing Your Client Side Cache? I would recommend keeping the cache item 'CacheMember_WorkingFolderAssignments,' but you can remove everything else.

evermeire
Posts: 4
Joined: Wed Sep 26, 2007 10:40 am

Post by evermeire » Wed Sep 26, 2007 11:41 am

Thanks for the speedy reply.

I deleted all the files in

C:\DOCUME~1\ericv\Application Data\SourceGear\Vault_1

and I still have the same problem.

evermeire
Posts: 4
Joined: Wed Sep 26, 2007 10:40 am

Post by evermeire » Wed Sep 26, 2007 11:57 am

Using Netmon 3.0, the last get/response headers look like.

1) GET Request
----------------
Frame:
- HTTP: Request, POST /VaultService/VaultService.asmx
Command: POST
+ URI: /VaultService/VaultService.asmx
ProtocolVersion: HTTP/1.1
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.2407)
ContentType: text/xml; charset=utf-8
SOAPAction: "http://www.sourcegear.com/schemas/vault ... nloadFiles"
ContentLength: 571
Expect: 100-continue
Host: vault
Cookie: ASP.NET_SessionId=zxdhvx3f2f1zi255iaufpx55; _authHdr=25a94b52-18b0-440e-8731-6e96ee4a5d0dBu2/tdPWzF4VTxBtFB++Ng==
HeaderEnd: CRLF

2) Response
- HTTP: Response, HTTP/1.1, Status Code = 100
ProtocolVersion: HTTP/1.1
StatusCode: 100, Continue.
Reason: Continue
Server: Microsoft-IIS/5.0
Date: Wed, 26 Sep 2007 17:52:51 GMT
X-Powered-By: ASP.NET
Server: vault
HeaderEnd: CRLF

4) Followed by a http payload response.
- HTTP: HTTP Payload
- HTTPPayload: <?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 ... <VaultAuth xmlns="http://w
- payload:
- HttpPayLoad:
Data: <?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 ... <VaultAuth xmlns="http://www.sour

4) This is the last HTTP traffic, another response.

- HTTP: Response, HTTP/1.1, Status Code = 200
ProtocolVersion: HTTP/1.1
StatusCode: 200, Ok
Reason: OK
Server: Microsoft-IIS/5.0
Date: Wed, 26 Sep 2007 17:52:51 GMT
X-Powered-By: ASP.NET
Server: vault
X-AspNet-Version: 1.1.4322
Cache-Control: private, max-age=0
ContentType: text/xml; charset=utf-8
ContentLength: 397
HeaderEnd: CRLF
- HTTPPayload: <?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 ... esResponse xm
- payload:
- XmlPayload:
ㄢ•潣杮瑵∸猼㩰敶数汭猺㵰瑴⼯敨⹳獬⹰⽧灡癮灯•湬獸栢㩰睷㍷杲〰䵘档ⵡ瑳散浸㩳㵤瑴⼯⹷漮㈯⼱卌浥㰾灡摯䔼潄潬楆剳潰⁥湬栢㩰睷潳散牡浯档獡畡㸢摮湷摡敬獥㹴䔯潄潬楆剳汵⼼䑤汮䙤獥灳敳猯㩰祤猯㩰敶数

evermeire
Posts: 4
Joined: Wed Sep 26, 2007 10:40 am

Post by evermeire » Wed Sep 26, 2007 12:26 pm

Well, now it works. I can't believe it. I changed nothing. In addition to packet sniffing with NetMon 3.0, I fired up Fiddler so I could see the entire request/response, instead of looking at individual frames. The then reloaded the Vault Client and was unable to communicate at all with the vault web service (not sure why, confirming if anyone in Operations reset the web site), but on about the 4 attempt, it connected and retrieved the repository.

No idea how to repro the problem I had now. Thanks for you help.

Post Reply