October 21, 2004 at 11:02 am
I am trying to set up Microsoft Outlook on my Sql Server so that the programmers can send e-mail alerts to users within their software. I logged into the Sql Server 2000 as ‘SQLExec’ and then installed Outlook 2003 on it. I can now log onto the server as SQLExec and open up Microsoft Outlook and send and receive mail.
But when I open up the properties on the Enterprise Manager <Sql Server Group – Database - Management – Sql Server Agent> and try to set the mail profile, I cannot pull down anything from the drop box nor enter anything manually in the profile at all.
I also tried going to <Sql Server Group – Database - Support services – Sql Mail>. Here again, I do not have anything listed in the drop down box but it allows me to write manually. I tried entering either ‘SQLExec’ or ‘outlook’. Both of them resulted in the following message.
Error 18030: xp_test_mapi_profile : Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default client.
Any ideas???
October 21, 2004 at 11:13 am
There is a great reference for SQL Mail on this site. Go to search type sql mail and choose the article by Steve Jones for SQL Mail Resources. Great tips.
One quick check: If your trying to do SQLAgentMail, check the "service startup account" and check to see if it matches the account used for the mail profile that will be selected under "mail session" rather than system account unless you have set SQLSERVERAGENT to the desired account.
October 21, 2004 at 12:49 pm
Try having a look at the following thread
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=105655
there's a sample procedure there that i posted to send mail using collaboration data objects, make sure you scroll down to my second post as i managed to miss some of it out the first time. and saves you having to install outlook on your database server which is always a good thing.
WE wrote this as we had so many problems with sql mail which caused us to have to reboot the database server a couple of times.
good luck
Dave
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply