Solved

Mailbox move from SBS2003 to W2k8R2 Exchange 2010 mapi error

Posted on 2010-09-01
21
3,058 Views
Last Modified: 2012-05-10
Hello.

I have problem with mailbox move from old Exchange 2003 SP2 on SBS2003 (SP2) to new Exchange 2010 (rollup3) on W2k8R2.

Both servers are DC in one domain/forest and in the same network. All FSMO has old SBS. AD and forest schema is 2003 native.

Old and new exchange work fine, mailflow too. Newly created mailbox on 2010 work, but move request from 2003 box to 2010 fails with error.

Any suggestions?


Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:06


Test user
Failed

Error:
Service 'net.tcp://x2010.xxxx.local/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
    ......
    Lid: 8600    dwParam: 0x6BE      Msg: EEInfo: ProcessID: 4672
    Lid: 12696   dwParam: 0x6BE      Msg: EEInfo: Generation Time: 2010-09-01 15:32:21:482
    Lid: 10648   dwParam: 0x6BE      Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x6BE      Msg: EEInfo: Status: 0
    Lid: 9624    dwParam: 0x6BE      Msg: EEInfo: Detection location: 290
    Lid: 13720   dwParam: 0x6BE      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6BE      Msg: EEInfo: NumberOfParameters: 1
    Lid: 12952   dwParam: 0x6BE      Msg: EEInfo: prm[0]: Long val: 0
    Lid: 53361   StoreEc: 0x80040115
    Lid: 51859  
    Lid: 33649   StoreEc: 0x80040115
    Lid: 43315  
    Lid: 58225   StoreEc: 0x80040115
    Lid: 50835  
    Lid: 62321   StoreEc: 0x80040115
    Lid: 47987  
    Lid: 50033   StoreEc: 0x80040115
    Lid: 52465   StoreEc: 0x80040115
    Lid: 60065  
    Lid: 33777   StoreEc: 0x80040115
    Lid: 59805  
    Lid: 52209   StoreEc: 0x80040115
    Lid: 19778  
    Lid: 27970   StoreEc: 0x80040115
    Lid: 17730  
    Lid: 25922   StoreEc: 0x80040115

Exception details: MapiExceptionNetworkError (80040115): MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
    ......
    Lid: 8600    dwParam: 0x6BE      Msg: EEInfo: ProcessID: 4672
    Lid: 12696   dwParam: 0x6BE      Msg: EEInfo: Generation Time: 2010-09-01 15:32:21:482
    Lid: 10648   dwParam: 0x6BE      Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x6BE      Msg: EEInfo: Status: 0
    Lid: 9624    dwParam: 0x6BE      Msg: EEInfo: Detection location: 290
    Lid: 13720   dwParam: 0x6BE      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6BE      Msg: EEInfo: NumberOfParameters: 1
    Lid: 12952   dwParam: 0x6BE      Msg: EEInfo: prm[0]: Long val: 0
    Lid: 53361   StoreEc: 0x80040115
    Lid: 51859  
    Lid: 33649   StoreEc: 0x80040115
    Lid: 43315  
    Lid: 58225   StoreEc: 0x80040115
    Lid: 50835  
    Lid: 62321   StoreEc: 0x80040115
    Lid: 47987  
    Lid: 50033   StoreEc: 0x80040115
    Lid: 52465   StoreEc: 0x80040115
    Lid: 60065  
    Lid: 33777   StoreEc: 0x80040115
    Lid: 59805  
    Lid: 52209   StoreEc: 0x80040115
    Lid: 19778  
    Lid: 27970   StoreEc: 0x80040115
    Lid: 17730  
    Lid: 25922   StoreEc: 0x80040115

Exchange Management Shell command attempted:
'xxxx.local/MyBusiness/Users/SBSUsers/Test user' | New-MoveRequest -TargetDatabase 'Mailbox Database 1448415644'

Elapsed Time: 00:00:06
0
Comment
Question by:dataline
  • 9
  • 7
  • 2
  • +1
21 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33578364
Is the Microsoft Exchange Replication Service started on the SBS2003 server?
0
 

Author Comment

by:dataline
ID: 33578484
On SBS2003 is only Microsoft Exchange Site Replication Service. Default state is disabled. I tried to start it, but no effect.

On Exchange 2010 is running MS E Replication and MS E Mailbox Replication.
0
 
LVL 1

Expert Comment

by:westjr71
ID: 33587080
0
 
LVL 1

Expert Comment

by:westjr71
ID: 33587105
0
 

Author Comment

by:dataline
ID: 33588262
It's WMI on old 2003 exchange needed for mailbox move?

Best Practicies Analyzer on new server with Exchange 2010 says:

Exchange server:WMI cannot be accessed
Cannot connect to the Windows Management Instrumentation (WMI) repository on server SBS2003. This could be the result of a network or permissions problem. Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

But Best Practicies Analyzer on old SBS2003 report no problem.

It may be permissions problem?
0
 

Expert Comment

by:MarcelMaan
ID: 33607563
Hi Dataline,

Same issue here. I am migrating from exchange 2003 SP2 to exchange 2010 (NON SBS).
I 've searched the net over and over but to no avail.

I am running ISA 2004 on mij exchange 2003 server.
An MS KB states the same problem but for ISA 2006.
Are you running ISA?l
0
 

Author Comment

by:dataline
ID: 33609380
Old server is SBS2003, so is ther ISA 2004. But both servers is in the same internal network.

I tried java script from this MS KB (ISA2006) on my ISA 2004 with no efect.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33609392
Before any migration away from SBS 2003 you should uninstall any ISA server and move the server to a single NIC configuration.

Otherwise the migration could fail.

You may find my migration guide here useful: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html
0
 

Author Comment

by:dataline
ID: 33609628
Bingo. After uninstalling ISA 2004 on old SBS is mailbox move working.

But i testing this in virtual environment on clone servers. In real environment i can't uninstall ISA server :(.

So I go looking for why ISA blocking mailbox move.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33609634
>> In real environment i can't uninstall ISA server :(.
Why not?
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 

Author Comment

by:dataline
ID: 33610053
It's GW for 150 users. But i can export configurations, uninstall ISA, move mailboxes, install ISA and import configuration.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33610067
Presumably if you are moving away from SBS you need to find an alternative to this anyway?
0
 

Author Comment

by:dataline
ID: 33610193
Yes.

Now we have SBS2003 (ISA+exchange) + 2 more DC with W2003 at app servers.

Plan is to upgrade to:
1) W2K8R2+TMG 2010
2) W2K8R2+Ex2010
3) W2K8R2 as backup

app servers are/will be only domain members.


I think the best practice is:
- instaling new server with ex2010
- migrating mailboxes
- uninstall Ex2003 from old sbs
- moving FSMO and CA

All these steps are without loss of availability mail/internet connectivity etc...

Last step wold be uninstalling ISA 2004, demote old SBS from domain and replace it with new server with TMG 2010 (with same IP). This must be done at night.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33610197
The first step with any SBS Migration is to configure the SBS server with a single network card and remove ISA.  Otherwise ISA can cause problems with your migration.

Read my migration guide for the steps involved in migrating, the order in which they are done are important.
0
 

Author Comment

by:dataline
ID: 33610343
I read it.

But if I uninstall old ISA2004 before completion of migration exchange, then i need new TMG server installed first. This means a change of GW in network and on workstations or I must change IP of old SBS.

solution 1:
- instaling new server with ex2010
- backup configuration and uninstall ISA on SBS2003
- migrating mailboxes
- temporarily put back ISA and restore configuration
- several days to solve problems at workstations
- uninstall Ex2003 from old sbs
- moving FSMO and CA
----------------------------------------------
- uninstaling ISA, demote SBS, promote new server and instaling TMG
----------------------------------------------

solution2:
- instaling new server with ex2010
----------------------------------------------
- uninstall ISA on old SBS, change IP on old SBS, promote new server and instaling TMG
----------------------------------------------
- migrating mailboxes
- several days to solve problems at workstations
- uninstall Ex2003 from old sbs
- moving FSMO and CA
- demote SBS
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 33610353
If you are using the ISA IP address as the gateway then simply updating your DHCP settings should quickly update your client IP Configuration
0
 

Author Comment

by:dataline
ID: 33610389
Clients are in different subnets.

There is more then 15 locations in diferrent Towns and connected via HW VPN. IP's  are assigned mostly manually. IP of GW (ISA) is part of configuration of Cisco VPN routers etc...

So this is reason why i do not want to change IP of GW.
0
 

Expert Comment

by:MarcelMaan
ID: 33645212
Our solution:

Place a virtual server in the DMZ and installe xchange 2003.
Make this server a member of the existing Exchnage organization.
Migrate mailboxes from the original mailserver to the Virtual exchange 2003 box.
Migrate from the virtual exchange 2003 to exchange 2010.

In this senario you can get around the connect issue with exchange 2003 -> exchange 2010 in an ISA 2004 enviroment.
Exchnage 2003 -> exchange 2003 goes without any problems though ISA 2004.

Hope it helps.

 
0
 

Accepted Solution

by:
dataline earned 0 total points
ID: 33751941
Hello.

I finally found a solution.

Simply turn off the RPC filter in ISA 2004. Then is Local move request function without uninstalling ISA server.

Problem is in different RPC specification between W2k3, W2k3SP1, W2k3SP2...

I found some patches from MS, but in my case on it no longer matters.

0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34689708
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
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

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this video we show how to create a mailbox database 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 Servers >> Data…
This video discusses moving either the default database or any database to a new volume.

708 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

11 Experts available now in Live!

Get 1:1 Help Now