Errors with Exchange in Upgrade from 2.4.6.161 to 4.0.3

[tbrokaw]

I have followed all the steps correctly that I know of. Here are the steps I have done.

Write down all Unity Settings i.e. routing

Run DB Walker on Unity database 2.4.6.161 "with no errors reported"

Install Export for 2.4.161 from Unity Tools site

Install Uninstaller for 2.4.6.161 Unity Tools site

Install Importer for 4.0.3 for data Unity Tools site

Export the old 2.4.161 database to be reimported into 4.0.3

Uninstall TSP Connector

Uninstall Unity Version 2.4.6.161

Run Unity Upgrade assistant and install patches and mods off of CD 1 of 3

Run Unity 4.0(3) upgrade form Disk 1 of 3

Run Import Utility to restore from 2x to 4x

Run DB Walker for 4.0.3 "Ran with a few orphaned errors" Fixed those

Installed DIRT BKUP off Unity Tools Site. The most recent one.

This is where my problems begin. I tried to run the DIRT BKUP and it reports a ton of errors and the event viewer lights up like an Xmas tree talking about Event ID: 1023 about the domain admin account can log into the Exchange site but not peticular mailboxes. I searched MS about it and all they talk about is MBClean from the Mail box manager, which I am not even running.

Please help. I am Ghosting my production image onto other disks to try again, but is there an easier fix?

[lindborg]

so, just to be clear the 4.0(3) system is running properly now, right?

I'm assuming you are selecting to backup messages with your DiRT backup, right? Presumably those errors are being kicked out by ExMerge - the most likely reason for that is the account you're running DiRT under does not have SA/RA rights on all the mailstores necessary - although DiRT backup does run a basic test to check for this.

I'd have to see the DiRT backup log and the event log errors in question to speculate further but I'm betting dimes to dollars if you run ExMerge stand alone (which I'd suggest trying) you're going to see the same errors - this is not DiRT or Unity specific.

[tbrokaw]

Now the 4.0.3 system is not running fine. Yes I am selecting to back up my messages and subscriber data to be able to copy it to my other server I have built with a fresh 4.0.3 Exchange 2000, and use DIRT to restore it.

It was running fine where I could log into the Web SA of Unity and see all the subscribers etc. Then I ran the DIRT BKUP and it popped up the log with errors. Then I tried to open my SA Web again and it errored telling me to check my event applicaiton viewer. I attached the DIRT BKUP Log and Application event log for the server.

[lindborg]

If Unity is not running fine then it's not diRT backup that put it in that state - DiRT backup is a read only operation. I've had many people try and tell me DiRT backup broke their system - it's never been the case (and never will be).

You likely have a basic install issue on the local system that needs to be addressed - if Unity is not running cleanly then DiRT backup will surely kick out all kinds of errors...

[tbrokaw]

I am not blaming the DIRT tool at all for this. I started at that point due to the fact it was the last action I did on the server is all. I totally agree that it must be something else, but just am trying to figure out what. I am re-ghosting to another set of disks now to start over again. I have had this upgrade go successfully on a different server running Unity in one of my offices, so I know my steps are good. I will continue rebuilding and see what happens. Thanks for your input.

[lindborg]

The best I can suggest is to exahustively test the base 4.0(3) system before doing the FullDBImport to suck in the 2.x data - this includes creating new users, importing an existing user, leaving a message, making sure the lamp turns on, checking the message and making sure the lamp goes off. Then do the import of 2.x data. By far and away the most common problem with 2.x import stuff is something haywire in the directory and/or message store rights causing a problem with the directory sycn (the SQLSyncSvr process) - after that all bets are off.