FailDeltaApply

[ICOM]

I'm going to try re-installing 3.5.0.4741 here, to see if that makes a difference. Do you have a 3.5.1.4786 server set up that we could connect to?

[ICOM]

So far I have been unable to break the combination of 3.5.1.4786 Client with 3.5.0.4741 Server.

[lbauer]

Interesting. Not sure why that would make a difference, unless a new server-side cache is created by the new installation . . .

[ICOM]

That wouldn't explain why the previous re-install and completely separate server install worked correctly though.

My current theory is that there's a MS update for both W2k and W2003 or SQL 2k and 2005 or for .NET that breaks 3.5.1.4786 server in some way.

That would explain both why it worked continuously before, and then failed on multiple machines simultaneously.

I'll keep you up to date if 3.5.0.4741 starts breaking on me too.

[jclausius]

Also note, I installed Vault Server 3.5.1 on vaultdemo.sourcegear.com as well as ran Windows Update to make sure all patches were applied.

Here is the info collected from a client connected to vaultdemo -

Server Information:
- Vault Server Version: 3.5.1.4786
- .Net Framework Version: 1.1.4322.2032
- Operating System: Microsoft Windows 2000 Server

[ICOM]

Well, that hope was shortlived.

I just got the same error with 3.5.0.4741 on one server. Trying with the other one hasn't killed it yet.

[ICOM]

For some reason the w2k server is standing up well with 3.5.0.. It'll be nice if it stays that way.

[ICOM]

So far so good.. I've thrown some massive commits to it with no issues.. I wonder why this one is staying working while the w2003 server isn't.

[jclausius]

Does your Windows 2003 Server have .Net 1.1 as well as .Net 2.0?

I don't have an explanation, but we've encountered some instances when IIS 6.0 is configured to run Vault with the .Net Framework 1.1 things seem to "work" a bit better.

Although I don't think that fully explains the situation you're seeing.

[ICOM]

Yes, and in fact Vault seems to use 1.1 by default (since I haven't changed it manually).

Setting it to use 2.0 didn't result in it magically starting to work either.

If you have any other suggestions, I'd love to hear them. We're kind of overtaxing the win2k server at the moment, and would much prefer to moving things back to the original machine.

[jclausius]

You may want to experiment on the VaultService virtual directory.


Some things you may want to try:

Setting the ASP.Net version on the virtual directory's properties to one version or another and then restarting IIS solves the problem.

Removing / re-creating the Application within the property page does the trick. Although I don't remember if this is only restricted to IIS 5.0.

Re-creating the Vault Application Pool configuration and resetting the virtual directory can help.

Re-registring the specific .Net Framework version ("aspnet_regiis /i"), disallowing and allowing the specific .Net Framework version.

[breischl]

I just ran into this same problem with client 3.1.9.3798 and server 3.1.6.3658.

Any resolutions for this yet?

[jclausius]

Did a new .Net Framework just get installed? If so, make sure IIS is using .Net Framework 1.1 w/ Vault 3.x.

[breischl]

Nothing changed on the client or server.

I was able to get the file to update from another client machine with the same setup.

[jclausius]

It could be the baseline file (in the _sgvault directory) was modified by some other application besides Vault.

Has the file been modified? If not, what happens if you try a different working folder?