In User Manager for domains, connect to the local
account database on the NT server where SQL
Server is installed.
Create an NT user account to be used by SQL
Server to log into the network. Make sure the
account has "Password Never Expires
checked" and does NOT have "User Must
Change Password at next logon" checked.
Make the NT account a part of the local
administrators group on the server where SQL
Server is installed. You could use the local
Administrator account for this purpose, as long
as this account will not be sending and receiving
mail independently of SQL Server's mail client.
Make sure that the new account is part of the
same domain from where the exchange mailboxes are
being created, or that there is a trust
relationship with that domain.
Still in User Manager for Domains, choose the
Policies menu and select User Rights. In the User
Rights dialog, select the "Show Advanced
User Rights" checkbox.
In the "Right" list box, choose
"Act As Part Of the Operating System."
Add the account SQL Server is using to log into
NT to the "Grant To" list box. Repeat
this process for the "Increase Quotas"
right, the "Log On As a Service" right,
and the "Replace a Process Level Token"
right. SQL Server must have all of these rights
when using other than the Localsystem account.
Exit User Manager for Domains.
In the Exchange Administrator, create a new
mailbox for SQL Server, specifying the new NT
account SQL Server will use to log into the
Go to Control Panel, Services on the server where
SQL Server is installed; alternatively, run the
Server Manager utility from the Administrative
Tools program group, choose the NT server where
SQL Server is installed and open the Services
utility. In the Services list box, choose the
MSSQLSERVER service. Press the Startup
button. SQL Server probably is logged into the
network as the System Account.
Choose "Log on as This account." The
LOCALSYSTEM account will probably be in the
"log on as this account" text box.
Press the ellipse button (the three dots) to go
to the List Accounts dialog, and choose the
account that you just created for SQL Server to
log into the network. Change the password and
exit out of the Startup dialog.
Stop and Restart the MSSQLSERVER service to have
SQL Server log into the network under the new
At the NT server where SQL Server is installed,
log in to NT as the account that was just created
for SQL Server, making sure the correct domain is
Install the Exchange client on the NT server.
While still logged into NT as SQL Server's new
account, run the Exchange client for the first
time. Go through the Wizard to set up a new
When the profile has been created and you are
running the Exchange client, go to the Tools menu
and select Options. Choose the Delivery tab.
Make sure the "Deliver To" setting is
"Mailbox-name" where name is the name
you chose during profile setup for the Exchange
mailbox. If the "deliver to" setting is
"personal folders" then SQL Mail will
not work correctly.
Verify that the Exchange client can send and
receive mail. Correct any lack of permissions
that is preventing mail from being sent or
received. You can then exit out of the Exchange
Go to Control Panel on this NT server where SQL
Server is installed, and run the Mail and Fax
utility. Choose "Show Profiles."
Make sure the profile just created from the
Exchange client is the profile to be used as the
default when running Exchange. Make a note of the
name of this profile. Exit from Control Panel.
Run SQL Enterprise Manager. Log into the SQL
Server by drilling down on the "+" icon
next to the server name. Right-mouse-button click
on the SQL Mail icon and choose Configure.
You will be prompted for the name of the Exchange
profile that SQL Server is to use. Type in the
name of the profile that you just made a note of
in Control Panel, e.g., "MS Exchange
Right-mouse-button click on the SQL Mail icon
again and this time choose Start. If the SQL Mail
icon turns green then SQL Server's mail client is
running and can send and receive mail.
If SQL Mail fails to start, go to the NT
Application Event log and check on the error. If
it is a "MAPI logon failure" that means
that SQL Mail was not able to log into the
Exchange server. If you were able to send and
receive mail through the Exchange client when
testing it interactively, then 99% of the time
this is a network permissions problem, meaning
that SQL Server doesn't have permissions on the
network to get to the Exchange server. Make sure
that SQL Server has been stopped and restarted
since changing its logon settings and make sure
that that SQL Server's NT user account has
permissions on the network to get to the Exchange
server. It should have, if you can send and
receive mail from the Exchange client.