Thursday 11 June 2009

SBS 2003 to 2008 Migration Stall – Event 1001 SBSSetup.exe and CLR20r3 – Workaround Found!

In our particular case, the actual root of the problem has not been brought to light yet, but we do know how the hiccup is happening and how to get around it now.

The interference was not an Active Directory sourced one as we originally had thought. Yes, the breakdown was seemingly happening during the replication phase of the SBS 2008 OS install, but the replication failure turned out to be a red herring.

The cause of the problem was actually found to be a reboot that happened before replication could actually happen!

How is that?

The Windows Update service was downloading and installing updates despite the fact that WSUS on the source server is set to only allow updates to be downloaded and then the admin notified that there are updates waiting to be installed.

The clue was in a “Windows is installing update X of X” window that flashed by quickly during Wayne and Justin’s troubleshooting.

So, onto the workaround!

Create a blank Migration Mode Answer File that has the Source, Destination, and Gateway IP in it only:


When it comes time to enter the migration specific information, the following screen will show up:


Check both items and click the Next button.

The Time Zone settings will come up next. This step can be done as soon as the above Start the migration window shows up.

Hit SHIFT+F10 key to bring up a command prompt:


Type: Services.msc [Enter]

Once the Services console comes up, we can then stop the required services and subsequently disable them (note the Dell DRAC toolbar):


Attempt 1 with just the Windows Update service stopped and then disabled failed with a blue screen. We managed to salvage the MiniDump file along with the Logs directory on the SBS 2008 box before making the second attempt. We have not examined the dump file yet.

In attempt number two, we stopped and disabled the following:

  • Update Services
  • Windows Update

Attempt 2:image

Once the services have been disabled, check the two radio buttons and click Next:


It is important to make sure that the time and time zone settings are correct:image

Verify the IP settings already present in the Answer File:


When prompted about getting updates, make sure to click the Do not get the most recent installation updates button!


SBS 2008 will then go ahead and make its connections to the network:


Next up is the business’ information:


We are not installing ForeFront nor Windows Live OneCare for Server on this box:


This is what the progress bar will look like when things are working as expected:


Our particular crash would always happen when the progress bar was at the “th” in “whether” found in the above screenshot’s second sentence line.

Finally, after about 45-75 minutes of waiting we had:


Once the above successful migration status is shown, do not forget to re-enable the service, or services, via the Services Console:

  1. Start –> Services.msc [Enter]
  2. Update Services = Automatic (Delayed Start)
    • image
  3. Start the service by clicking on the Start button.
  4. Windows Update = Automatic (Delayed Start)
    • image
  5. Start the service by clicking on the Start button.
  6. Once the services kick in, then the server will be requesting a reboot to reseat them almost immediately:
    • image

We are truly grateful to Wayne and Justin for figuring out how to get things working.

It is now 1230hrs, or just after midnight here, and the mailbox migration has just started on fifty some mailboxes totaling around 50GB worth of data.

The original post on this problem is here:

Philip Elder
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer


Tim Barthelman said...

Great tech note! I just experienced a very similar stall and CLR20r3 error, which caused my SBS2003 to SBS2008 migration installation to fail. How did you resume the SBSsetup or did you flatten the source server are start over? Thanks

Philip Elder Cluster MVP said...


When a proper System State backup was in place, we would back off by restoring the System State.

In this case, we needed to clean out the following references to the new SBS 2008 box:
+ Pull FSMO roles back before shutting down SBS 08 in ADUC and Domains and Trusts. Seize of SBS 08 is gone.
+ DNS A, NS, and IP address in all Zones
+ DSSite.msc - Remove SBS 08
+ ADSIEdit.msc - verify FRS & Sites removal.

From there, a restart of the SBS 2008 install in Migration Mode can happen.

Also note, an alternative to the above methodology is to disable WSUS on the source SBS 2003 server before running the install.

See the SBS 2003 to SBS 2008 Migration Guide we just completed: SBS 2003 to SBS 2008 Migration Guide.

Tim Barthelman said...

Nice migration guide, I've added this to our internal process. To follow-up on our issue, MS Support determined it was caused by a duplicate CNAME record for the source server domain controller which caused a WMI DNS query to fail and crashed wmiprovider thus failing the migration.

Unknown said...


I apologize in advance as I'm fairly new to this, but after experiencing a similar problem I am reinstalling and re-migrating.

Is there a need to restore my backup of my SBS 2003 server in order to complete this, or can I simply create the new answer file and reinstall and re-initiate the migration?

Thank you,


Philip Elder Cluster MVP said...


At the minimum you will need to restore the System State to remove references to the failed new SBS attempt.

Otherwise, an AD cleanup will be required by removing references to new SBS in DNS via A and IP, DSSite.msc by removing references there, and a couple of other spots that I don't remember off the top.


Jon Hooper said...

Excellent Tip!
Worked a charm got past the "th" at last! I'd even resorted to a Post-It note on screen to watch for progress!
Thanks for taking time to share your findings.

Brent Sadler said...

Your guide while a great help doesn't seem to fix our problem on the same error.
The bar makes it to about the y on you before erroring out the same way.
A look at the logs show an error during Certificate Services (Taks ConfiguerCA failed) setup. I had left that option blank in teh answer file. I don't have CA installed on the 2003 server, do I have to install it on there for it to work during migration?

Anonymous said...

Philip, on your June 18, 2009 post you list some things to do upon a failed migration, before a new one can be created. Aren't there steps in Exchange 2003 as well, because there's a new Exchange Administrative Group setup there that references the SBS2008 server? Do you have a list of instructions to do that?

Philip Elder Cluster MVP said...


All of our failed attempts so far have never reached the point where the connectors were installed.

As a result, to remove the Exchange content is something that we have not had to address yet.


PressF12 said...

@ Brent Saddler - I have the same error. After 4 hours on phone with Microsoft - I have restarted the migration just to get to the same error. Have you solved it? Please let me know. Thanks!