This means you have more then 128 outstanding notifications, which can mean
you either can not process requests fast enough, which can happen if you
have a huge number of parallel jobs and did not adjust the sub system worker
thread limits. An other case where I have seen this happen is when people
had tight xp_sqlagent_enum_jobs or sp_help_job in a tight lopp, which blocks
the shared memory between the SQL Server and SQL Agent.
Post or email your SQLAgent.OUT file, there will be more clues in there I
hope, which one of the two cases. Make sure you are running with verbose
logging on, otherwise you might be missing out on a lot of information.
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright ? SQLDev.Net 1991-2002 All rights reserved.
> Lately many of my jobs fail reporting the following error
> "The maximum number of pending SQLServerAgent notifications has been
> exceeded. The notification will be ignored. [SQLSTATE 01000] (Message
> 22022) Unable to post notification to SQLServerAgent (reason: The maximum
> number of pending SQLServerAgent notifications has been exceeded. The
> notification will be ignored.) [SQLSTATE 42000] (Error 22022)"
> After restarting the SQLServerAgent I get a short grace period with no
> error, but after a few day they resurface.
> I'm running SQL2K sp2 +latest hotfixes on win2k using netsend and email
> (using outlook client ) notification.
> Any idea to the cause ?
> I couldn't find a signal article on the subject?
> Please help
> Guy Rafalovich
> DBA Team Leader Hotbar.com