Error 17952 Failed to Start SQL Mail Session

Error 17952 Failed to Start SQL Mail Session

Post by Palom » Wed, 15 Jul 1998 04:00:00


I'm trying to start the SQL Mail with Windows Messaging 4.0.0993.3 and
Microsoft Mail.

In the Books Online I only found information about the configuration with
MSMail32... but I using Windows Messaging (Exchange).

I always receive the following error message:
Microsoft SQL-DMO : "Error 17952  Failed to  Start SQL Mail Session. Check
the error log file in the  SQL Server directory for detail"

InSQLExec.out these are the entries:

7/14/98 7:23:19 PM - ? SQL Executive version 6.50.240
7/14/98 7:23:19 PM - ? SQL Server version 6.50.281
7/14/98 7:23:19 PM - ? DB-Library version 6.50.252
7/14/98 7:23:19 PM - ? SQLExecutive Service Started
7/14/98 7:23:32 PM - ? Starting Microsoft Mail session using account
7/14/98 7:23:32 PM - + DBLib Message Handler: Failed to start SQL Mail

Any help appreciated.

Paloma Queimadelos

Please direct replies to news group. Thanks.


Error 17952 Failed to Start SQL Mail Session

Post by Neil Pik » Wed, 15 Jul 1998 04:00:00


PSS ID Number: Q153159
Article last modified on 07-11-1997

6.0 6.5


The information in this article applies to:

 - Microsoft SQL Server, versions 6.0 and 6.5


You can use certain basic troubleshooting techniques to diagnose and
resolve most SQLMail problems. Typically, errors in starting a SQLMail
session or sending mail from SQLMail with a Microsoft Exchange Server
into two categories: permissions problems and Exchange client setup
problems. SQLMail functionality is documented in the "Books Online" for
version 6.x. These should be thoroughly reviewed before using SQLMail.


You should examine the following checklist of items, preferably in the
order given:

1. Log on to Windows NT with a user account that is an administrator of
   the local computer and is a domain account.

2. Confirm that the Exchange client, EXCHNG32.EXE, can connect to the
   Exchange server and mail can be sent.

3. Confirm that the Exchange profile used does not have a Personal
   Message Store (.pst) by running the Mail and Fax tool in Control
   Panel. Click the Show Profiles button and in the Mail dialog box
   the default profile in the profile list according to the drop-down
   labeled "When starting Microsoft Exchange, use this profile." Click
   Properties button.

4. Select the services tab in the new dialog box and confirm that the
   services are Microsoft Exchange Server and Personal Address Book.
   the Delivery tab and confirm that what is selected on the Deliver To
   drop-down list is the Mailbox on the Exchange Server, which should
   something like "Mailbox - <Friendly User Name>" where Friendly User
   is the name of the user who logged on to Windows NT in step one.

5. To run SQLMail with an Exchange Server, it is necessary that the
   MSSQLServer service is run under the same user account that logged
   during step one above. You can determine this by opening the
   tool in Control Panel, selecting the MSSQLServer service and
   the Startup button.

6. Confirm that the SQLMail user name and password are correct by
   running SQL Server Setup. Select Set Server Options and click the
   Login button. The user name must match the Profile name from step

NOTE: The password and Copy SQLMail Configuration in the Current User
Account check box do not matter since both no longer apply.

NOTE: SQL Server Setup version 6.5 will only ask for the Exchange

7. Test SQL Server access permissions to the Exchange Server. You can
   do this by using the XP_CMDSHELL extended stored procedure, which
   with the same permissions as SQLMail. Use the following command to
   connectivity to the server, assuming the Exchange Server is located
on a
   computer named "NTServer".

      xp_cmdshell "NET USE \\NTServer\IPC$"

If the above command fails, step three has not been completed

8. At this point SQLMail should be able to Autostart or be started
   manually with the xp_startmail extended stored procedure.
   you can choose the profile to use with xp_startmail by replacing
   <Profile name> with the profile name from step three, as in the
   following example:

      xp_startmail "<Profile name>",""

 Neil Pike MVP/MCSE
 Protech Computing Ltd


Error 17952 Failed to Start SQL Mail Session

Post by Sir. Issac » Thu, 16 Jul 1998 04:00:00

I was having the same problems as Paloma.  The article that you provided
helped.  I now connect and mail queues correctly.  It places the
outbound messages in the outbox of the email user.  I set the 'check for
new messages' interval to 1 minute.  It doesn't ever upload the messages
to our POP3 server.

I dug a little and found that both the SQL Mail process and the
Exchange32 program use the MAPI spooler.  It seems that the Exchange32
program is unable to upload outgoing mail/download new mail if another
program is also using the spooler.

I don't know if I am even looking at the right area.

The simptoms of the problem are:
1. When an SQL event runs and then sends out an email, it sits in the
outbox indefinetly.
2. When I manually run the 'InBox' (icon - or Windows Messaging which
shows up as exchange32 in the task manager), it tries to upload/download
email and hangs without ever displaying the dialog indicating it's
3. If I stop SQL Mail, and end the MAPI Spool process prior to double
clicking the 'InBox', it will successfully upload/download to the POP3

Is there a way to just have the SQL Mail be routed to the POP3 server
without spooling it to an email user's outbox?  If not, how can Windows
Messaging be setup to automatically upload/download email without
requiring the InBox to be left running (as it seems that both SQL Mail
and the InBox can't run at the same time without causing the InBox to

Thanks in advance.


Error 17952 Failed to Start SQL Mail Session

Post by Neil Pik » Fri, 17 Jul 1998 04:00:00

It should work if you install the MS Exchange client ( a recent version
).  The problems are caused by bugs in mapi, not in SQL Server.  I've
no experience going to POP3 via SQL MAil though

 Neil Pike MVP/MCSE
 Protech Computing Ltd