SQL Mail (Help! - Frustrated) 
Author Message
 SQL Mail (Help! - Frustrated)

I have my MS Windows Messaging configured to be used in SQL Mail. When I
do the testing for SQL Mail service, the service running well. But I try
to test sending e-mail to the operator, I get
"Error 22022:SQL ServerAgent Error: The Mapi Call failed."

When I try to test using SQL Query analizer I get "Server: Msg 17902,
Level 18, State 1, Line 0
General MAPI failure."

I have replaced the mapi32.dll with the new one Size 800kB +. I really
stuck on this matter, while my developer has asked me to make it run.

I check on Control Panel/Internet/Options I could only find Outlook
Express there.

All the advice on this mailing list has been completed, but seems the
SQL Mail I have is not working.... What should I do to make my SQL Mail
run???

Other thing is: Is it true that xp_sendmail will only work with sa
account?

Any help will be appreciated, especially from you, Neil Pike.

Regards
Agus Wong
Washington, DC



Mon, 07 Oct 2002 03:00:00 GMT
 SQL Mail (Help! - Frustrated)

1. Log on to the server using the login that SQL server uses, Run OUTLOOK
and make sure you can send mail.
2. Make sure that the default address book is the one you wish to have
active when SQL sends mail.
3. Make sure SQL Server is running using a Domain Login that is part of the
administrators group.
4. Make sure that the profile is properly entered in the SEM SQL MAil
profile.
5. Make sure SQL mail is running.

THese are the most common probs..

XP_sendmail may be used by anyone, however it runs in the security context
of SQL Server, which usually has administrative rights...

From BOL

Troubleshooting SQL Mail with Exchange Server
Typically, errors in starting a SQL Mail session or sending mail from SQL
Mail with Microsoft? Exchange Server fall into two categories: permissions
problems and Exchange client setup problems. For more information about SQL
Mail, see SQL Mail.

Examine this list of items, in this order:

Log on to Microsoft Windows NT? with the user account that will be used for
the MSSQLServer service. This user account must be an administrator of the
local computer and a domain account.
Confirm that the Exchange Server client, Exchnge32.exe, or the Microsoft
OutlookT client, Outlook.exe, can connect to Exchange Server and that e-mail
can be sent.
Confirm that the Exchange Server profile used does not have a Personal
Message Store (.pst).
On the Services tab, confirm that the only services available are Microsoft
Exchange Server and Personal Address Book, and then click the Delivery tab.
Confirm that the selection in the Deliver To box is the mailbox on Exchange
Server, which should have a name similar to "Mailbox - <Friendly User Name>
 (where <Friendly User Name> is the name of the user who logged on to
Windows NT in Step 1).
To run SQL Mail with Exchange Server, the MSSQLServer service must be run
under the same user account that logged on in Step 1. In Control Panel,
double-click Services, select the MSSQLServer service, and then click
Startup.
Confirm that the SQL Mail profile is correct. In SQL Server Enterprise
Manager, expand the server, expand the Support Services folder, select SQL
Mail, and then right-click. Click Properties, and then on the General tab,
ensure that the profile name specified in the Profile name box is correct.
If needed, click Test. The profile name must match the profile name used in
Step 3.
Test Microsoft? SQL ServerT access permissions to Exchange Server by
executing xp_cmdshell, which executes with the same permissions as SQL Mail.
Use this command to test connectivity to the server, assuming Exchange
Server is located on a computer named "NTServer".
xp_cmdshell "NET USE \\NTServer\IPC$"

If this command fails, Step 3 was not completed correctly.

It should now be possible either to start SQL Mail automatically or to start
SQL Mail manually using xp_startmail. When using xp_startmail, the profile
can be replaced by replacing <Profile name> below with the profile name used
in Step 3:

xp_startmail '<Profile name>',''

--
Wayne Snyder
MCSE, MCT, SQL Server MVP
IKON Education Services -  C{*filter*}te, NC
(Please respond only to newsgroups.)



Tue, 08 Oct 2002 03:00:00 GMT
 SQL Mail (Help! - Frustrated)
Wayne,

Thanks for the response, I try to follow your steps, however I am using MS
Windows Messaging provided by Windows NT 4.0.

1. I logon as sqladmin user same as the SQL service account. The Windows
Messaging can send mail and receive.
2. The default address book is set as Personal Address book
3. Conifgured as menitoned
4. Configured as mentioned
5. SQL mail is running.

However my error when I try to send test message in Operator properties still
appear as:
"Error 22022:SQL ServerAgent Error: The Mapi Call failed."

If I run the xp_sendmail, different error comes up:
"Server: Msg 17902,
Level 18, State 1, Line 0
General MAPI failure."

Any other solution?

Thanks
Agus Wong
Washington, DC

Quote:

> 1. Log on to the server using the login that SQL server uses, Run OUTLOOK
> and make sure you can send mail.
> 2. Make sure that the default address book is the one you wish to have
> active when SQL sends mail.
> 3. Make sure SQL Server is running using a Domain Login that is part of the
> administrators group.
> 4. Make sure that the profile is properly entered in the SEM SQL MAil
> profile.
> 5. Make sure SQL mail is running.

> THese are the most common probs..

> XP_sendmail may be used by anyone, however it runs in the security context
> of SQL Server, which usually has administrative rights...

> From BOL

> Troubleshooting SQL Mail with Exchange Server
> Typically, errors in starting a SQL Mail session or sending mail from SQL
> Mail with Microsoft? Exchange Server fall into two categories: permissions
> problems and Exchange client setup problems. For more information about SQL
> Mail, see SQL Mail.

> Examine this list of items, in this order:

> Log on to Microsoft Windows NT? with the user account that will be used for
> the MSSQLServer service. This user account must be an administrator of the
> local computer and a domain account.
> Confirm that the Exchange Server client, Exchnge32.exe, or the Microsoft
> OutlookT client, Outlook.exe, can connect to Exchange Server and that e-mail
> can be sent.
> Confirm that the Exchange Server profile used does not have a Personal
> Message Store (.pst).
> On the Services tab, confirm that the only services available are Microsoft
> Exchange Server and Personal Address Book, and then click the Delivery tab.
> Confirm that the selection in the Deliver To box is the mailbox on Exchange
> Server, which should have a name similar to "Mailbox - <Friendly User Name>
>  (where <Friendly User Name> is the name of the user who logged on to
> Windows NT in Step 1).
> To run SQL Mail with Exchange Server, the MSSQLServer service must be run
> under the same user account that logged on in Step 1. In Control Panel,
> double-click Services, select the MSSQLServer service, and then click
> Startup.
> Confirm that the SQL Mail profile is correct. In SQL Server Enterprise
> Manager, expand the server, expand the Support Services folder, select SQL
> Mail, and then right-click. Click Properties, and then on the General tab,
> ensure that the profile name specified in the Profile name box is correct.
> If needed, click Test. The profile name must match the profile name used in
> Step 3.
> Test Microsoft? SQL ServerT access permissions to Exchange Server by
> executing xp_cmdshell, which executes with the same permissions as SQL Mail.
> Use this command to test connectivity to the server, assuming Exchange
> Server is located on a computer named "NTServer".
> xp_cmdshell "NET USE \\NTServer\IPC$"

> If this command fails, Step 3 was not completed correctly.

> It should now be possible either to start SQL Mail automatically or to start
> SQL Mail manually using xp_startmail. When using xp_startmail, the profile
> can be replaced by replacing <Profile name> below with the profile name used
> in Step 3:

> xp_startmail '<Profile name>',''

> --
> Wayne Snyder
> MCSE, MCT, SQL Server MVP
> IKON Education Services -  C{*filter*}te, NC
> (Please respond only to newsgroups.)



Tue, 08 Oct 2002 03:00:00 GMT
 SQL Mail (Help! - Frustrated)
Wayne,

Thanks for the response, I try to follow your steps, however I am using MS
Windows Messaging provided by Windows NT 4.0.

1. I logon as sqladmin user same as the SQL service account. The Windows
Messaging can send mail and receive.
2. The default address book is set as Personal Address book
3. Conifgured as menitoned
4. Configured as mentioned
5. SQL mail is running.

However my error when I try to send test message in Operator properties still
appear as:
"Error 22022:SQL ServerAgent Error: The Mapi Call failed."

If I run the xp_sendmail, different error comes up:
"Server: Msg 17902,
Level 18, State 1, Line 0
General MAPI failure."

Any other solution?

Thanks
Agus Wong
Washington, DC

Quote:

> 1. Log on to the server using the login that SQL server uses, Run OUTLOOK
> and make sure you can send mail.
> 2. Make sure that the default address book is the one you wish to have
> active when SQL sends mail.
> 3. Make sure SQL Server is running using a Domain Login that is part of the
> administrators group.
> 4. Make sure that the profile is properly entered in the SEM SQL MAil
> profile.
> 5. Make sure SQL mail is running.

> THese are the most common probs..

> XP_sendmail may be used by anyone, however it runs in the security context
> of SQL Server, which usually has administrative rights...

> From BOL

> Troubleshooting SQL Mail with Exchange Server
> Typically, errors in starting a SQL Mail session or sending mail from SQL
> Mail with Microsoft? Exchange Server fall into two categories: permissions
> problems and Exchange client setup problems. For more information about SQL
> Mail, see SQL Mail.

> Examine this list of items, in this order:

> Log on to Microsoft Windows NT? with the user account that will be used for
> the MSSQLServer service. This user account must be an administrator of the
> local computer and a domain account.
> Confirm that the Exchange Server client, Exchnge32.exe, or the Microsoft
> OutlookT client, Outlook.exe, can connect to Exchange Server and that e-mail
> can be sent.
> Confirm that the Exchange Server profile used does not have a Personal
> Message Store (.pst).
> On the Services tab, confirm that the only services available are Microsoft
> Exchange Server and Personal Address Book, and then click the Delivery tab.
> Confirm that the selection in the Deliver To box is the mailbox on Exchange
> Server, which should have a name similar to "Mailbox - <Friendly User Name>
>  (where <Friendly User Name> is the name of the user who logged on to
> Windows NT in Step 1).
> To run SQL Mail with Exchange Server, the MSSQLServer service must be run
> under the same user account that logged on in Step 1. In Control Panel,
> double-click Services, select the MSSQLServer service, and then click
> Startup.
> Confirm that the SQL Mail profile is correct. In SQL Server Enterprise
> Manager, expand the server, expand the Support Services folder, select SQL
> Mail, and then right-click. Click Properties, and then on the General tab,
> ensure that the profile name specified in the Profile name box is correct.
> If needed, click Test. The profile name must match the profile name used in
> Step 3.
> Test Microsoft? SQL ServerT access permissions to Exchange Server by
> executing xp_cmdshell, which executes with the same permissions as SQL Mail.
> Use this command to test connectivity to the server, assuming Exchange
> Server is located on a computer named "NTServer".
> xp_cmdshell "NET USE \\NTServer\IPC$"

> If this command fails, Step 3 was not completed correctly.

> It should now be possible either to start SQL Mail automatically or to start
> SQL Mail manually using xp_startmail. When using xp_startmail, the profile
> can be replaced by replacing <Profile name> below with the profile name used
> in Step 3:

> xp_startmail '<Profile name>',''

> --
> Wayne Snyder
> MCSE, MCT, SQL Server MVP
> IKON Education Services -  C{*filter*}te, NC
> (Please respond only to newsgroups.)



Tue, 08 Oct 2002 03:00:00 GMT
 SQL Mail (Help! - Frustrated)
Wayne,

Thanks for the response, I try to follow your steps, however I am using MS
Windows Messaging provided by Windows NT 4.0.

1. I logon as sqladmin user same as the SQL service account. The Windows
Messaging can send mail and receive.
2. The default address book is set as Personal Address book
3. Conifgured as menitoned
4. Configured as mentioned
5. SQL mail is running.

However my error when I try to send test message in Operator properties still
appear as:
"Error 22022:SQL ServerAgent Error: The Mapi Call failed."

If I run the xp_sendmail, different error comes up:
"Server: Msg 17902,
Level 18, State 1, Line 0
General MAPI failure."

Any other solution?

Thanks
Agus Wong
Washington, DC

Quote:

> 1. Log on to the server using the login that SQL server uses, Run OUTLOOK
> and make sure you can send mail.
> 2. Make sure that the default address book is the one you wish to have
> active when SQL sends mail.
> 3. Make sure SQL Server is running using a Domain Login that is part of the
> administrators group.
> 4. Make sure that the profile is properly entered in the SEM SQL MAil
> profile.
> 5. Make sure SQL mail is running.

> THese are the most common probs..

> XP_sendmail may be used by anyone, however it runs in the security context
> of SQL Server, which usually has administrative rights...

> From BOL

> Troubleshooting SQL Mail with Exchange Server
> Typically, errors in starting a SQL Mail session or sending mail from SQL
> Mail with Microsoft? Exchange Server fall into two categories: permissions
> problems and Exchange client setup problems. For more information about SQL
> Mail, see SQL Mail.

> Examine this list of items, in this order:

> Log on to Microsoft Windows NT? with the user account that will be used for
> the MSSQLServer service. This user account must be an administrator of the
> local computer and a domain account.
> Confirm that the Exchange Server client, Exchnge32.exe, or the Microsoft
> OutlookT client, Outlook.exe, can connect to Exchange Server and that e-mail
> can be sent.
> Confirm that the Exchange Server profile used does not have a Personal
> Message Store (.pst).
> On the Services tab, confirm that the only services available are Microsoft
> Exchange Server and Personal Address Book, and then click the Delivery tab.
> Confirm that the selection in the Deliver To box is the mailbox on Exchange
> Server, which should have a name similar to "Mailbox - <Friendly User Name>
>  (where <Friendly User Name> is the name of the user who logged on to
> Windows NT in Step 1).
> To run SQL Mail with Exchange Server, the MSSQLServer service must be run
> under the same user account that logged on in Step 1. In Control Panel,
> double-click Services, select the MSSQLServer service, and then click
> Startup.
> Confirm that the SQL Mail profile is correct. In SQL Server Enterprise
> Manager, expand the server, expand the Support Services folder, select SQL
> Mail, and then right-click. Click Properties, and then on the General tab,
> ensure that the profile name specified in the Profile name box is correct.
> If needed, click Test. The profile name must match the profile name used in
> Step 3.
> Test Microsoft? SQL ServerT access permissions to Exchange Server by
> executing xp_cmdshell, which executes with the same permissions as SQL Mail.
> Use this command to test connectivity to the server, assuming Exchange
> Server is located on a computer named "NTServer".
> xp_cmdshell "NET USE \\NTServer\IPC$"

> If this command fails, Step 3 was not completed correctly.

> It should now be possible either to start SQL Mail automatically or to start
> SQL Mail manually using xp_startmail. When using xp_startmail, the profile
> can be replaced by replacing <Profile name> below with the profile name used
> in Step 3:

> xp_startmail '<Profile name>',''

> --
> Wayne Snyder
> MCSE, MCT, SQL Server MVP
> IKON Education Services -  C{*filter*}te, NC
> (Please respond only to newsgroups.)



Tue, 08 Oct 2002 03:00:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. SQL Mail Help Help Help !!!!

2. Tired...Frustrated..Confused...Please Help

3. Frustrated with DTS! Help

4. REALLY FRUSTRATED. PLEASE HELP

5. vb.Net is very frustrating - HELP!!!!!

6. Hrmm, dont know if this is right but it sure has me frustrated, Help Please

7. Need Help Am Frustrated

8. SQL server 7 agent mail / SQL mail setup questions

9. SQL Mail vs SQL Agent Mail

10. SQL Mail (SQL-2000) via Lotus cc:Mail (DB8)

11. Setting up SQL Agent Mail and SQL Mail

12. Send E-Mail Without Using SQL Mail in SQL Server (Q312839)


 
Powered by phpBB® Forum Software