Microsoft KB Archive/248431

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


SBS: Server Msg 17952: Failed to Start SQL Mail Session

Article ID: 248431

Article Last Modified on 5/18/2001



APPLIES TO

  • Microsoft BackOffice Small Business Server 4.5



This article was previously published under Q248431

SYMPTOMS

When you attempt to execute the extended stored procedure xp_startmail in SQL Server 7.0 on SBS 4.5, you may receive the following error message:

Server: Msg 17952, Level 18, State 1, Line 0 Failed to start SQL Mail session. Check the errorlog file in the SQL Server directory for details.



The SQL Error Log might also refer to error messages 17951 and 17903.

CAUSE

This error message occurs because the SBS installation process performs an unattended installation of SQL Server 7.0 and configures the MSSQLServer and SQLServerAgent services to run using the System Account.

RESOLUTION

To resolve this error, do the following:

  1. Click Start, point to Settings, click Control Panel, and then double-click Services
  2. Configure the MSSQLServer and SQLServerAgent services to run using a valid domain account. You can have them use the Administrator account or create another account exclusively for SQL. Note that if you ever change the password for the Administrator account or the account you decide to use for SQL, you also need to change that password in the Services tool in Control Panel.
  3. Create a mail profile for this account on the server.For additional information about MAPI profiles and how to create them using Outlook 2000, click the article number%2 below to view the article%2 in the Microsoft Knowledge Base:

    195478 OL2000: (CW) User Profiles and Information Service

    Note that Outlook 2000 or another configured MAPI client must be started before xp_startmail is executed.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kberrmsg kbhowto KB248431