April 7, 2004 at 8:48 am
I'm running SQL Server 2000 and this morning started receiving the following error when attempting to manually run jobs:
From Microsoft SQL-DMO (ODBC SQLState 42000)
Error 22022: Unable to post notification to SQLServerAgent (reason: MapViewOfFile() returned error 8, 'Not enough storage is available to process this command.')
It is only jobs started manually that have a problem, scheduled jobs run fine. The server has 2.5GB of RAM. A total of 2GB of RAM is in use with SQL Server using 1.8GB, so there is plenty of memory available. The disk drive with the least free space has 4GB free.
I don't know if they are related (but I suspect they are), but earlier this morning we also started getting the following error when attempting to send mail via CDOSYS:
Error setting Message configuraton field "smtpserver". [SQLSTATE 01000] (Message 0) ODSOLE Extended Procedure [SQLSTATE 01000] (Message 0) Error loading type library/DLL. [SQLSTATE 01000] (Message 0).
The database configuration has not changed recently and I'm at a loss as to what the problem could be. Any help is greatly appreciated.
Thanks,
Dave
April 12, 2004 at 8:00 am
This was removed by the editor as SPAM
May 10, 2004 at 4:57 am
I'm afraid I don't have any answers to this question; I am experincing the same error myself. I wonder if this problem is related to the other problem I am having on my SQL Server at the moment (http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20946416.html)
You suspect your problem is related to CDOSYS, whereas I suspect my problem is related to ADO. To fix my problem, I need to stop and restart my SQL Server services, then it all works ok for a few days. Does this work for you also?
May 10, 2004 at 9:56 pm
I restarted SQL Server later within a day or two of my post, so it's now been running about a month with no problems.
Dave
August 10, 2005 at 5:17 am
Are you using linked servers. it could be that third party drivers (oracle etc.) use memory from the sql server proces. you can fix using following:
"HKLM\Software\Microsoft\Mssqlserver\providers\MSDAORA" and set the value for "AllowInProcess" to 0
regards,
March 3, 2008 at 3:27 am
change the SQL Server Audit level setting to failure or none only, then restart the SQL Server. Thats it.
May 25, 2011 at 2:45 pm
Restarting the SQL Engine fixed if for me...not that there is an answer there, but it worked.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply