June 26, 2002 at 1:30 pm
I have a SQL 7 server (SP2) running on Windows NT 4.0 (SP6) and I cannot get SQLMail to work. It used to work, but a couple months ago the Exchange group tried to implement a 2way connector from Exchange 5.5 to Active Direcotry and it did not work. They rolled back and several mailboxes were affected, including the one the SQL Mail was configured to use.
I started looking at this last week and everything appeared to be configured correctly. The MSSQLServer service account is a domain user, who has rights to the mailbox. We were using the Exchange Messaging client and could send mail interactively, but starting SQLMail gave us the following error:
Error 22030: A MAPI Error (87) occured. MapiLogonEx Failed due to MAPI Error 87: Invalid Parameter"
We upgrade to Outlook 2000 this week, but the same error occurs. We can send mail interactively, no .PSTs setup. Profile is setup and appears in the drop down.
Any ideas?
Steve Jones
June 26, 2002 at 1:50 pm
I see a bunch of postings about it on Google. Tried recreating the profile while logged in using the account the mail will run under? Voodoo.
Andy
June 26, 2002 at 2:05 pm
Andy has a good suggestion...
Have you tried rebooting your SQL Server?
I've had a MAPI 87 before on SQL 7 due to MAPISP32 being hung.
You can try to kill it or reboot the server.
I really wish microsoft would allow us to use SMTP without MAPI.
June 26, 2002 at 4:02 pm
Deleted and recreated profile, both with Windows Messaging and Outlook.
Rebooted.
Logs definitely show it stopping and startnig the day of the Exchange upgrade (before the upgrade). They also show it failing a few hours after the upgrade. Hasn't worked since.
Did check and there are two MAPI32.DLLs, same size, different dates. That's the next step.
Server rebooted a few times.
Can't upgrade service packs due to application that connects, but don't see a fix that makes sense for this.
Steve Jones
June 27, 2002 at 6:30 am
Have you gone back to basics and tested your profile using outlook on the server?
Steven
June 27, 2002 at 10:01 am
This article contains all the correct MAPI32.DLL versions depending on your version of outlook. Verify that you have the right one installed... possibly reinstall Outlook if there is a major version difference. When your IT group messed this up did they install anything locally or just on the exchange mail server? If they didn't touch anything locally, maybe you should have them create you a new mail user for testing.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q263556
June 27, 2002 at 10:12 am
Profile tested using Outlook. Works fine interactively (when logged in using the MSSQLServer service account). Sends mail without an issue.
Both MAPI32.DLLs are beyond the versions given in the Q article, so I was stuck there. Since they are the same size, I suspect the newer one was just "touched" by the mail guys at MS, but getting them in complete synch is the next step.
Also, setting a new mailbox is another possibility. Again, once I get the client to agree, I'll do that one.
The problems with the Exchange upgrade were with the 2 way connector from Exchange 5.5 to Active Directory to allow the AD to synch abck and forth with the Exchange GAL. They rolled back and nothing was ever done to the local server. However, the mailbox was corrupted, so I suspect somehow Exchange did get changed.
Thanks to everyone for suggestions. I do appreciate it, but I've been diggin through BOL, Technet, MSDN, and Product Support as well as newsgroups and nothing really points to logon failures. It seems more issues are with sending mail and it hanging or stopping. I cannot even get a logon to occur to the Exchange server. The domain account works fine and the server can be rebooted without an issue. Mail just does not run.
Steve Jones
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply