Unable to move one out of >20 mailboxes 5.5 - 5.5 1

[Valier]

Hi

We just moved from ES 5.5, NT 4 to ES, W2k server.
(yes, we know there are newer releases)

We successfully moved all mailboxes but one.
The last one starts off just fine, but it ends unsuccessful.

Eventid 1151: A rule synchronization error (1144) has occurred. The private folder is Rotnivå\inkorgen.
The distinguished name of the owning mailbox.... etc etc
...there are 24 of 24 retreis left.

Followed by Eventid 1008: Unable to move mailbox.

Why?

What goes wrong?

Mike, Stockholm, Sweden

 

[zbnet]

There are corrupt rules that are crashing the MAPI connection used by the move process.

Clean the rules from the mailbox first, then you should be able to move it.

http://support.microsoft.com/default.aspx?scid=kb;en-us;320022

gives details.

 

[Valier]

Thanks zbnet.

I tried that, and found two strange rules, with a lot of hex dump figures in it. Deleted it. (And all other rules too)
But I still get the same error.

The move works fine up to about 70% or so, then it just stops giving me this error.

Now we are trying the rollup for running Outlook 2003 with Exchange 5.5. Maybe that will do it.

Any other clues?

Can I export this single mailbox and import it in some easy way?

Mike

 

[zbnet]

It sounds like the corruption is deeper than just the rules, then. I suspect there are some corrupt items in one of the folders in the mailbox, possibly in the folder you refered to in your first post.

Can Outlook access this folder and open all the items in it? This might show you where the corruption is, and might even enable you to delete the items stopping the mailbox moving.

Alternatively, you could also export the mailbox to a PST file (exmerge will automate this process for the entire mailbox for you easily) and then you can delete the mailbox, and manually recreate it on the new server. Then you would import the PST you made into the new mailbox - again, exmerge can do this for you. This approach loses the single instance storage for this mailbox, but would solve your problem with mailbox corrption.

 

[Valier]

Thanks again, running Exmerge right now.

Fill you in when finished.

 

[Valier]

Hi-hi!

It sort of worked.

Exmerge found a few bad files.
PST file created perfectly.

But could´nt easily import mailbox, because Exmerge only imports to existing mailboxes. And if I created a new one, it did´nt show either because it was never accessed and did not contain anything.

Solved it by deleting the erratic messages in Outlook, and doing the "move mailbox" stuff in Exchange Admin.

Voila!

No more mailboxes on old server.

Thanks.

 

[zbnet]

Exmerge can't import to the new mailbox because the mailbox wasn't initialised. New mailboxes (just after creation) exist only in the directory, they have no corresponding store component. The store component of a mailbox is created the first time the mailbox receives a message, or the first time a client logs on to the mailbox. Exmerge couldn't access the new mailbox because exmerge is a store-only tool (it ignores the directory).

I'm glad you got your problem sorted out.