Solved

Problems moving mailboxes from exchange 5.5 to exchange 2003

Posted on 2003-11-11
9
2,132 Views
Last Modified: 2007-12-19
We currently have Exchange 5.5 running on one of our domain controllers. Last week, we installed exchange server 2003 standard on a new Win 2003 member server. I followed all of the steps in the deployment guide to installing a Exchange 2003 server in a Exchange 5.5 organization, and everything went fine...no problems at all. Once Exchange 2003 was installed, and everything was up and running, I went ahead to try and move one of our mailboxes from the exchange 5.5 server to the 2003 server. The process failed, and the following three events were logged in the application log on the Exchange 2003 member server each time I tried to move a mailbox.

(Note: ZION is the name of our member server, and MAINHOST is the DC, which is also our Exchange 5.5 server)

Event Type: Error
Event Source: MSExchangeAdmin
Event Category: MAPI Session
Event ID: 9175
Date: 11/5/2003
Time: 8:00:26 AM
User: N/A
Computer: ZION
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error
Event Source: MSExchangeAdmin
Event Category: Move Mailbox
Event ID: 9167
Date: 11/5/2003
Time: 8:00:26 AM
User: N/A
Computer: ZION
Description:
Unable to get an administrative interface to the mailbox store on server 'MAINHOST'.
Error: The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error
Event Source: MSExchangeAdmin
Event Category: Move Mailbox
Event ID: 1008
Date: 11/5/2003
Time: 8:00:26 AM
User: N/A
Computer: ZION
Description:
Unable to move mailbox 'Sherry Stone'.
Error: The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.

I also noticed the following event being logged on the member server's application log every 25 minutes.

Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date: 11/5/2003
Time: 8:15:03 AM
User: N/A
Computer: ZION
Description:
Error initializing session for virtual machine ZION. The error number is 0x80040111. Make sure Microsoft Exchange Store is running.
For more information, click http://www.microsoft.com/contentredirect.asp.

On further investigation, I also found that since the Exchange 2003 setup had finished, the following events were being logged regularly in the DC's security log.

Event Type: Failure Audit
Event Source: Security
Event Category: Directory Service Access
Event ID: 565
Date: 11/5/2003
Time: 11:22:33 PM
User: NORFOLK\ZION$
Computer: MAINHOST
Description:
Object Open:
Object Server: DS
Object Type: configuration
Object Name: CN=Configuration,DC=cashn,DC=on,DC=ca
New Handle ID: -
Operation ID: {0,4369963}
Process ID: 260
Primary User Name: MAINHOST$
Primary Domain: NORFOLK
Primary Logon ID: (0x0,0x3E7)
Client User Name: ZION$
Client Domain: NORFOLK
Client Logon ID: (0x0,0x179BD9)
Accesses Control Access
Privileges -
Properties:
---
Manage Replication Topology
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I decided to reboot the DC, as it had not been rebooted since before Exchange 2003 was installed. Once it rebooted, I tried to move a mailbox again, using the exact same process, and it worked fine. I also noticed that the two above events were no longer being logged on the DC or member server. I assumed that the reboot had corrected what ever the problem was, and left the problem.

About three hours later, I went back to move an additional mailbox, and to my surprise, the process again failed, and the initial three events were again logged in the application log. It seemed whatever problem was rectified by a reboot of the DC, came back. I tried to reset the exchange services on the member server, but it did not correct the problem. Further, once I restarted the exchange services on the member server, the other two events began to reappear in the application log (event 8197) on the member server and the security log (event 565) on the DC. The end result was I ended back exactly where I started.

The stores on both servers are mounted, and each server independently seems to be working fine. I have created new mailboxes on the new server, and mail seems to be flowing fine between the exchange 5.5 and 2003 server.  I have a ticket open with Microsoft as well, and they seem to think it's an LDAP problem, but I'm not convinced.  If it was, I wouldn't think it would work at all, ever.  (The LDAP port on exchange 5.5 was changed early on to 391 so it wouldn't interfere with the DC LDAP port.)  

Their recommendation is to remove the DC/GC functionality on the Exchange 5.5 server.  Before I go to all that work, I thought I would let everyone here take a crack at it.
0
Comment
Question by:csmout
  • 7
  • 2
9 Comments
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
Does the 5.5 service account have full privs on the E2K3 server? Is the 5.5 running on W2K domain controller? Is the new E2K3 server account part of the Exchange Domain Servers group?

D
0
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
And how is the AD connector configured?

D
0
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;317338

This supports what MS is saying. Do you have more than 1 GC in your environment? Restart ALL the GCs in your environment, however many there are.

D
0
 

Author Comment

by:csmout
Comment Utility
Yes, the Exchange 5.5 service account has full privs on the new Exchange 2003 server.

The 5.5 server is running on one of our two domain controllers, and that DC has always been a GC.  The other domain controller is in another office in a different site, and that was recently made a GC.  I rebooted both of them, but had the same problems once they came back up.  The E2K3 server account is also a member of the exchange domain servers group.

As far as the AD connector, I followed the exchange 2003 deployment guide, and used the ADZ tools connection agreement wizard to configure the ADC.  Everything seems to be working fine, as changes are replicating between the two directories.  In fact, the only thing I have found that isn't work properly is the move mailbox.

That is the first I have seen that document on Microsoft's site.  Sometimes the search engine on their support site is really picky, as I tried many combinations that should have returned that article but didn't.

Any other ideas??
0
Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
Not right off the top of my head, but I'm still leaning towards the GC problem. Is it possible that we could point the E2K3 server to the GC at the other site? Are you familiar with the DSAccess tab on the server props, and how to try this?

D
0
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;822569


Since 5.5 is running on the DC/GC Windows 2000, I was curious if you already had an ADC installed previously?

d
0
 
LVL 24

Accepted Solution

by:
David Wilhoit earned 500 total points
Comment Utility
0
 

Author Comment

by:csmout
Comment Utility
Yep...that was it.  We ended up bringing a second DC online, and moved the global catalog role to it, and the problem went away.

Thanks Kidego
0
 
LVL 24

Expert Comment

by:David Wilhoit
Comment Utility
You're welcome! Let me know if you have any other problems

david
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Utilizing an array to gracefully append to a list of EmailAddresses
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
This video discusses moving either the default database or any database to a new volume.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

6 Experts available now in Live!

Get 1:1 Help Now