I am trying to install SQL Mail to send automatic system messages. The SQL Mail service starts but when I try to test it I get the following error. Does any one have any solution to this problem?
Error: A Mapi error ( error number 273) occured. Unable to get the default MAPI message Store due to MAPI error 273. The information store could not be opened.
I am trying to install SQL Mail to send automatic system messages. The SQL Mail service starts but when I try to test it I get the following error. Does any one have any solution to this problem?
Error: A Mapi error ( error number 273) occured. Unable to get the default MAPI message Store due to MAPI error 273. The information store could not be opened.
I created a new MAPI profile on the server, and it seems to work fine with Outlook. I also dropped the previous default MAPI profile.
Now, when I go to the EM SQLAgent Properties, the only MAP profile offered in the SQLMail drop-down is the old, deleted profile. Also, only the old profile comes up with xp_get_MAPI_profiles.
How can I get SQLAgent to recognize that I've set up a new mail profile?
I recently installed MS SQL server version 7.00.623 on a Win2k server. I installed Outlook 2000 and had the Exchange Administrator create a mailbox in order to use SQL Mail and SQL Server Agent alerts when jobs fail. The Outlook mailbox was set up with a different name then the SQL Server Agent so I created a new account for the SQL Server Agent to match the name of the mailbox. I can send and receive mail from Outlook when logged into the server but I receive the following error when testing the profile in SQL Mail and SQL Server Agent properties:
"[260] Unable to start mail session (reason: Unable to logon (reason: Unable to get the default MAPI Message Store due to MAPI error 273: The information store could not be opened); check the mail profile and/or the SQLServerAgent service startup account)"
The SQL Server Agent account is a NT User type, uses NT Authentication and has sysadmin server privledges and I am attempting to configure the mail while logging in to the server via Terminal Services Client using this account. I have tried to stop and restart the SQL Server Agent services but still receive the same error. When I log into Outlook, I receive a dialog box titled "Enter Password" that asks for a user name, domain name and password. The Exchange Admin. set this up so I have to use my user name, domain and password.
Do I need to install a service pack for SQL Server?
Did changing the SQL Server Agent account cause this to fail?
Does anyone have any insight on why I cannot get SQL Mail configured?
I have several dts packages that run just fine through a third party scheduler. I then put a mail task on them to tell me if the package succeeded or failed. Every time the scheduler gets to the mail task it fails and logs a mapi login failure error. When I execute the dts package on my local box it sends the email with no problems. is it a problem with the robot login or is it associated to the profile? any help would be greatly appreciated.
My IT manager doesn't like the idea that a production process written in DTS needs Outlook 2000 running for DTS Email. I tend to agree that having an app like Outlook 2000 running in the production machine is kind of tacky. Am I missing something here? Why would MS suggest such a solution? Is there a way to configure DTS and Outlook so Outlook doesnt have to be running as an app?
I have a situation where a SQL Maintenance Task is running, and suppose to email a report to the sys admin. Currently I am getting a Microsoft SQL-DMO Error 17903, Mapi Login Failure.
I have tested the Outlook 98 application and the profile is set correctly. I have tried to send an email within SQL and I receive the error above. I have carried all activities suggested by Microsofts Online Books. Can anyone suggest where to go from here. All Service Packs have been applied.
I set up e-mail on my SQL server (7.0) via SMTP. I installed Outlook '97. Typical Installation. Everything was working fine, for couple of days, then I got Dr. Watson messages, about MAPI. Dr.Watson The application, exemapisp32.dbg, generated an application error The error occurred on 11/ 7/2000 @ 11:35:48.437 The exception generated was c0000005 at address 6e4f2630 (<nosymbols>)
Then SQL will give me this message:
Unable to read local eventlog (reason: The data area passed to a system call is too small).
Anyway, try to reinstall Outlook '97, but the problem continues. Any help, will be greatly appreciated.
I have Exchange & sql 7.0 on the same box. I have configured sqlserver and sqlserveragent for the same nt login. Also a Mail profile is created and assigned to SQL-MAIL & SQL-AGENT.
I have a back-up job in SQLSERVER and the notification is set to exchange mail box. For the first time after restarting the exchange services, the notification works fine. But for the subsequent job executions, the notification failed and the message is "MAPI LOGIN FAILED".
(Isn't this fun? Type MAPI and SQL into Google and it almost tilts!)
Here is the situation: 1- When SQL Agent starts, it establishes a MAPI session. For some bizarre design reason, it keeps that session open as long as it is running, rather than re-opening the session when it has mail to send. (this can be days, weeks, or months) 2- Frequently, Exchange servers are clustered. When the virtual server moves to a different physical server in the cluster, - or the Exchange server is restarted for whatever reason - the (above) MAPI session of the SQL Agent gets jammed. 3- SQL Agent tries, and fails to send an E-mail saying (for instance) that a database dump has completed (etc.) 4- User posts a question to some forum, asking for help again.
My solution: I created a job to run on a daily basis to restart the SQL Agent, and re-establish the MAPI session. Voila!
The problem: Now we (sometimes) get the message: [241] Startup error: Unable to initialize error reporting system (reason: The EventLog service has not been started) This is incorrect - the service was never stopped!
*sigh* No hits in Microsoft or Google - Back to the drawing board.
SO: Can anyone think of a way to *test* the MAPI connection in a job step (without actually sending a message), so that the agent restart job is only executed if the MAPI connection is failing?
Scenario:DBMS: SQL Server 2000OS: Windows Server 2003Goal:Enable SQLMAIL via Internet MailProblem:How do I set up the MAPI profile for the SQL Server service account?On Windows 2000 Server, I can use "Control Panel"/"Mail" tocreate a MAPI profile for the SQL Server service account, and thenreference that profile for SQLMAIL in SQL Server and SQL Server Agent.But on Windows Server 2003, there is no "Mail" applet in "Control Panel".How do I create a MAPI profile, for the SQL Server service account,on Windows Server 2003?
hi, I have settup up sql mail and did the following: 1. created an E-mail account and configured Out look by creating a pop3 mail profile. tested it by sending and receiving mail, that is ook 2. I Created one domain account for MSsqlserver and Sql Agent service. both services use same account and start automatically in the control panel-services 3. I used the profile that I created in outlook to test the sql mail but got an error: Error 22030 : A MAPI error ( error number:273) occurred: MapiLogon Ex Failed due to MAPI Error 273: MAPI Logon Failed
I really do not know what went wrong. I followed the steps from bol and still having a problem. Am I missing something.
I do have a valid email account I do have a valid domain account I tested outlook using the email account and it worked. so why sql server does not recognise MAPI.
My next question, How to configure MAPI in Sql server if what I did was wrong.
I'm trying to send a Test Email to Operators defined in a SQL 7.0 server (currently on SP2). And get the following error message: "Error 22022: SQLServerAgent Error: MAPI error: Table too big."
We've checked the email profiles (also performed test on SQL MAIL) and can stop/start SQL Mail successfully. Verified that the accounts are correctly identified with appropriate permissions. MSDB is 150MB with no table that looks abnormal in size.
Has anyone come across this situation? Please let me know. THANKS!!!