Vault and VS.Net 2005 Issues

ZackJones · Post by **ZackJones** » Mon Jun 12, 2006 8:41 am

Vault server and client versions are 3.1.9 and we had this problem with 3.1.8 as well.

One of our non-local developers is having an issue with Vault and VS.Net 2005. When he tries to do a get latest from VS he gets a series of errors starting with

"Unable to open the web 'http://localhost/SpotBuy'. The Web 'http://localhost/SpotBuy' does not exist." The web does exist and he can load the web site in his browser.

Clicking Ok to that dialog leads to

"Your source control provider encountered an access error. Do you want to switch to working offline in disconnected mode?"

Clicking Yes that dialog leads to

"The current source control operation cannot be completed. The source control plug-in returned the following error: Access failure."

He also sees this error when trying to use the client:

[6/12/2006 8:31:26 AM] Version Check: Your Vault server is version 3.1.9.3798

[6/12/2006 8:31:27 AM] Version Check: The following information was retrieved from the SourceGear website. No information was sent to SourceGear. You can disable this part of the version check from the Options dialog.

[6/12/2006 8:31:27 AM] Version Check: The most recent Vault release is version 3.1.9.3798

[6/12/2006 8:31:46 AM] Getting latest version of $/SpotBuy

[6/12/2006 8:31:49 AM] Finished get latest of $/SpotBuy

[6/12/2006 8:31:49 AM] An exception was encountered during the get latest operation. Exception: Server was unable to read request. --> There is an error in XML document (1, 1023). --> The XML declaration is unexpected. Line 1, position 1027.

I have Vault Server logging in Debug Mode and would gladly email it to you folks if needed.

We have tried removing the offline cache folder and then performing a get latest to see if that will clear things up but it didn't. What other things can we check on the developer's computer? He's the only one having any issues - the rest of the development team can download latest updates. etc just fine.

lbauer · Post by **lbauer** » Mon Jun 12, 2006 8:52 am

Since this is working on other machines, it might be a problem with the bindings. Have the user try unbinding and rebinding.

A similar problem reported here -- perhaps some of the suggestions will help:

http://support.sourcegear.com/viewtopic.php?t=5444

If the user continues to experience difficulty, send us the log file. My email address is linda at SourceGear.com.

ZackJones · Post by **ZackJones** » Wed Jun 14, 2006 10:07 am

Linda,

We're back in business but it wasn't pretty. Developer ended up removing all traces of application from IIS, working folder, cache folder, etc and then was finally to reopen from source using steps outlined in KB article posted in the forum.

lbauer · Post by **lbauer** » Wed Jun 14, 2006 3:45 pm

Sorry it took such drastic measures. Glad he's up and running again, though.

ZackJones · Post by **ZackJones** » Thu Jun 15, 2006 5:17 am

Well things were working until he shut down the computer for the day

. I spent about an hour on the phone with him last night and we enabled client logging using that Ctrl-Alt-Shift-F12 keystroke combo and will be emailing you several log files.

The oddest thing is if he performs a get latest operation with 4 or less files then the operation works. If he tries more than 4 at a time the operation fails.

ZackJones · Post by **ZackJones** » Mon Jun 26, 2006 7:49 am

Linda,

Thanks again for all of your help with this issue. Our developer in FL still continues to have problems and I wanted to point something out to you. We're seeing a lot of 500 errors in the web server logs from /VaultService/VaultService.asmx and /VaultService/VaultFileUpload.aspx

In a daily log file with 2749 lines I've found 220 500 error responses. When this happens shouldn't an error be logged in the Vault log file? The errors showing up in the web server log are from different IP address so the issue isn't limited to a single developer. If you'd like I can email you one of the daily Vault and web logs.

lbauer · Post by **lbauer** » Mon Jun 26, 2006 10:22 am

Yes, we'd like to see the logs. Put Vault logging in debug mode first. Then after the web logs have captured several 500 errors, send the Vault server log and IIS log for the corresponding time period.