I think I've screwed the team using Vault, please help :)

[Marcie]

So, first a little background. I tend to keep the Vault Client app open all the time, as I used to do with SourceSafe. However unlike VSS, the Vault client occasionally tells me, sorry, you've been timed out/logged out. Today I grew tired of this, and decided to go hunting for a setting that would allow me to extend this timeout. I fire up the Vault Server (currently is my same machine) Admin tool, and find something called timeout. I add a couple of zeroes to it, and hit Apply.

Now, whenever I, or any of my team mates, try to open the Vault Client, or work with it from within VS.NET, we just get a big error box, the gist of which is:

"Specified argument was out of the range of valid values.
Parameter name: slidingExpiration"

I also get that error when I try to amend the error of my ways and reenter the Vault Admin tool. So I'm screwed.

Please advise. (Any suggestions are appreciated).
Marcie

[dan]

Ouch. We need to provide better error checking there.

Go to the web.config file in your VaultServices folder (usually c:\inetpub\wwwroot\VaultService) and find the timeout value in the sesssionState element, and bump it up to something more reasonable

If you keep getting logged out, it is likely you have an IIS setting that recycles the Vault server, or disconnects connections at shorter time intervals than the 72 hour vault default, or there is a firewall or proxy between you and the Vault Service timing you out.

[Marcie]

Thanks Dan, that did the trick. (Yeah, some validation on that prop. would probably be good )

Next I'll try to figure out my IIS timeout issue, I don't think it could be a firewall thing because they're literally the same machine.

Thanks!!
Marcie

[bsapd]

There is a similar error when you change the IIS Max Upload setting beyond the maximum allowed value. The Admin tool crashes and then IIS bombs and locks everyone out. Its easy enough to fix, but the admin tool should probably trap this error from occurring.

[Evaluator]

There is a similar error when you change the IIS Max Upload setting beyond the maximum allowed value. The Admin tool crashes and then IIS bombs and locks everyone out. Its easy enough to fix, but the admin tool should probably trap this error from occurring.

hi, i experienced "max upload" crashes this week too. that's more than a year later than previous post - wot's the story? is this really, really hard to fix or something?

[dan]

Can you elaborate on what you are seeing, and which version of Vault you are running?

In 3.1.1, if you enter a very large value in the IIS FIle Upload Limit in the admin tool Server Options pane, it will display an error, and not let you change it, and I believe this has been the case for awhile.

Thanks,

[Evaluator]

There is a similar error when you change the IIS Max Upload setting beyond the maximum allowed value. The Admin tool crashes...

hi, i experienced "max upload" crashes this week too. that's more than a year later than previous post - wot's the story? is this really, really hard to fix or something?

In 3.1.1, if you enter a very large value in the IIS FIle Upload Limit in the admin tool Server Options pane, it will display an error, and not let you change it, and I believe this has been the case for awhile.

Yes, you're right. Sorry, my mistake. The crash I had was after an error message was displayed, so it must be that the problem mentioned by bsapd is fixed already.

[dan]

That's good to hear. Let us know if you need further assistance.