Alarming error message

Post #37,898 by Silverlock 5/8/02 9:20:00 AM Reply	Alarming error message Running Office XP on Win2000, boot the system, get started on the morning routine, start Outlook (work mandated) to check for new messages. Get to about the third or fourth message and up pops this thing. error message- "! A recently installed program may cause Microsoft Office or other e-mail-enabled programs to function improperly. Outlook can resolve this conflict without affecting the program that originally caused the problem. Do you want Outlook to resolve this problem?" The only options are yes and no. I try to think what I could have installed that might cause this while cursing MS for the non-information included in the message, and remember I installed the Exchange Administrator Client yesterday. Fire up TechNet and do a search on the phrase "Outlook can resolve this conflict" and get a few hits only one of which seems to fit this particular set of circumstances. The most likely answer from technet shows a conflict with the mapi32.dll file. One problem; the article talks about outlook 2000 or older. I am using Outlook XP AKA Outlook 2002 AKA Outlook 10. Another weirdness; The article says in order to fix the problem you need to either answer yes or no to the error message. Huh????? quote- "RESOLUTION ========== To resolve this behavior, click either Yes or No in the error message." -endquote If you are interested in the seeing the technet note, [link\|http://support.microsoft.com/default.aspx?scid=kb;en-us;Q287570\|here] is knowledgebase article #Q287570 (I chose "no") K-mart. The company that beat Microsoft in customer satisfaction.
Post #37,903 by Meerkat 5/8/02 9:32:10 AM Reply	It's almost as if... ...there are a lot of insiders at M$ doing stuff like this on purpose to drive people into the waiting arms of Linux and the like. I mean, can there really be another reason? To their credit, I guess their making woefulness a standard across their business practices, programs and documentation... On and on and on and on, and on and on and on goes John.
Post #37,952 by scoenye 5/8/02 2:59:19 PM Reply	Uh-oh There have been problems with programs that supply their own MAPI DLL since M$ came up with that API. Netscape was notorious for breaking Outlook 98 if you let it make itself the default e-mail client. Keeping/restoring the Outlook DLL is best. Everything else seems to be a lot less picky and will work with that DLL. Given that it's an other M$ DLL that is causing you grief, you may be OK, but as it is bound to be an older one... Keep an eye out for crashes in Outlook, or any other program you send mail from. Most likely cause will be the replaced MAPI DLL.
Post #37,958 by Silverlock 5/8/02 3:22:23 PM Reply	Not quite the case My understanding of the technet article referenced in my previous post is that the new Outlook XP uses it's own mapi32.dll instead of the shared one in the system32 directory. In other words a bogus error message. K-mart. The company that beat Microsoft in customer satisfaction.
Post #38,066 by scoenye 5/9/02 10:37:58 AM Reply	Yes and no... According to this [link\|http://support.microsoft.com/default.aspx?scid=kb;en-us;Q266418\|KB Q266418], Outlook 2K+ installs a stub mapi32.dll in win\\system32 which routes calls to the "real" mapi32.dll further down the directory tree. Exchange overwrote that stub with a real mapi32.dll file. Nifty... It may be just me, but perhaps "Gordian" would be a good replacement for "XP" in next year's version of things...
Post #38,075 by Silverlock 5/9/02 11:34:44 AM Reply	Gah... That's just wrong. I guess I'll have to let outlook replace the file. I haven't noticed any problems though. Heavy email use and lots of Exchange admin stuff without a hiccup. K-mart. The company that beat Microsoft in customer satisfaction.

Welcome to IWETHEY!