SBS 2003 to 2011 Migration Failure

15 pts.
Tags:
Migration failure
SBS
SBS 2003
sbs 2011
SBS Migration
Small Business Server
I'm running out of ideas on my SBS 2003 to SBS 2011 migration I'm attempting. The SBSSetup.log file contains the text at the end of this post showing where it bombs out. The migration appears to fail on SharePoint. The client doesn't even use SharePoint. I've run the best practices analyzer and all the other steps in the migration documentation twice now with the same result. After the first attempt I restored from backup, fully removed SharePoint and reinstalled it using Microsoft's documentation (manually removed it piece by piece then used Add/Remove to change components on the SBS entry to re-add SharePoint using disc 3 of SBS 2003). And of course, after reinstalling SharePoint I reinstalled 2.0 SP3 for SharePoint. Does anyone have any ideas on what could be causing this problem? The error message doesn't appear to be one publicly documented in this context... [code] [5728] 110627.203055.7836: Task: In Task ConfigureGP: [5728] 110627.203055.7836: Setup: Task ConfigureGP succeeded. [5728] 110627.203055.7836: Task: Task ("ConfigureGP") execution complete. [5728] 110627.203055.7836: TaskManagement: Exiting ProgressManager.UpdateProgress(100), not updating since the task is complete. [5728] 110627.203055.7926: TaskManagement: Task ConfigureWSSConfigCOMPlusForMigrationTask doesn't have cost data [5728] 110627.203055.7926: Task: Running Task(ConfigureWSSConfigCOMPlusForMigrationTask) with Type(Microsoft.WindowsServerSolutions.Setup.Tasks.ConfigureWSSConfigCOMPlusForMigrationTask) and Assembly(IWorkerConfig.dll). [5728] 110627.203055.8176: Task: Configuring COM+ identiy for appID: {edb25e5f-50d2-4258-9e0d-542e64c1f0c3}, the account is mydomain.localAdministrator [5728] 110627.203057.2076: Task: In Task ConfigureWSSConfigCOMPlusForMigrationTask: [5728] 110627.203057.2086: Setup: Task ConfigureWSSConfigCOMPlusForMigrationTask succeeded. [5728] 110627.203057.2086: Task: Task ("ConfigureWSSConfigCOMPlusForMigrationTask") execution complete. [5728] 110627.203057.2166: Task: Running Task(ConfigureSharePointDatabaseTask) with Type(Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointDatabaseTask) and Assembly(IWorkerConfig.dll). [5728] 110627.203057.3246: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureSharePointDatabaseTask" Task threw an Exception during the Run() call:System.Runtime.InteropServices.COMException (0x8000401A): The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri) at System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType) at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object[] props, Boolean bNewObj) at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointDatabaseTask.Run(ITaskDataLink dl) at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink) at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName) [5728] 110627.203057.3256: Setup: An error was encountered on the TME thread: System.Runtime.InteropServices.COMException (0x8000401A): The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri) at System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType) at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object[] props, Boolean bNewObj) at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointDatabaseTask.Run(ITaskDataLink dl) at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink) at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName) at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter._RunTasks(Object sender, DoWorkEventArgs e) [5220] 110627.203057.3896: Setup: _UnhandledExceptionHandler: Setup encountered an error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: The TME thread failed (see the inner exception). ---> System.Runtime.InteropServices.COMException: The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.EnterpriseServices.Thunk.Proxy.CoCreateObject(Type serverType, Boolean bQuerySCInfo, Boolean& bIsAnotherProcess, String& uri) at System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType) at System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(RuntimeType serverType, Object[] props, Boolean bNewObj) at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointDatabaseTask.Run(ITaskDataLink dl) at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink) at Microsoft.WindowsServerSolutions.TaskManagement.TaskScheduler.RunTasks(String taskListId, String stateFileName) at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter._RunTasks(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) --- End of inner exception stack trace --- at Microsoft.WindowsServerSolutions.Setup.SBSSetup.ProgressPagePresenter.TasksCompleted(Object sender, RunWorkerCompletedEventArgs e) --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Delegate.DynamicInvokeImpl(Object[] args) at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Microsoft.WindowsServerSolutions.Common.Wizards.Framework.WizardChainEngine.Launch() at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass._LaunchWizard() at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.RealMain(String[] args) at Microsoft.WindowsServerSolutions.Setup.SBSSetup.MainClass.Main(String[] args) [5220] 110627.203057.4056: Setup: Removed the password. [5220] 110627.203057.4096: Setup: Deleting scheduled task at path MicrosoftWindowsWindows Small Business Server 2011 Standard with name Setup [5220] 110627.203057.4296: Setup: Removed SBSSetup from the RunOnce. [/code]

Answer Wiki

Thanks. We'll let you know when a new response is added.

I just performed a migration from SBS 2003 to SBS 2011 standard about a month ago. Like you, the client didn’t use Sharepoint, or fax. So what I did was just just skip both of those options in the migration tool. I have had no problems with the migration from not swinging the old share point over to the new server.

The problems I did run into were small gaps in the documentation such as migrating the Public folder store and mailbox stores for exchange.

The best advise I can give is to run the best practices analyzer on your sbs2003 box and go through each issue with a fine tooth comb. From there you will have a good baseline. If you have other servers like a 2003 server box for storing files or apps; run the best practice analyzer on those servers too. I also recommend running the exchange best practice analyzer on sbs 2003 to make sure that you exchange is healthy before moving it over.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Vt4l
    I swore I posted my workaround to this but after seeing the above post I notice my reply is gone. I ran the BPA fully and had no errors. I also worked through warnings. Neither were the cause of the problem. The problem is two fold - a bug in the install media and an undocumented no-no during install. I eventually gave up on migration being on-site with limited time (it was a smaller network). I tried to run a new install but ended up with the EXACT same error. At this point I knew something was wrong. I ran across a post stating that when you create the admin account it can't contain the word ADMIN anywhere - first name, last name, username. The installer will allow you to name the account XYZ with first name Admin last name User but it will FAIL. Running a clean install using bogus user names allowed me to do a clean install. While my new clean install ran, I checked out the migration tool. There I noticed there was no spot to specify a second administrator user. My guess is that under the covers sharepoint bombs if you use the word admin in first name, last name or administrator account name. And since the migration tool requires an administrator account (which has always been Administrator on most SBS 2003 installs) this is what I used. I very much suspect if I created a bogus admin account prior to migrating and gave that for the admin account in the migration tool things would have worked. But like I said, I was out a full day trying to get things going and had to cut my losses. Bottom line - do NOT use the word admin anywhere in your admin account or names or you will have problems (even if the installer/tools lets you use them and it's not documented otherwise).
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following