Failed to establish a connection to the database...
Moderator: SourceGear
Failed to establish a connection to the database...
Starting about a week ago, we started getting the following entries in the log file:
Critical Error downloading file! Exception of type System.OutOfMemoryException was thrown.
VaultFileUpload.aspx encountered: an exception while copying the request's input stream.Exception of type System.OutOfMemoryException was thrown.
Vault Failed to establish a connection to the database.
System.NullReferenceException: Object reference not set to an instance of an object.
At this point, the system appears dead to the clients. (can't log in) Restarting the server machine will bring everything back up and working again, for generally 2 to 4 days.
Both clients and server are at v3.1.8.
The server is a 2003 box with dual hyper-threading processors, 4 gb ram, 500gb storage, database is approx 56gb, 100 active user accounts, approx 30 active max concurrently.
Mods: changed the 'max pool size' to 200 (about a year ago), changed TreeManagerSize from default to 250 (after first event last week)
Let me know what additional information you need to solve this!
Thanks.
Critical Error downloading file! Exception of type System.OutOfMemoryException was thrown.
VaultFileUpload.aspx encountered: an exception while copying the request's input stream.Exception of type System.OutOfMemoryException was thrown.
Vault Failed to establish a connection to the database.
System.NullReferenceException: Object reference not set to an instance of an object.
At this point, the system appears dead to the clients. (can't log in) Restarting the server machine will bring everything back up and working again, for generally 2 to 4 days.
Both clients and server are at v3.1.8.
The server is a 2003 box with dual hyper-threading processors, 4 gb ram, 500gb storage, database is approx 56gb, 100 active user accounts, approx 30 active max concurrently.
Mods: changed the 'max pool size' to 200 (about a year ago), changed TreeManagerSize from default to 250 (after first event last week)
Let me know what additional information you need to solve this!
Thanks.
Can you look in your server's event viewer for around the same time that you get the out of memory error and let me know if you see any types of errors there?
Try setting the DBBufferSizeKB in your Vault.config to 512 if it's on 256.
When these out of memory errors occur are there any large operations occurring? You might want to check out this KB on delta compression: The TreeDeltaCompresionThreshold option. This is also set in the vault.config file.
Try setting the DBBufferSizeKB in your Vault.config to 512 if it's on 256.
When these out of memory errors occur are there any large operations occurring? You might want to check out this KB on delta compression: The TreeDeltaCompresionThreshold option. This is also set in the vault.config file.
Try each one separately so you can observe what happens for each. Yes, you can do what the article suggests to see if that ends the memory issues. It will help me narrow down exactly what's causing that error.
Is your Vault server in debug mode? If not, set that in the Admin web page and perform an iisreset.
Is your Vault server in debug mode? If not, set that in the Admin web page and perform an iisreset.
After changing only the DBBufferSizeKB to 512 on the 16th, Vault had the OutOfMemory exception again this morning. (I'll email the log files to you Beth) I'm setting the TreeDeltaCompresionThreshold now.
We have purchased the v4.x upgrades, just can't wedge the downtime in among the projects to perform the update yet.
(edit: err, what is your email Beth? Its not in your profile...)
We have purchased the v4.x upgrades, just can't wedge the downtime in among the projects to perform the update yet.
(edit: err, what is your email Beth? Its not in your profile...)
One more setting I'd like you to change. Look for Tree Manager Size and set that to 100 or 50. Then perform an iisreset.
After that setting, if you are still getting memory errors, then I think upgrading will be the next step and I can help you with that. You might be losing more time to the errors than the time needed for an upgrade (you'd have to be the judge of that).
After that setting, if you are still getting memory errors, then I think upgrading will be the next step and I can help you with that. You might be losing more time to the errors than the time needed for an upgrade (you'd have to be the judge of that).