Friday, 29 May 2009

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

This one is a stumper.

The migration is from SBS 2003 to SBS 2008 with approximately 45 users and a 45GB mail store. Most of the users are remotely connected.

The error in the SBSSetup.log:

[4020] 090520.201958.9605: Setup: Exception removing info: System.IO.IOException: The process cannot access the file 'C:\Program Files\Windows Small Business Server\Data\info.xml' because it is being used by another process.

   …Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass._PrepareForFinalExit(Boolean stillHaveOneMoreReboot)

[4020] 090520.202756.1849: Setup: Removed SBSSetup from the RunOnce.

The error in the SBS 2008 Event Log:

image

Application

SBSSetup.exe

CLR20r3 with System.IO.IOException

We just ran the migration on our own hardware by having our client ship us a ShadowProtect image of the source server that we used to complete a Hardware Independent Restore to one of our lab servers.

We used one of our own quad core Xeon 3000 series boxes to run the SBS 2008 setup in Migration Mode on.

The failure is always during the DCPromo and Active Directory replication cycle of the SBS 2008 Migration Mode install.

At this point, we are completely stumped and are looking to get Microsoft support involved to figure out where the problem lies.

Hopefully when we find the solution to the problem, we will post that here.

Note the following:

  • Okay: NIC binding order
  • Clean: DCDiag
  • Clean: NetDiag
  • Clean: RepAdmin /SyncAll
  • Clean: RepAdmin /ShowReps
  • Clean: ADSIEdit.msc of any other DC references
  • Clean: ntdsutil in MetaDataCleanup mode
  • Clean: Active Directory Sites and Services
  • Clean: SBS 2003 Best Practices Analyzer
  • Clean: Migration Preparation Tool on SBS 2003

UPDATE 2009-06-02: A support incident has been opened with Microsoft’s Product Support Services to get this resolved. Hopefully we can.

UPDATE: 2009-07-10: Workaround found: SBS 2003 to 2008 Migration Stall – Event 1001 SBSSetup.exe and CLR20r3 – Workaround Found!

Philip Elder
MPECS Inc.
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

 Subscribe in a reader
at

6 comments:

  1. emiel29 May, 2009 14:14

    Hi, I am stuck with this problem too. Today I was migrating from sbs 2003 to sbs 2008 and when the migration wizard appears it's hanging after 20 minutes and then I get the message "Setup has stopped working" with the event CLR20r3. Hopefully there will be a resolutiom soon.

    ReplyDelete
  2. Philip Elder Cluster MVP29 May, 2009 14:18

    Emiel,

    Please zip up the entire Logs folder on the SBS 2008 server and e-mail it to me. Link on the right for e-mail.

    C:\Program Files\Windows Small Business Server\Logs.

    Thanks,

    Philip

    ReplyDelete
  3. Anonymous01 June, 2009 05:52

    Any solutions on this issue yet?

    ReplyDelete
  4. Philip Elder Cluster MVP01 June, 2009 10:58

    No, at this point we are setting aside some time to work with the Microsoft Product Support Services team to find a resolution.

    Philip

    ReplyDelete
  5. Anonymous10 July, 2009 07:06

    Just wondering if this was ever resolved. Starting a sbs03 to sbs08 migration myself next week :)

    ReplyDelete
  6. Philip Elder Cluster MVP10 July, 2009 09:15

    The post has been updated with a link to the workaround Microsoft came up with.

    The source of the problem was updates being delivered via WSUS on the source server having a high priority deadline that forced them to download and install automatically.

    Disabling WSUS on the source server before starting the migration process is the best way to protect from this particular problem.

    Just in case, here is the link: SBS 2003 to 2008 Migration Stall – Event 1001 SBSSetup.exe and CLR20r3 – Workaround Found!.


    Thanks for the comments,

    Philip

    ReplyDelete

NOTE: All comments are moderated.