Check In Fails Consistently

beanmf · Post by **beanmf** » Tue Jun 28, 2005 11:16 am

Vault 2.0.0 (cannot update on server). Has been working for years now. My proxy password has changed but I reset this by deleting the registry encrypted value and restarting Vault client to get the proxy authentication window. Connect and retrieve repository always works. Check out and uncheck out work generally but sometimes fail. Check in always fails: connects, begins transaction, but then I get "Session is no longer valid. Either the server restarted or your session timed out. You must login again to re-authenticate." I suspect the error is erroneous - something else is going wrong.

lbauer · Post by **lbauer** » Tue Jun 28, 2005 11:22 am

You probably cannot add files, either. Some other settings may have changed.

See this KB article about troubleshooting this:
http://support.sourcegear.com/viewtopic.php?t=735

beanmf · Post by **beanmf** » Tue Jun 28, 2005 11:46 am

As the VaultService is on a .Net hosting server far away, I have very limited access to make changes. For example, it is nearly impossible for me to view the log files except by ftp which is turned off in our company.

I am the only user and have made no settings changes. What might have happened to cause the check in process to change. The only thing I can think of is that there is a problem on the server (I had the app pool reset) or a change in our coporate firewall (unlikely but nearly impossible to resolve). Can you help with more specific suggestions if possible?

beanmf · Post by **beanmf** » Tue Jun 28, 2005 12:01 pm

I was able to add a file to the repository and then delete it (although I had the same connection dropped error on first attempt to delete).

I think I just succeeded in checking in (sort of). The file uploaded, transaction completed, retrieved the repository again, and then I got the connection dropped message again. Upon reconnecting, I notice that the file in question is now renegade, as if Vault realizes that it is out of synch - could this be some tag on the client computer?

Might this be an overloaded server (e.g. timeout)?

lbauer · Post by **lbauer** » Tue Jun 28, 2005 12:34 pm

First, let's eliminate possible client-side issues:

If the registry was edited, something could have changed the setting for Chunked Encoding.

This is one of the suggestions in the troubleshooting link I sent earlier. Please review this and verify that DontUseChunkedHTTPTransfers is set to True:
http://support.sourcegear.com/viewtopic.php?t=78

If Vault has been working with no problems, and nothing was changed on the client side, then changes must have been made elsewhere.

You mentioned you had to change your proxy password. Could other changes have made to the proxy/network?

If you are indeed getting server timeouts, then it could be due to IIS recycling:

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

beanmf · Post by **beanmf** » Wed Jun 29, 2005 2:20 pm

Client-side issues: >> Chunked Encoding checked OK

Proxy issues: Could other changes have made to the proxy/network? >>I have no way to tell really.

Server issues: if you are indeed getting server timeouts, then it could be due to IIS recycling: >> I don't think recycling happens every 20 seconds. I DO begin to think it is server side though as now I cannot even see the repository reliably, getting "Session is no longer valid. EIther the server restarted, or your session timed out. etc." I remember there was a timeout setting somewhere; could I try changing that perhaps (server side changes are very difficult to make as I have no control over the servers which are 3500 miles away).

lbauer · Post by **lbauer** » Wed Jun 29, 2005 2:37 pm

Is it possible for you to get a copy of the sgvault.log file? It's on the server machine in the Windows\Temp\sgvault directory. It may give us more information so we can suggestion additional things to try.

Email the log to linda at SourceGear.com. Be sure to reference this post in your email.

beanmf · Post by **beanmf** » Fri Jul 01, 2005 10:05 am

sgvault.log file emailed earlier.

Hosting support tells us:"
These are the patches applied over the last week
Windows Server 2003 family Windows Server 2003 Service Pack 1 Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Windows Malicious Software Removal Tool - June 2005 (KB890830) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB890046) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Cumulative Security Update for Internet Explorer for Windows Server 2003 (KB883939) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Cumulative Security Update for Outlook Express for Windows Server 2003 (KB897715) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896358) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896422) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896428) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB893066) Monday, June 27, 2005 Windows Update website
Windows Security Update for Windows SharePoint Services (KB887981) Wednesday, June 08, 2005 Windows Update website

I ran the tests from the server and could see it error out. But the error message are filter and I was unable to see stack trace information. Can you ask the vendor how to see the error stack trace ?"

CAN WE TURN ON A MORE VERBOSE STACK TRACE?
IS THIS SERVER PATCH KNOWN TO BE OK?

lbauer · Post by **lbauer** » Fri Jul 01, 2005 10:47 am

The log shows Vault server was restarting every 10 minutes for the past few days and every few minutes yesterday. That could explain the problem:

----6/30/2005 5:50:13 PM sgvaultsystem--()--
System Started
----6/30/2005 5:50:37 PM sgvaultsystem--()--
System Started <snip>
----6/30/2005 5:51:47 PM sgvaultsystem--()--
System Started <snip>
----6/30/2005 5:52:54 PM sgvaultsystem--()--
System Started <snip>

It could be due to a configuration in IIS 6 on the server machine.This KB article discusses how to configure IIS recycling time:

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

If that doesn't help, you need to consult with your hosting provider on why the aspnet process is restarting so often.

Post by **jeremy_sg** » Fri Jul 01, 2005 8:42 pm

Some things to note when it seems like the Vault server is restarting for every request.

1. I've had success with configuring IIS to run in 5.0 isolation mode to solve this problem. http://support.sourcegear.com/viewtopic.php?t=2314

2. If sharepoint is installed on the same box, it could seriously interfere with Vault's session management. The official recommendation is to create a new web site, in a new directory (not in inetpub), and install the Vault web service in the new web site and the new directory.

beanmf · Post by **beanmf** » Tue Jul 05, 2005 8:18 am

"2. If sharepoint is installed on the same box, it could seriously interfere with Vault's session management. The official recommendation is to create a new web site, in a new directory (not in inetpub), and install the Vault web service in the new web site and the new directory."

The recycle time is 12 hours, so that is not the problem. The list of patches included a sharepoint patch, so that could be it. My question is - if it was working fine 3 weeks ago, why has it suddenly started acting differently. I have no control over what is installed on the box as it is a commercial server.

lbauer · Post by **lbauer** » Tue Jul 05, 2005 8:25 am

These are the patches applied over the last week
Windows Server 2003 family Windows Server 2003 Service Pack 1 Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Windows Malicious Software Removal Tool - June 2005 (KB890830) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB890046) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Cumulative Security Update for Internet Explorer for Windows Server 2003 (KB883939) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Cumulative Security Update for Outlook Express for Windows Server 2003 (KB897715) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896358) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896422) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB896428) Monday, June 27, 2005 Windows Update website
Windows Server 2003 family Security Update for Windows Server 2003 (KB893066) Monday, June 27, 2005 Windows Update website
Windows Security Update for Windows SharePoint Services (KB887981) Wednesday, June 08, 2005 Windows Update website

These security updates may have changed some permissions on the machine, reset some configurations, changed something in Sharepoint.

You are in a difficult position with no control of the server side, since the server is the "heart and brains" of Vault.

Is there any way you can find out if Sharepoint is installed on the Vault server machine? And if it is installed, could you get Vault Server reinstalled per our Sharepoint recommendations?

beanmf · Post by **beanmf** » Thu Jul 07, 2005 10:35 am

Our host's reply is: "sharepoint has always been installed on the server, before the error occurs. Did sourcegear suggested the way to see the applicate error ?

chris:
I ran the tests from the server and could see it error out. But the error message are filter and I was unable to see stack trace information. Can you ask the vendor how to see the error stack trace ?"

lbauer · Post by **lbauer** » Fri Jul 08, 2005 11:17 am

The Sharepoint updates could have changed things. Sharepoint often overrides values in the web.config file of other apps, like Vault.

One thing you could try is to add the following to the Vault web.config file in the <system.web> section (default location of the web.config file is C:\Inetpub\wwwroot\VaultService):

<httpModules>
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule"/>
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
<add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule"/>
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule"/>
<add name="PassportAuthentication" type="System.Web.Security.PassportAuthenticationModule"/>
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule"/>
<add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule"/>
<add name="ErrorHandlerModule" type="System.Web.Mobile.ErrorHandlerModule, System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</httpModules>

Some of these may cause things to fail with a message about "duplicates." Take out duplicates in the web.config until it works again.

If that doesn't work, you may need to reinstall Vault, using these guidelines for servers with Sharepoint.

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

Regarding the stack trace -- what test was run? What was the error message, and where did it come from? Are you Chris?

Guest · Post by **Guest** » Fri Jul 08, 2005 11:43 am

Ok, I will do that this weekend. I am Mark and I think Chris is one of the server support folks at my hosting service.

"Regarding the stack trace -- what test was run? What was the error message, and where did it come from? " I don't know the answer to any of these, but assume they are able to see some errors (perhaps in the Vault log?) and wanted more detailed information. I believe Vault log is set to be detailed. Let's try your suggestion first. I really do NOT want to reinstall Vault. The hosting service does NOT run msi installers on their servers by policy. I have never really understood why we can't just copy the files to the server - something most hosting companies will accept. Actually, I wasn't the one who originally installed Vault, it was someone who used to work for me, and I know he had lots of problems, so I would like to avoid doing that.