Another follow up to this… this has been bugging me, you shouldn’t be having any problems with Outlook 2000. I spent some time chatting with our in house MAPI expert about what else could be going on here and there’s a couple of things I’d like to see you guys try.
The first (and easiest) thing is to simply remove the "Unity System profile" from the mail applet and reboot. We recreate the profile automatically when we come up (we had to do that early on since so many folks decided to get rid of it on their own, not knowing what it was). This can clear up the connection.
If that doesn’t work, you may be running into a problem with the MAPI stub functionality in NT land. Since several applications such as IE, Outlook, Outlook Express, Hot Mail etc… install their own MAPI32.DLL, MS put a stub functionality in there to make sure folks like us end up pointing at the right one. There are known problems based on what you’re installing and in what order that might be hosing that up (this is why I was wondering if perhaps you made Express your default reader… that’s one scenario that causes problems with Outlook also on the box). Microsoft has a utility called “FixMAPI.EXE” that is designed to help get things back in order.
Here’s a link to a little information on the FixMAPI program you can read over, there’s other articles out there you can dig around for, but the long and the short of it is we end up being pointed at the wrong MAPI DLL which causes all kinds of grief when we start up. Given the error messages in your post, I'm guessing that's the source of the problem.
http://msdn.microsoft.com/library/psdk/mapi/mapistub_2x42.htm
Once you run this, again, delete our message profile in the mail applet and restart the box. Let me know if either of those worked out for you or not.
Jeff Lindborg
Unity Product Architect
Active Voice
jlindborg@activevoice.com
http://members.home.net/jlindborg
