Problem with moving mailboxes to new Exchange 2003

[drmuzik]

I recently setup a new SBS2003 server with Exchange 2003 as an additional domain controller. This machine will be my new email server. My old server, also with SBS2003 and Exchange 2003, is still going to remain a domain controller and serve many other functions.

My problem is when I move a mailbox from the old server to the new server then try to connect from outside the network through pop3 or imap, I repeatedly get a user/pass prompt. Once I hit cancel, it gives me the error: "There was a problem logging onto your server. Your password was rejected. Server response: '-ERR The requested mailbox is not available on the server.'"

How do I get the old server to look on the new machine for the mailbox? Mail delivery between mailboxes on the old and new servers works fine, as well as from external accounts to either server. They are both added as local bridgeheads as well. Also, I know the two machines ARE communicating because if I log into "old server's OWA" with "moved mailbox's credentials", it forwards me to "new server's OWA".

 

[markdmac]

You are in for a world of hurt. SBS will stop working on one of your servers within 21 days. SBS can not operate long term with another SBS server on the same cable plant.

Your best bet is to use ExMerge to export mail from the old server to a PST file then import that ont he new server and shutdown the old SBS server permanently.

I hope you find this post helpful.

Regards,

Mark

 

[drmuzik]

Ouch... ok, you're right. I found that out the hard way.

If I demote the new server so it will just on the network doing Exchange tasks, would that work or am I screwed with SBS? I don't want to get rid of the old server... just offload some of the processing.

 

[markdmac]

You are screwed. Your only choice is to purchase the upgrade pack for it so you can convert it to standard server and then demote it from being a DC.

I hope you find this post helpful.

Regards,

Mark

 

[drmuzik]

I just took a shower and got refreshed, and in the middle of the shower it occured to me that we ALREADY have two SBS 2003 servers on the same network... this one I setup yesterday is now the third (all three difference licenses). Here is what's going on:

Server 1 - Original DC, takes care of everything including Exchange
Server 2 - The second server that was already there and setup before I came into the picture. It is not a DC, and merely serves as a gateaway for people to remote desktop into when using VPN.
Server 3 - The server I just setup. I made it an additional DC, and want to make it the primary Exchange server.

So by the logic that Server 2 has already been existing with Server 1 for well over a year now, if I demote Server 3 it should work along with the first two? What's going on?

 

[markdmac]

You sure they did not already put in the upgrade pack? It preserves all of the SBS functionality but allows you to break away the functions like Exchange and SQL to other boxes.

What you are describing is not supposed to be possible. Do you perhaps have different versions of SBS like a mix of 2000 and 2003?

I hope you find this post helpful.

Regards,

Mark

 

[drmuzik]

Alright... upon further investigation I found that server 2 is actually just Windows Server 2003. Not SBS.

So, I am going to reformat server 3 again and setup Windows Server 2003 on it as well.

 

[etdit]

Mark,
That is what I did....used ExMerge to move mailbox to a PST file....then when I used it to try and move the mail back to the Exchange server, I get the below iformation. Any thoughts on what I've done wrong?


From ExMerge.log
[10:08:38] Found 32 mailbox(es) homed on the specified databases.
[10:08:38] Ignored 3 mailbox(es) homed on the specified databases.
[10:10:21] Using attribute 'PR_MESSAGE_DELIVERY_TIME' for date operations.
[10:10:21] Merging data into target store. The program will copy only those messages that do not exist in the target store.
[10:10:21] Associated folder data will NOT be copied to the target store.
[10:10:21] Using 'English (US)' (0x409) as the default locale (Code page 1252)
[10:10:21] All mailboxes will be processed, regardless of locale
[10:10:21] Using default locale for all mailboxes
[10:10:21] Initializing worker thread (Thread0)
[10:10:21] Merging data from file 'H:\CAPERS\SWASSBERG.PST' to mailbox 'Stephanie Wassberg' ('SWASSBERG') on server 'EXMAIL'.
[10:10:22] Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0x8004011d)
[10:10:22] Errors encountered. Copy process aborted for mailbox 'Stephanie Wassberg' ('SWASSBERG').
[10:10:23] Number of items copied from the source store for all mailboxes processed: 0
[10:10:23] Total number of folders processed in the source store: 0
[10:10:23] 0 mailboxes successfully processed. 1 mailboxes were not successfully processed. 0 non-fatal errors encountered.
[10:10:23] Process completion time: 0:00:00:01

 

[markdmac]

etdit

First off from your message I can't figure out if you are saying you used exmerge to backup mailboxes and then tried to restore the data to the same or a different server. The user names must match the PST name. Also, if you have DNS misconfigured it will not work. The Exchange box needs to be able to contact a global catalog.

If the above does not help, then please start a new thread and I will be happy to try and help isolate the problem.

I hope you find this post helpful.

Regards,

Mark

 

[etdit]

Mark,

1. I used Exmerge to backup the Exchange mailbox
2. The pst file name and the user name are both swassberg
3. I attempt to restore the email back to the Exchange mailbox from the pst file utilizing Exmerge utility and that is when I get the error that I posted above.

I am sure it is something really really simple, but it's going over my head right now?

Thanks for responding, Mark.
John

 

[etdit]

forgot to mention that I am using the same server for both.

 

[markdmac]

Most likely your problem is that the ID being used to run ExMerge does not have Send/Receiver As rights to the mailbox in question.

I hope you find this post helpful.

Regards,

Mark