Re: Cannot setup SQL Mail on SBS 2003



HI Jenny,...

Thanks for the input,.... we strike our first problem at step 1... We
CANNOT install outlook on the Server computer because this is a Small
Business Server we are talking about - ie: Exchange also on this box, and
cannot install outlook on the exchange server!

soo.... are we still stuck?

Mark


"Jenny wu [MSFT]" wrote:

> Hi Mark and Karl,
>
> Thanks for posting here! Also thanks for Steve's input.
>
> To resolve SQL Mail issue, I suggest you double check your configuration for
> correcting an improper configuration can resolve the vast majority of SQL
> Mail problems.
>
> To make sure that you have SQL Mail configured correctly, use this list:
>
> 1. You must have a mail client (such as Microsoft Outlook) installed on the
> computer that runs SQL Server.
>
> 2. Use the Corporate or Workgroup option for Microsoft Outlook 2000
> (Microsoft Outlook 2002 does not have the Corporate or Workgroup option). To
> select the option, on the Tools menu, click Options, and then double-click
> the Mail Services tab. In the Mail Services dialog box, click the Mail
> Support command. Microsoft Outlook 2002 does not work with SQL Mail when you
> use an Internet mail server unless the Outlook client is left running at all
> times.
>
> 3. You must have a working mail server such as Microsoft Exchange or an
> Internet mail (Post Office Protocol 3 [POP3] or Simple Mail Transport
> Protocol [SMTP]) server. The outgoing mail SMTP server need not be the same
> as the incoming mail POP3 server; however, you must have a valid incoming
> mail server with a configured mail account, even if you never plan to send
> mail to SQL Mail.
>
> 4. The account you use to start the SQL Server service must be a domain
> account if you are using an Exchange server. The domain account must have a
> mailbox on the Exchange server. If you are using an Internet mail server,
> you can use a local account to start SQL Server. However, the account you
> use to start SQL Server cannot be the Local System account, under any
> circumstances. The same applies to the service account you use to start the
> SQL Agent if you are using SQLAgentMail.
>
> 5. Because mail profiles are associated with a Microsoft Windows login
> account, you must log on to the computer that is running SQL Server with the
> SQL Server service startup account in order to inspect the mail profile
> available to SQL Server. For example, open Control Panel. In the Control
> Panel dialog box, double-click Mail. In the Mail dialog box, double-click
> Show Profiles. If you are using SQLAgentMail and the SQL Agent service
> account is different from the SQL Server service account, you must also log
> on with the SQL Agent service startup account to inspect the mail profiles
> available to the SQL Agent.
>
> 6. You must be able to open the mail client and test sending and receiving
> an e-mail to your mail server. No dialog box or message should appear that
> requires user action. SQL Mail uses the mail client to send mail. Because
> SQL Mail runs in the SQL Server service, any dialog boxes that require user
> interaction appear on the "virtual desktop" and do not receive a response.
> The lack of response causes SQL Mail to stop responding (hang).
>
> 7. You must provide SQL Mail the mail profile you use to test your mail
> client configuration. To do so, in Enterprise Manger, open the Support
> Services folder. In the Support Services folder, right-click SQL Mail, and
> then click Properties. If you use SQLAgentMail, you must provide the mail
> profile to SQL Agent. To do so, in Enterprise Manager, open the Management
> folder, right-click SQL Agent, and then click Properties.
>
> 8. The default Internet e-mail program must be the same as the mail client
> you use to test the mail configuration. To make sure you have the correct
> program, open Control Panel, double-click Internet Options, and then click
> the Programs tab.
>
> 9. For any of the preceding changes to take effect, you must stop, and then
> restart the SQL Server service. If you reconfigure the default mail profile,
> you must restart the computer for the changes to take effect.
>
> And I would like to suggest you refer to the following KB article to get
> more detail info about frequently encountered problems and general
> troubleshooting methods.
>
> 315886 INF: Common SQL Mail Problems
> http://support.microsoft.com/kb/315886/en-us
>
> 311231 INF: Frequently Asked Questions - SQL Server - SQL Mail
> http://support.microsoft.com/kb/311231/EN-US/
>
> HOW TO: Troubleshoot Your SQL Mail Issue (321183)
> http://support.microsoft.com/kb/321183/EN-US/
>
>
> The following KB article may be useful to you:
>
> How to obtain the latest SQL Server 2000 service pack
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;290211
>
> INF: How to Configure SQL Mail
> http://support.microsoft.com/kb/263556/en-us
>
> FIX: SQL Agent Mail May Cause E-mail to Be Written to Root Directory of
> Source Mailbox (308758)
> http://support.microsoft.com/kb/308758/en-us
>
> Support WebCast: Troubleshooting Microsoft SQL Mail
> http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com/servicedesks/webcasts/wc091301/wcblurb091301.asp
>
> Hope above information helps! If you have any further concern or question
> about the issue please feel free to let me know. I am always happy to be
> assistance of you!
>
> Have a nice weekend!
>
> Best Regards,
>
> Jenny Wu
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ----------------------------------------------------------------------------
> -----
> <shiftylizzards@xxxxxxxxx> ????
> news:1125072703.078521.29790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Thanks anyways Steve. Been searching the KB, but as you said, 'experts
> > at hiding...'!
> >
> > Good weekend! ;-)
> > K
> >
>
>
>
.



Relevant Pages

  • Re: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... issues, such as a server that might have IIS running on the same machine, ... applicable to SQL 2000 environment, ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • RE: MP Install issue
    ... Where in the installation are you talking about specifying the account rather ... > MPDB ERROR - CONNECTION PARAMETERS ... > SQL Server Name: servername ... > with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)
  • Re: SQL Express Fails with Hardware Error
    ... The LocalSystem account is a built-in account, ... which the SQL Service runs. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Minimum Hardware Requirement (Warning) ...
    (microsoft.public.sqlserver.setup)
  • Re: SCCM with a remote SQL instance problems (IT IS NOT A WARNING)
    ... PreReq check is not a WARNING it is a FAILURE. ... account the run the SQL Server Service on the server, Domain Memberships, AD ...
    (microsoft.public.sms.installer)
  • Re: Distributed Query - Linked Servers?
    ... In the case of SQL style accounts, it doesn't seem very secure to me, because the password will be transmitted over the network. ... it should also be able to work by setting up a credential and proxy account on Server1. ... In this case it could work with NTLM authentication. ... we just need to verify that the 2 sql server instances are under sql server and windows authentication mode and the sql account you use has the permission on the 2 sql server instances. ...
    (microsoft.public.sqlserver.server)