July 1, 2008 at 7:59 am
After upgrading a bunch of servers from SQL 2000 to SQL 2005, SP2, I get the following message from the SQL server agent when trying to modify a job schedule with script.
I've found other posts here and at Microsoft saying this could be caused by MSDB or tempdb running out of disk space, but that is not my case...I've got them both set to autogrow with no limit, and there is on the order of 20GB at least on the disks in question.
Bouncing the services seems to fix the problem, but it comes back after a day or so.
Any other ideas I should try?
Executed as user: dbo. Unable to post notification to SQLServerAgent (reason: MapViewOfFile() returned error 8, 'Not enough storage is available to process this command.') [SQLSTATE 01000] (Message 22022). The step succeeded.
The Redneck DBA
July 1, 2008 at 8:15 am
Try the link below
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=301902&SiteID=1&pageid=0
Regards..Vidhya Sagar
SQL-Articles
July 1, 2008 at 8:20 am
Thanks. It suggests in that post to "defragment your virtual memory". Anyone know how to do that?
The Redneck DBA
July 1, 2008 at 8:26 am
your SQL Server Agent Job log is probably full.
or else
try to restart the server or the sql servcice it may work.:D
July 1, 2008 at 8:28 am
anjan.ashok (7/1/2008)
your SQL Server Agent Job log is probably full.or else
try to restart the server or the sql servcice it may work.:D
The log isn't full.
restarting services does help, but has to be done every day, and that is not a good thing to do for a production environment.
The Redneck DBA
July 2, 2008 at 7:53 am
Our network gury finally called Microsoft. We were also having other issues on some of the servers. Turns out all we needed to do was rebuild every index on every table, and all sorts of issues went away. Guess it doesn't automatically do that when you upgrade.
The Redneck DBA
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply