Server request timed out on Delete Repository and Obliterate

[jstarbird]

Vault 5.0.1.18729

I'm having a problem deleting a repository and also when I used Obliterate. I've gone through all the posts here that related to the error I get but nothing has worked yet.
Here is what I'm getting:
"A runtime Error has occured. Do you wish to Debug? Line: 5 Error: sys.webforms.pagerequestmanagertimeoutexception: the server request timed out."
When I answer No things will return to normal after I kill the web browser but the Repository is not deleted and the Obliterate does not occur.
I've even tried this on the vault server directly with the same results.

I had my IS guy check the db and that didn't fix things either. As far as server settings:
Session Timout is the default - 10080
IIS upload limit - 102400
and I've tried the DB buffer size from the default of 256 up to 1024.

I've done a import from VSS and that did not have any timeout issues so I'm not to sure what is wrong.


Thanks,
J

[jstarbird]

minor update. The Obliterate finally completed in the background. Seems a bit odd that it took so long, 15 mins, since the folder I was deleting was empty except for one sub folder but neither contained any other content and never has they were just created in error.

[Beth]

Could you post your Vault server log (can be deleted when finished troubleshooting) or send your server log in an email? If you send an email address it to support at sourcegear.com (attn: Beth) with a link to this forum thread.

Delete and Obliterate are two different things. Are you inside the Vault GUI client while you are doing this or inside the Vault admin web page?

[jstarbird]

Update - The Delete Repository request finally came back in the log the other day and it did not succeed. It complained that our db server ran out of space for the transaction log so I'm working with our DBA to work that part out and then I'll try it again. We had allowed a large amount of space but it's filling that up and this is the only thing using Vault at this time as I'm still setting it up.
I will update again or email you the log as soon as I can.

Also you asked about how I was running these, I wasn't aware you could run either of these from the Vault Client UI so I had been running them both from the Admin Web UI directly on the Vault server.


Thanks,
J

[Beth]

You had mentioned delete and obliterate, so where you are running them from tells me which it is. A delete only happens in the client. Obliterate can only happen in the Vault admin web page.

Sometimes it helps to delete in smaller chunks and then obliterate in equally smaller chunks.

[jstarbird]

Beth,
along the way I think you misunderstood me or I wasn't clear. This about Delete Repository and Obliterate not the normal Delete from within the Client UI.

I am still having problems with things failing saying the transaction log is running out of space and since I have to go thru our DBA to work on this it's taking longer to work out than I had hoped.
He tells me there is enough space and doesn't understand why it's giving this error in the Vault log. I've had him try several different settings with no success.

Is there a way for me to delete a repository directly from the db rather than going thru the web ui? I ask as I think this repository has just gotten into a bad state resulting in these issues.


Thanks,
J

[Beth]

There can be plenty of space on disk and still be a limitation placed on the database. We can take this offline so I can take a closer look if you'd like. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[jstarbird]

Beth,
thanks for the reply. As it turns out my DBA wasn't giving me entirely accurate info as our server was low on space. This has been corrected and the Delete Repository functioned correctly. So I apologize for wasting your time on this.

However, for both Delete Repository and Obliterate the web interface still times out even if run on the server itself. Eventually the processes still complete but I have to go back and check as nothing ever comes back to the web page. This is a minor inconvenience.
Based on other postings I have adjusted settings with no effect so far.
This is all with Vault 5.0.1.18729, Windows Server 2003 Sp2 64bit, and IIS 6, web client was IE7.


Thanks,
Jon

[Beth]

You get a timeout, but the operation completes anyway? Or does it not complete when there is a timeout?

In the vaultservice virtual directory is a file called vault.config. In there is a SQL timeout setting that is set to 360 by default. One thing you can try is to add a '0' to the end of that number and save the vault.config. After that, you will need to perform an iisreset by going to Start - Run and typing iisreset. That will disconnect everyone from IIS.

If you can't perform an iisreset, you could instead try recycling the Vault App Pool. To do that, go to your IIS Manager, expand Application Pools, right-click Vault App Pool and select recycle.

Is there any change after changing that setting?

[jstarbird]

Yes only the web times out. I can later pull up admin web interface again and see that the repository is gone or the obliterate worked.

For Vault.config I have set that setting to 3600 already. I have the db buffer size to 1025, and in the web.config file I set the the Connection Timeout to 120 in the connection string.
None of those changes had any effect. I also verified the settings of the App Pool but it is configured as is posted in the knowledge base.



Thanks,
J

[Beth]

db buffer size to 1025

The "sweet spot" for that setting is actually 512.

The settings of the app pool shouldn't have anything to do with this. What I was suggesting was just running a recycle or an iisreset to force IIS to load the settings file again. If it isn't reloaded, the changes aren't used. Did you perform either a recycle or iisreset?

[jstarbird]

Yes I had. I didn't do this today but rather last week and I did cycle the IIS server. Fortunately this IIS server isn't used for anything else and I haven't opened up Vault to our users yet.
Anyway, I had tried that first and the others afterwords with IIS restart after each param change.


Thanks,
J

[Beth]

I'm going to need more information and to collect your full logs. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

What I'll need is for you to place the Vault Server Log into debug mode, reproduce the scenario, note for me the time you reproduced the scenario at, then send the Vault Server Log, a screenshot of the error you see on the web page, and your server Event Viewer logs. It would be better if you can run this most recent test right on the server.

[jstarbird]

Beth,
I am not able to do this at this time. I have begun our migration from VSS to Vault and am now in the middle of importing databases. Once I have us fully setup on Vault, all the db's imported and such, I'll get back to this. I need to get the imports done now while we have a lull in our development cycle.
If after that work is complete I am still having a problem I will get back in touch and reference this thread.


Thanks,
J

[Beth]

Thanks for the update. I can work around whatever timeline you have.