SQLMail Problem - not the usual!

Question

Post reply

SQLMail Problem - not the usual!

Jeff Brumley

SSC Eights!

Points: 802
More actions
September 13, 2004 at 11:11 am

#108829

I haven't been able to find info on this error anywhere....
In EM, when accessing an operator object and testing the mail address -
Error 22022: SQLServerAgent Error: The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
We are using the same domain account for SQL Server and Agent; we can successfully test the Mail Profile (it can start and stop a MAPI session); this only occurs on certain servers.
Now, I've seen the same prompt on my workstation as they actually do make changes to the Exchange configuration, but I wouldn't expect it from a server MAPI profile...and I don't know what I should do about it anyway!
Thanks in advance..
September 16, 2004 at 8:00 am

This was removed by the editor as SPAM

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Dallas Miller Newbie Points: 7 More actions · Answer 1

Anyone found anything on this yet? I am now getting the same error.

Kenny Wendel Newbie Points: 7 More actions · Answer 2

For me it helped just to restart the SQLServerAgent for that instans in the SQLserver.

Don´t forget that the SQLServerAgent-service most be running with the accout that holds the outlook-profile.

/maffi

Jeff Brumley SSC Eights! Points: 802 More actions · Answer 3

we actually ended up buying SQLSentry, so no more worries about SQLMail at all

Usman Zaman Newbie Points: 7 More actions · Answer 4

I got the same message on my workstation; spoke to the adminisreator and he says that no configuration changed were made to Exchange....

Ed Bell Old Hand Points: 360 More actions · Answer 5

That error happened to me when my network admin moved the sqlservice mailbox from Exchange 2000 to Exchange 2003. Outlook was pointed towards the correct server, but SQL Mail still wouldn't send. Re-starting the SQL Server Agent fixed the problem

keithwarnock SSC Rookie Points: 30 More actions · Answer 6

I had the exact same error... restarting SQl Server Agent fixed the issue.

FYI

🙂

dharanikota Newbie Points: 3 More actions · Answer 7

Ed Bell (2/6/2006)
That error happened to me when my network admin moved the sqlservice mailbox from Exchange 2000 to Exchange 2003. Outlook was pointed towards the correct server, but SQL Mail still wouldn't send. Re-starting the SQL Server Agent fixed the problem

True, restarting the SQLServer Agent fixed the problem only for testing the email notification via an Operator. But emailing the report as an attachment is still failing.

Here is the error.

Emailing report to operator 'XYZ' [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 18025: [Microsoft][ODBC SQL Server Driver][SQL Server]xp_sendmail: failed with mail error 0x80040119

(null)

Anyone facing similar problems ?

Marti Oakerson Grasshopper Points: 11 More actions · Answer 8

I had a similar problem, but with a different wrinkle. Jobs that I schedule daily that send success/failure messages continued to appear to be running to the system. When the job was scheduled to run the next day...it was refused because the appearance of one still running. I tried to locate the process in processes, task manager..????, but couldn't find it anywhere to force complete it or cancel it.

Anyone have a clue where I might look...I'm stumped

P.S

In the end...re-starting the Sql Server agent cleared up the rogue processes and jobs were then able to run as scheduled.