Event ID: 3288

Donnal,

we get hundreds of them. As you say the official line is it is due to a mailbox being moved and applying SP1 will fix it. I'm not at all convinced about this (seeing as it is wrong!).

Re-enabling the mailbox *seems* to shift the problem to another mailbox temprorarily which is not much help. I have 2 thoughts on this at the moment.

(1) It doesn't matter very much (ignore the message)

(2) It may be connected with this file: c:\windows\systems32\mapi32.dll. Can you tell me how large this file is on your system? Also do you have a mapi32x.dll in the same folder?

By the way - we're using EV 5.0 SP4. We got the errors on SP3 as well.


David
http://messy.bravehost.com/

Donnal,

actually I decided to get my finger out and actually test my hunch rather than just speculating and it *seeems to* have worked. I'm actually pretty confident it'll fix quite a few other quirks in the system as well so it's on my list of *Good Ideas*.

The background and fix is documented here : http://messy.bravehost.com/tryfirst.htm

Could you do me a favour and feedback on this if you try it please -- and also if the article makes any sense or not! :-)? that would be very much appreciated.


David

The bug here is generally more to do with emsmdb32.dll not mapi32.dll.

So steps to follow are:

Upgrade the vault server ESM to Exchange 2003 SP1 or Exchange 2000 sp3 + latest Rollup.

Then check to ensure that there are no dll mismatches on the servers for : emsmdb32.dll

When Exchange System Manager 2003 sp1 is installed on the vault server then the version of the file should be 6.5.7226.0 in all folders. (Search all drives for the file and check the versions and update them where necessary)(Specifcally %windir%\system32).

On systems with Exchange 2000 ESM installed the dll version should be 6.0.6475.0 or greater.

This will require a restart of all the vault services. (preferably reboot)

If this is still not fixing it then I suggest a support call. Good luck.

Ghost,

hmm... swapping emsmdb32.dll in the 1033 directory also works. That's interesting. I think I'm going to stick with the mapi32.dll in System32 change though. It just seems more "right" to me than forcing Outlook to use an Exchange file..?

Going to keep the emsmdb32.dll in mind though, that's really useful in case the other fix is just temprorary or if (ok, when ;-) ) we see other MAPI problems. Thanks for that mate.

I raised this with support in the Spring and got pretty much nowhere.


David

Some more follow up:

We upgraded to SP5 a few weeks ago, I have to say it was completely seamless and successful. We also upgraded the clients to SP5 at the same time and all is well.

However the 3288 errors persist, so this thread caught my eye. I've just found that indeed in the 1033 directory that my EMSMDB32.DLL was not the 6.5.7226 version so I copied the correct one from SYSTEM32 so will wait to see what if this fixes the 3288's.

Glenn,

and what is/was the size of your MAPI32.dll in System32?


David
www.UDStech.com

Sorry it took so long to respond. The mapi32.dll file size is 111KB and i do have the mapi32x.dll. Thanks for your help with this.

Donnal,

Have you implemented the fix at http://messy.bravehost.com/tryfirst.htm?

Did it work? It worked a treat for me.



David

Sorry for the delay but I was just trying to figure out something. I've got the full range of MAPI32 & EMSMDB32 DLLs....and I thought DLL hell died with XP & Server 2003..!

However, I followed the various options that David & Ghost recomended and found that of course if you're importing OL2003 PSTs then you'd better make sure the MAPI32 is the 111k version otherwise if you've got a Unicode file then the PST migrator will fail to read it.

Also, following on with the EMSMDB32 question, I made sure this DLL was the 6.5.7226 version in all the proper places. But then I found if this is used in conjunction with the OL2003 MAPI32 dll then the PSTMIGRATOR will migrate the items ok but the folders it creates in the mailbox will contain chinese like characters. I first found this on a production box and then reproduced it in test, it's quite easy, no reboot or re-sstart required, I just rename the DLLs and with one I get corruption and with the other I don't.

So it looks like I've got to use the pure OL2003 DLLs otherwise I'll get migration issues. So I don't even know if the 3288's will be fixed but it does lend credability to sticking with the latest OL2003 DLLs.

Also, I'm running EV SP5.

The problem occured with this combination.
MAPI32.DLL - 111k Version 1.0.2536.0 (srv03_rtm.030324-2048)
EMSMDB32.DLL - 953k ESM SP1 Version 6.5.7226.0

The problem did not re-occur with this combination
MAPI32.DLL - 111k Version 1.0.2536.0 (srv03_rtm.030324-2048)
EMSMDB32.DLL - 727k OL2003 Version 11.0.6352

Don't think we're done with this topic quite yet.
Glenn

I am going to agree with Glenn Martin. I have been testing both suggestions and found the exact issues that Glenn Martin found. However, I am not getting the 3288's now.


I cannot import PST files with the following:

MAPI32.DLL - 621KB version 6.5.7226.0

I can import PST files with the following:

MAPI32.DLL - 111KB 1.0.2536.0

When I tried the suggestions that Ghost had, I could no longer open Outlook 2003. It shows a splash screen indicating that Outlook could not be started and has the option to "Restart Outlook". Once I changed the EMSMDB32.DLL back to the original, I was able to open Outlook.

My archiving jobs have ran three times since the changes and I have yet to recieve the 3288 error. I am not sure what has changed seeing as how I am using the same DLL's that I started with.

Looks like DLL hell still exist...