foxpc123
asked on
Urgent: SBS 2003 to 2011 Migration Failed
Guys,
I'm currently in the middle of a failed migration, it appeared to be going well about 30 minutes in when the wizard appeared and stated that an error had occurred and that the migration could not continue.
There was no specific reason given.
Have looked through the setup.log and the following error is recorded;
Summary
Setup: Caught exception when getting source OS Version: System.Runtime.InteropServ
I'm currently using three guides to prepare for this migration which is the same as all our migrations;
MPECS - SBS 2003 to SBS 2011 Migration guide v1.4.0
SBS 2011 Standard Migrations - Keys to Success Dematzer Small Business Server 2003 to 2011
All of the checks in each of the guides have been completed to the letter with a 'tick' next to each one.
The SBS 2003 BPA runs fine with no issues.
The Exchange pre-deployment readiness tool runs fine with no issues.
The MS IT Environment Health Scanner runs fine with no issues.
The standard Migration tool runs fine with no issues as well.
So it is with a little surprise that this failed.
I have a system state backup of the server before the start, a full NTBackup, and also a shadow protect full image as well.
Whilst the destination server was accessible I've run WBEMTOOL on the source and destination server and can confirm that it is possible to connect to both without any issues (looking at the source server after the failure there were a couple of services which were stopped compared to a recently migrated system which I've started) -it may be that some of those services (I don't remember which) may have allowed the WBEMTOOL to complete o.k.
So the question I have is that the migration wizard on the destination, simply suggested rebuilding the destination server again which I have done and then re-attempt the migration.
Do I need to restore the system state on the source server - or do I re-attempt again?
I'm currently in the middle of a failed migration, it appeared to be going well about 30 minutes in when the wizard appeared and stated that an error had occurred and that the migration could not continue.
There was no specific reason given.
Have looked through the setup.log and the following error is recorded;
Summary
Setup: Caught exception when getting source OS Version: System.Runtime.InteropServ
I'm currently using three guides to prepare for this migration which is the same as all our migrations;
MPECS - SBS 2003 to SBS 2011 Migration guide v1.4.0
SBS 2011 Standard Migrations - Keys to Success Dematzer Small Business Server 2003 to 2011
All of the checks in each of the guides have been completed to the letter with a 'tick' next to each one.
The SBS 2003 BPA runs fine with no issues.
The Exchange pre-deployment readiness tool runs fine with no issues.
The MS IT Environment Health Scanner runs fine with no issues.
The standard Migration tool runs fine with no issues as well.
So it is with a little surprise that this failed.
I have a system state backup of the server before the start, a full NTBackup, and also a shadow protect full image as well.
Whilst the destination server was accessible I've run WBEMTOOL on the source and destination server and can confirm that it is possible to connect to both without any issues (looking at the source server after the failure there were a couple of services which were stopped compared to a recently migrated system which I've started) -it may be that some of those services (I don't remember which) may have allowed the WBEMTOOL to complete o.k.
So the question I have is that the migration wizard on the destination, simply suggested rebuilding the destination server again which I have done and then re-attempt the migration.
Do I need to restore the system state on the source server - or do I re-attempt again?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Are all services running on the SBS2003 server ?
RPC & Remote registry service
- Rancy
RPC & Remote registry service
- Rancy
ASKER
I've recently completed a SBS 2003 migration last week, and have compared the source server to this one and can see that all of the same services are running now.
The RPC and Remote registry service are running now.
Have re-attempted the destination and it fails to dcpromo, so am in the process of reverting everything back to the way it was, so that I can try this again.
The RPC and Remote registry service are running now.
Have re-attempted the destination and it fails to dcpromo, so am in the process of reverting everything back to the way it was, so that I can try this again.
The joys of Sunday working !!
Keep us posted :-)
(I take it you are doing the migration using an admin account specifically set up for the purpose)
Keep us posted :-)
(I take it you are doing the migration using an admin account specifically set up for the purpose)
ASKER
This is becoming a nightmare, have restored system state, and on reboot, I get;
Directory Services could not start because of the following error:
A transaction recover failed.
Error Status: 0xc0000227.
Please click OK to shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.
So head back to directory services restore mode, log back in it comes up with safe mode message box, click ok and then it simply logs off and then shuts down.
Any thoughts?
Directory Services could not start because of the following error:
A transaction recover failed.
Error Status: 0xc0000227.
Please click OK to shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.
So head back to directory services restore mode, log back in it comes up with safe mode message box, click ok and then it simply logs off and then shuts down.
Any thoughts?
Am just building destination server and preping the source server for a migration next weekend (this will be my seventh in as many months - I am now cacking myself :-)
Did you disconnect the destination server from the network first
Not sure what to suggest other than look at your timescale any whether it is best to "regroup" by doing a full server restore from your backup
Did you disconnect the destination server from the network first
Not sure what to suggest other than look at your timescale any whether it is best to "regroup" by doing a full server restore from your backup
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Yes problem is I can't get into DSRM for any length of time to get this step completed - so I'm dead in the water as fas DSRM appears.
ASKER
Have restored the server from the SBS 2003 NTBackup taken earlier. Which has now completely restored and the server appears to be up and running o.k.
I have an issue with SMTP and DNS however, I'll ask that in another question for now this issue is resolved with regards to getting the source server back in an operational state.
I have an issue with SMTP and DNS however, I'll ask that in another question for now this issue is resolved with regards to getting the source server back in an operational state.
ASKER
Thanks for the help guys
ASKER
I'm almost certain now that I'll have to a system state resore to try this again.