SQL Mail on SQL 2005 Sevrer Not Working

Question

Post reply

SQL Mail on SQL 2005 Sevrer Not Working

Sam T

Right there with Babe

Points: 742
More actions
June 28, 2006 at 3:18 pm

#168993

Hi – My DBA has "looked everywhere" for the answer to this, but still can’t solve the issue. For legacy application reasons, we still need to use SQL Mail and have a new SQL 2005 install. He's gotten it configured properly as per Microsoft’s documentation, and set up an Exchange account and an Outlook profile for the user that the SQL Server services run as (domain user). Even after all of that, he still gets the same error when right-clicking on the ‘Properties’ of SQL Mail in the SQL Management Studio:
TITLE: Microsoft SQL Server Management Studio
Cannot show requested dialog.
ADDITIONAL INFORMATION:
If a stored procedure could not be found, SQL Mail may not be installed in the instance. (SqlManagerUI)
xp_get_mapi_profiles: 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 mail client. (Microsoft SQL Server, Error: 17930)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=17930&LinkId=20476
Any ideas or resources would be greatly appreciated.
I thank you and my DBA thanks you!
Sam

Viewing 15 posts - 1 through 15 (of 16 total)

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

Jim Dillon-291542 Hall of Fame Points: 3344 More actions · Answer 1

Was SQL Server Agent restarted after setting up SQL Mail?

Sam T Right there with Babe Points: 742 More actions · Answer 2

Yes, we even rebooted the machine. We can't really get SQL Mail setup completely because it won't let us get to the properties. I had my DBA show me everything today and we even tried using xp_startmail with the profile and password and we got the same 17930 error.

In the meantime, I had the DBA set up SQL Mail on a SQL 2000 machine and he had no issues with that.

Thanks for the response!!

Sam

Jim Dillon-291542 Hall of Fame Points: 3344 More actions · Answer 3

Have you tried the Database Mail feature for 2005. I have a 64 bit SQL server so I can't use SQL Mail, but I can use Database Mail. It was fairly easy to set up and seems to work well.

Jim Dillon-291542 Hall of Fame Points: 3344 More actions · Answer 4

SQL Mail problem check:

Look at your Internet Settings,(Setttings->Control Panel->Internet Options) your default mail client might be set to Outlook Express. Make sure this is set to Outlook.

Sam T Right there with Babe Points: 742 More actions · Answer 5

Unfortunately, the majority of our customer base is still using SQL 2000 and we are trying to stick with one set of source code for both versions of sql.

I'm thinking that the developer needs to come up with a way to figure out which version of SQL is being used and use SQL Mail for 2K and Database Mail for 2K5...but I'm not sure how that's going to go over.

I'll double check that it's set as Outlook and not Outlook Express.

Thanks!

Sam

Sam T Right there with Babe Points: 742 More actions · Answer 6

Sam T

Right there with Babe

Points: 742

June 29, 2006 at 2:15 pm

#646842

Yup...Outlook is the default client.

Sam

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 7

Good Day Sam,

Here's the code that your developer probably needs (it's from today's SQL Server Central emailing !):

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1753

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Sam T Right there with Babe Points: 742 More actions · Answer 8

Thanks, Rudy! I just got to the bottom of the e-mail and saw that too. Timing is everything! Thanks to all!

Sam

DB_Andrew Ten Centuries Points: 1089 More actions · Answer 9

"we still need to use SQL Mail and have a new SQL 2005 install."

They key there is "a new"

By default SQL 2005 has several services disabled. If you read the books online and search under "Surface Area Configuration for Features" you will find that SQL Mail is disabled by default in new installations.

I hope this helps.

Sam T Right there with Babe Points: 742 More actions · Answer 10

Is there more to it than going into the Surface Area Config. and checking of the enable check box (I think it was a check box) under SQL Mail? We did that and rebooted the server - no luck. We've been talking to Microsoft today and they are stumped; the guy we talked to is going to try to recreate the issue there and call back on Monday.

Thanks!

Sam

DB_Andrew Ten Centuries Points: 1089 More actions · Answer 11

Search the books online documentation for "SQL Mail" it will tell you all of the requirements needed to use this feature of SQL Server 2005.

Thats a typical MS "hose and close". If you don't get a call by back 9:00AM Monday, I'd call them back and follow up.

GL

John Dempsey Hall of Fame Points: 3225 More actions · Answer 12

Sam T, I'm not sure if this is your problem exactly but maybe it can help. I ran into a similiar problem trying to use the MAPI mail client in a DTS package to maintain a legacy application. Here is an excerpt of an email that I sent out to fellow coworkers regarding the issue:

I attempted to run a .NET application that called several DTS packages. In one of these DTS packages it called the MAPI SendMail component as the first step. Upon reaching this step the job failed. I opened up SQL 2000 Enterprise Manager and then opened the package and attempted to open the Properties of the SendMail step. This immediately produced an error message which stated "Cannot load MAPI Interface layer for DTS. Please make sure that semmap90.dll is installed". Upon looking up the message on google the following websites were found related to this issue: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=143383&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=158753&SiteID=1 .

Basically, the issue had to due with the recent installation of SQL Server 2005 on my local machine. It seems that upon installing SQL Server 2005 on the machine that it changed the DLL that the MAPI SendMail uses to "semmap90.dll". In SQL 2000 the DLL appears to be located in \Program Files\Microsoft SQL Server\80\Tools\Binn and is called "semmap.dll". I believe that the SQL Server 2005 installation changes the reference of the MAPI SendMail to the "semmap90.dll" DLL. But, this DLL is created and found in a different path \Program Files\Microsoft SQL Server\90\Tools\Binn. This 90 path is installed with SQL Server 2005 I believe so the new DLL is created there. I haven't been able to confirm this but I think that SQL 2000 Enterprise Manager looks to the referenced object name which is now "semmap90.dll" but it looks for it in the Binn directory for SQL Server 2000. The Binn directory for 2000 is \Program Files\Microsoft SQL Server\80\Tools\Binn and which doesn't contain "semmap90.dll" it contains "semmap.dll" so the step crashes.

The solution that worked was to copy the DLL from \Program Files\Microsoft SQL Server\90\Tools\Binn\semmap90.dll into the SQL Server 2000 (80) Binn directory located at \Program Files\Microsoft SQL Server\80\Tools\Binn. In addition you need to copy the C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SEMMAP90.rll into \Program Files\Microsoft SQL Server\80\Tools\Binn\Resources\1033.

I hope this helps.

Sam T Right there with Babe Points: 742 More actions · Answer 13

Thanks! Microsoft has three people working on this now because we are having trouble installing the service pack for Office and SQL. Hopefully, your answer will fix the email issue!

Thanks again!

Sam

Balmukund SSCertifiable Points: 6648 More actions · Answer 14

I am curious to know the version of outlook.

SQL Server 2005 Books Online

How to: Configure Mail Profiles for Use by SQL Mail (Windows)

Install an Exchange client on the computer that runs SQL Server. For Microsoft SQL Server 2005, supported Microsoft Exchange clients are Microsoft Outlook XP and Outlook 2003.