November 12, 2004 at 8:46 am
What do you mean by local or domain? It is an account I setup on the server. It is called SQLAdmin.
November 12, 2004 at 8:53 am
If it is any consolation, i am having a similar problem, but i have identified it as the Outlook .pst file will either be locked by Outlook, in which case SQL will not send e-mails, (and i recieve a similar message to yours), or SQL locks it and outlook will not open. We are not using Exchange though, as i understand exchange does not use .pst files. We are intending to install Outlook 2000 or 98 next week, and see if that resolves the issue.
If it's any help, the Microsoft KBase reference is :-
http://support.microsoft.com/default.aspx?scid=kb;SL;q263556
November 12, 2004 at 10:19 am
This is the error I am getting, which I am sure is the problem:
Unable to logon to the mail system. You should start a mail client (Microsoft Outlook or Microsoft Exchange Client) to use this feature.
I have Outlook 200o running in the background. And it is setup properly too.
Does anyone have any ideas out there of what else it could be?
November 12, 2004 at 10:39 am
should not need outlook running the background.
Try this: Enterprise Mgr right click server. then security tab. Startup account. is it system account or System account. if system, then that account may not have access/permission to run mail.
SQL mail uses this information to "connect" to outlook.
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
November 12, 2004 at 10:42 am
It is setup to use the SQLAdmin account also.
Any other ideas?
November 12, 2004 at 10:56 am
Maybe it is something with this:
Make sure that that SQL Server's NT user account has permissions on the network to get to the Exchange server.
Where do I check to see if that is setup right?
November 12, 2004 at 11:36 am
When I go the Event Viewer, there is an error in the Lightweight Directory Access Protocol (LDAP). Do any of you know what that is and how to configure it? Maybe that is the problem.
November 16, 2004 at 10:21 pm
I know I have came in on the tail end of a very long discussion here. I have setup email notifications using CDOSYS which does not require Outlook to be installed on the server.
See http://www.sqlservercentral.com/columnists/dharris/sendingsqlnotificationswithcdosys.asp
Regards,
Ian Scott
November 17, 2004 at 10:34 am
It would be nice to just figure this out ya know? I have Outlook 2000 setup and a mail profile setup also. Why would it give me this message when I create a new operator and try to send an email?:
"Unable to logon to mail system. You should start a mail client (Micorsoft Outlook or Microsoft Exchange Client) to use this feature.
December 1, 2004 at 11:40 am
So is everyone out of ideas? I just don't understand why it won't work. I have done everything I was supposed to(I think). I receive emails fine when I have a job setup and have it send me an email through T-SQL, but when I try to set up an operator and do a test email, it gives me this error:
"Unable to logon to mail system. You should start a mail client (Micorsoft Outlook or Microsoft Exchange Client) to use this feature."
When I run this:
exec xp_get_mapi_default_profile
It says: Could not find stored procedure 'xp_get_mapi_default_profile'.
Why would that be?
In Outlook, I am able to receive and send emails.
Any ideas? Please help!!!
December 1, 2004 at 12:16 pm
OK, i ran this:
exec master..xp_get_mapi_profiles
And it gives me my SQLAdmin, like it should right?
Anyone out there?
Viewing 11 posts - 31 through 40 (of 40 total)
You must be logged in to reply to this topic. Login to reply