Printable View
I' m not being succesful trying to get SQL Mail to work on. I have Sql Server 2000 and Exchange Server 2003 installed on the same server. I also installed outlook Client to create the MAPI profile to be used by SQL mail.
The system hungs when i test the MAPI Profile from Sql Enterprise.
Any suggestions. Thanks.
Steps To Set Up SQL Mail:
1. On the Microsoft Exchange server, set up a mailbox for the user account that is to be used by the MSSQLServer service. This account must be a domain account. For example:
Account: DOMAIN1\SQLServerAccount
Mailbox: SQL1
2. On the SQL Server computer, log on to Windows NT by using the same user account that is to be used by the MSSQLServer service.
In the preceding example in step 1 it would be:
DOMAIN1\SQLServerAccount
3. Install an Exchange client on the SQL Server computer. When running SQL Server 6.5 or SQL Server 7.0, this can be the client application that ships with Microsoft Exchange Server, Microsoft Outlook 98 or Microsoft Outlook 2000. The addition of the Outlook security patch for Outlook 2000 to prevent the spread of e-mail viruses will cause SQL Mail 6.5 or 7.0 to stop responding (hang). Because Outlook 2002 also includes this security feature, it will also cause SQL Mail 6.5 or 7.0 to hang. (See the "Outlook 2000 Client" section later in this article for a detailed explanation of the cause.)
When running SQL Server 2000, the mail client must be the Microsoft Outlook 2000 or Outlook 2002 client. Because SQL Mail 2000 makes an extended MAPI connection to the mail server, it is not affected by the Outlook security features. With SQL Server 2000 Service Pack 1, you can also use Outlook 98.
4. Start the Exchange client and configure the client to connect to the Microsoft Exchange Server. You will need to provide the name of the Exchange server and the mailbox on the Exchange server. After the setup is complete, verify that you can send and receive mail interactively. You can then close the client.
5. Start the Mail application in Control Panel. Click Show Profiles to find the name of the profile that was configured in step 4. If the profile name is longer than 32 characters or contains unusual characters (periods, hyphens, pound signs, and so forth), change the profile name to be less than 32 characters and remove the unusual characters (spaces are okay).
6. In Control Panel, click Services, and then verify that the MSSQLServer service is configured to run under the same Windows NT user account that you logged on with in step 2. Start or restart the MSSQLServer service if necessary. In SQL Server 7.0 and SQL Server 2000, make any startup account changes by way of the SQL Enterprise Manager if you are using Full Text Search on the computer.
7. Configure SQL Mail to use the profile name you found in step 5. SQL Mail uses the account and password configured for the MSSQLServer service to login to the Exchange server.
8. Start SQL Mail. The SQL Mail icon becomes green if SQL Mail starts successfully. (This step is not necessary when using SQL Server 2000 because SQL Mail will be automatically started when you first try to send mail.) Test SQL Mail by opening a query window and use xp_sendmail to send e-mail to yourself. If you are using SQL Server 7.0 or SQL Server 2000, also configure SQLAgentMail with the same profile. You can test SQLAgentMail by sending mail to an operator.Quote:
NOTE: If the profile name that you type in is not recognized or no profiles appear in the drop-down list box for SQL Server 7.0 or SQL Server 2000, you have started the MSSQLServer service under the Local System account. Change the service to start under a domain account, stop and restart SQL Server, and then try to configure the mail profile again.
For more information refer this link:
http://support.microsoft.com/kb/263556
Exchange's implementation of the NSPI proxy in DSProxy is somewhat simplestic. It literally reads packets from one socket and writes them to the other. A side effect of this simple implementation is a number of error scenarios don't get handled well. Particularly if the GC being proxied to goes down - DSProxy doesn't always send the error back to the client. So we can end up with a client that's waiting on the server to respond, and a server that's convinced the connection has been torn down. This particular hang can only happen if the MAPI client isn't using referral, which is why it's so important to ensure referral is working.