The trigger here was saying yes to updates during the install process which rebooted the server in an awkward way.
[UPDATED 2/11 - New Resolution - Provided by John Bay, Sr. SEE in CSS] Primary Failing Task: None - Setup never completed Last entries in the SBSSETUP.LOG are NOT: Setup: We made it all the way through the Wizard. Setup: Removed the password. Setup: Removed SBSSetup from the RunOnce. Setup: Rebooting the box. Key Error or Exception from the Log: Task: Task ("MUPhase2Task") execution complete. TaskManagement: Previous Task required us to stop processing Tasks for a restart, failure, or cancel. TaskManagement: A Reboot was required. Now=True,Finished=False,Redo=True Setup: TME needs a reboot: bTMEHasMoreToDo=True bPrepareOnly=False Setup: Setting RebootPendingValue to true. Setup: Back from running the TME Setup: Setting ResultFile value to C:\Program Files\Windows Small Business Server\Data\TME\Results\TaskStatusResults634104809850346319.xml Wizard: Admin:QueryNextPage(sbssetup.mainprogress) = null Wizard: WizardChainEngine Next Clicked: Last page, so the wizard isdone, closing wizard frame and returning Setup: Setting ShowBillboards to False Wizard: sbssetup.mainprogress exited with the button: Next 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 Most Common Cause: The server went for the reboot but the setup never resumed. This can happen due to some source environment conditions and a timing issue during the setup during certain installs. Once it happens, the setup is not completed and steps are required to finish it. This assumes that all setup tasks that have completed up until this point have worked. Resolution Summary: 1-Use Notepad to create the following registry file, save it and import it (within the cut here blocks, do not include them). Save the file as import.reg, then double click the file to trigger the import. --cut here-- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Setup\Internal] "Stage"="MainProgress" "InProgress"="True" --cut here--
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Setup\Internal]
"Stage"="MainProgress"
"InProgress"="True"
2- Then you must recreate the info.xml file. The file will be saved as SBSSetup-runtimedata.dat Copy c:\program files\windows small business server\data\tme\enginestate\sbssetup-runtimedata.dat to c:\program files\window small business server\data\info.xml (replace the existing file.
3- Once the registry keys are in place, and the info.xml has been recovered, you can attempt to continue the setup by running c:\program files\windows small business server\bin\sbssetup.exe . Make sure you are using the same administrative account used during the setup This issue is documented here: http://blogs.technet.com/b/sbs/archive/2010/08/03/the-ultimate-guide-to-sbs-2008-setup-failures.aspx
Ed Price - MSFT edited Revision 9. Comment: Need technology in title. Adding tags.
Susan Bradley edited Revision 8. Comment: Adjust for Font size
Susan,
I have a question about this part:
10. RPC Client Access Service Configuration (service not started).
You may see this during the middle of the migration when SBS 2003 and SBS 2011 are both running. Once you remove the SBS 2003 you will see this issue go away. If suddenly your clients Outlook are having issues receiving email, make sure this service is running on the server.
I am 4 days into a migration and I cannot start this service (technically it starts, then stops). I actually posted this on the Partner forums, but am not getting any responses yet. In my searches for an answer, your name seems to be on almost every thread, so I'm hoping you can straighten me out here. If time permits, can you take a look at my forum post and let me know if this is something you have seen before? I migrated a single mailbox and although I can access it from OWA, my Outlook client (this customer is 100% Outlook 2003 and earlier) cannot open the mailbox. Above it says that removing SBS 2003 will make this issue go away, but I need to migrate another 15 mailboxes before I can do that, and I am quite nervous about migrating mailboxes to a server that Outlook cannot talk to. My problem appears to be a side effect of issues updating SPNs.
social.microsoft.com/.../38e8a17d-e991-432b-9611-2dad13418dca
Good