Article ID: 2533423 - View products that this article applies to.
After running the SBS 2008 or 2011 Standard setup in join domain/migration mode, you launch the Migration Wizard (“Migrate to Windows SBS” link in the console) and the wizard crashes.
The MigrationWizard.log in “c:\program files\Windows Small Business Server\Logs” will have content similar to this:
This can happen if the info.xml file is incomplete or corrupt.
This article will concentrate on a scenario where the info.xml is incomplete due to a partial SBS setup.
Due to a timing condition, the SBS Setup may not resume after the server restarts following the installation of updates. Once that happens, the server boots into a desktop and no errors are displayed. The server seems to be functional although a number of configuration tasks are missing.
In order to properly recognize that you are experiencing the issue described in this article, please reference the log excerpts below:
Key Section from the end of the Log:
SBS 2011 Standard
Key Section from the end of the Log:
Wizard: TOC sbssetup.finish is NO longer on ExpectedPath
Setup: We are back from the wizard after user clicked Next.
Setup: Get Stage = <null>
Setup: We have a reboot pending.
Setup: Rebooting the box.
Setup: service SPAdminV4 is stopped correctly
Setup: service SPTimerV4 is stopped correctly
Setup: service SPTraceV4 is stopped correctly
Setup: service SPUserCodeV4 is stopped correctly
Setup: service SPWriterV4 is stopped correctly
Setup: service SPSearch4 is stopped correctly
In order to allow the SBS Setup to complete the tasks that are missing, follow the steps below on the SBS 2008 or 2011 Standard server that is experiencing the symptoms and matches the cause described in this article only.
1. Make a full backup of the new SBS server. Due to the way the SBS setup processes operate, you only get one attempt at using these steps to complete the sbssetup process.
2. 2. Use Notepad to create the following registry file, save it and import it.
a. Open Notepad and copy the text below (within the cut here blocks, do not include them) into Notepad.
b. Save the file as “import.reg” (include the quotes so it does not get saved as import.reg.txt).
c. Double click the file, import.reg, to trigger the import.
. 3. Rename the C:\program files\window small business server\data\info.xml file to info.xml.old.
4. 4. Copy C:\program files\windows small business server\data\tme\enginestate\sbssetup-runtimedata.dat to the C:\program files\window small business server\data folder and then rename the file in the data folder from sbssetup-runtimedata.dat to info.xml.
WARNING: Do not copy sbssetup-runtimedata.dat from another machine.
5. Make sure you are logged in with the same administrative account used during the setup and that the password has not changed.
6. 6. Once steps 1 through 5 have been performed, you can attempt to continue the setup by running C:\program files\windows small business server\bin\sbssetup.exe.
There are 3 possible outcomes for this resolution process:
1. It works as expected and you end up with a setup completed screen.
If this is the case your setup is complete and you can continue with the next set of configuration/migration tasks.
2. It works as expected and you end up with a setup completed with errors screen.
If this is the case you will need to review the errors presented on the screen and follow the linked documentation.
3. Setup fails unexpectedly.
You can review the C:\Program Files\Windows Small Business Server\Logs\sbssetup.log to determine the cause of this failure and attempt to troubleshoot it from there. If you wish to re-run sbssetup.exe at this point, you will need to restore the new SBS 2008 or 2011 Standard server from the backup you took in step 1 of the resolution and try steps 2-6 again.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2533423 - Last Review: April 8, 2011 - Revision: 2.0