August 13, 2003 at 6:44 am
I just got an error while trying to connect to my production SQL Server (2000) on Windows NT 4 that says CryptoAPI function "CryptAcquireContext" failed.
Our hosting facility rebooted the box and it is back now up and running, but I checked the error logs and 10 minutes before we started getting that error there was a log entry for "Warning: The available page file space has dropped below 4Mb."
Anyone else experienced this? I don't quite understand what happened but want to know how I can prevent it from occurring again.
Thanks
Edited by - cross on 08/13/2003 07:37:49 AM
August 14, 2003 at 2:23 am
I guess your server was running out of (virtual) memory. And the CryptoAPI function needed more than was available. This could be a memory leak in some application or just one of the applications needed a lot of memory.
You should check with your hosting partner if they run any traces about memory consumption of different processes. If not, they should consider starting one until the problem has been resolved.
A temporary workaround could be to increase the page file size on the server. But sooner or later you will bump into the same problem again...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply