I tried to manually start a job from Enterprise
Manager and got
' Error 22022: Unable to post notification to SQL
ServerAgent (reason: MapViewOfFile() returned error
8, 'Not enough storage is available to process this
command')

This happens quite often. Every time I have to re-start
the server to work around it.

Any suggestion?

Thanks!

[ Post a follow-up to this message ]

Haven't seen this error before. It's just a guess from my side that may be
the system drive or the sql server installation drive is running out of
space?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/


"Mike" <anonymous@discussions.microsoft.com> wrote in message
 news:29b6901c465c0$31e3b7b0$a501280a@phx
.gbl...
> I tried to manually start a job from Enterprise
> Manager and got
> ' Error 22022: Unable to post notification to SQL
> ServerAgent (reason: MapViewOfFile() returned error
> 8, 'Not enough storage is available to process this
> command')
>
> This happens quite often. Every time I have to re-start
> the server to work around it.
>
> Any suggestion?
>
> Thanks!

[ Post a follow-up to this message ]

quote:
Originally posted by Narayana Vyas Kondreddi 
Haven't seen this error before. It's just a guess from my side that may be
the system drive or the sql server installation drive is running out of
space?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/


"Mike" <anonymous@discussions.microsoft.com> wrote in message
 news:29b6901c465c0$31e3b7b0$a501280a@phx
.gbl...
> I tried to manually start a job from Enterprise
> Manager and got
> ' Error 22022: Unable to post notification to SQL
> ServerAgent (reason: MapViewOfFile() returned error
> 8, 'Not enough storage is available to process this
> command')
>
> This happens quite often. Every time I have to re-start
> the server to work around it.
>
> Any suggestion?
>
> Thanks! 
 

Has anyone cracked this problem, as we are experiencing same issue?  Thanks

[ Post a follow-up to this message ]

I just helped somone else with this same error.  They found that the
SQL Server Agent Job log was full.

[ Post a follow-up to this message ]