Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cdpowers
Starting Member
5 Posts |
 Posted - 2003-08-07 : 13:35:11
|
| '22022 unable to post notification to SQL server agent'Anyone familiar with this error, what further research might be performed to determine solution.Thx |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-07 : 13:36:49
|
| I have never received this error. You should check the SQL Server Error Log for a more descriptive error if one is available. What is your job trying to do with the notifications (e-mail somebody about the job?, write to Event Log?, etc...)? Does the SQLSERVERAGENT log on with an account that has administrative privileges on the server?Tara |
 |
|
|
cdpowers
Starting Member
5 Posts |
Posted - 2003-08-07 : 15:06:03
|
| Tara - thanks for your attention. This is some follow up information from my administrator:"SQLServerAgent logs on using the RICHMOND\SQLEXE account, which is the same account MSSQL Server uses. This is the same account it's used in the past, so unless it has changes since yesterday I wouldn't suspect it to be the culprit.The only notifications set up were to write to the NT event log if the job fails. I tried turning this off so that no notifications were used and still received the same error when attempting to start the job.It should be noted too that existing jobs which are scheduled to run hourly appear to be executing successfully, but if we create a new job and put it on a reoccurring schedule it will not execute. Also, it doesn't appear to matter what the job does, even a new job with a simple step such as running sp_who fails with the same error." |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-07 : 15:34:30
|
| Did you check the SQL Server Error Log yet? Are you on the latest service pack for SQL Server (if SQL 2000, then it's service pack 3a)?Tara |
|
|
|
shsmonteiro
Constraint Violating Yak Guru
290 Posts |
Posted - 2003-08-12 : 22:58:52
|
| Please post the reason part of the error message as well as the SQLagent.out log file. If the reason part says that you've reached the maximum number of notifications, you have more than 128 notifications pending, what mean that you does not process notification fast enough, because you have a large number of jobs or that you have insuficient worker threads, or that you have xp_sqlagent_enum_jobs runing on loops.regards,Sérgio MonteiroTrust in no Oracle |
|
|
|
|
|
|
|
|
ERROR: related to sql job component