Migration issues

rated by 0 users
This post has 0 verified answers | 2 Replies | 2 Followers

Suggest an Answer

Lightweight Poster

Points 334

Matt Beardon posted on Sat, Feb 5 2011 9:04 AM

rated by 0 users

I'm trying to migrate a clients sbs2003 to sbs2008 and after logging into the sbs 2008 box it reports the installation failed.

However, AD is replicating as well as Exchange in installed, Sharepoint is installed but does not work. I've tried running some wisards, move data worked for everything apart from sharepoint data, when I run the internet setup task it reports it cannot configure and to run the repair wizards.

Can I reinstall the wizards and sharepoint? or does it mean a rebuild? I'm running a virtual sbs2003 as the client is using the same hardware for the 2008 box. So can I remove installed exchange/ad parts rather than restoring from tape? (which is out of action as its attached the 2008 box)

Truncated log below...

[3444] 110204.190641.9922: Task: ClientDeployment.GPOTask succeed with C:\Program Files\Windows Small Business Server\Bin\GPOTask.exe /config:C:\Users\administrator.REDINC\AppData\Local\Temp\tmp63CA.tmp
[3444] 110204.190642.0078: Setup: DoWork is trying function=Void OpenDSGPO() times=0
[3444] 110204.190642.0858: Setup: SetPolicy SOFTWARE\Microsoft\SmallBusinessServer\ClientSetup Version <6.0.5601> String 2
[3444] 110204.190642.0858: Setup: DoWork is trying function=Void SetPolicy() times=0
[3444] 110204.190642.2730: Task: Policy setting Software\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit:REDINC\Domain Admins:REG_SZ:REDINC\Domain Admins
[3444] 110204.190642.2730: Setup: SetPolicy Software\Policies\Microsoft\Windows NT\Terminal Services\RAUnsolicit REDINC\Domain Admins <REDINC\Domain Admins> String 2
[3444] 110204.190642.2730: Setup: DoWork is trying function=Void SetPolicy() times=0
[3444] 110204.190642.8970: Task: Finish of task ClientDeployment.GPOTask
[3444] 110204.190642.8970: Task: In Task ConfigureGP:
[3444] 110204.190642.8970: Setup: Task ConfigureGP succeeded.
[3444] 110204.190642.8970: Task: Task ("ConfigureGP") execution complete.
[3444] 110204.190642.8970: TaskManagement: Exiting ProgressManager.UpdateProgress(100), not updating since the task is complete.
[3444] 110204.190642.9438: Task: Running Task("ConfigureSharePointTask") with TaskProcessor("NET").
[3444] 110204.190643.0062: Task: Getting the server name used during staging.
[3444] 110204.190643.0062: Task: The sharepoint url for the default site is: http://win-eugso7lo7py/
[3444] 110204.190643.0062: Task: Getting the port for SharePoint to listen on
[3444] 110204.190643.0062: Task: The port for SharePoint to listen on is: 987
[3444] 110204.190643.0062: Task: Building the Uri for the SharePoint site.
[3444] 110204.190643.0062: Task: The sharepoint url for the new site is: https://sites:987/
[3444] 110204.190643.0062: Task: Creating and provisioning the new sharepoint web application
[3444] 110204.191428.7130: Task: Getting an instance of DataLink.RuntimeData
[3444] 110204.191428.7130: Task: Adding the root sharepoint site to the web application
[3444] 110204.191428.7130: Task: The id for the template to use is: STS#0
[3444] 110204.191428.7130: Task: Currently logged on user: administrator
[3444] 110204.191428.7130: Task: Configuring SharePoint in DomainJoin scenario. Obtaining properties for currently logged on user
[3444] 110204.191458.8366: Task: Unprovisioning the default Wss V3 site: SharePoint - 80
[3444] 110204.191500.8958: Task: Setting the Default Website to AutoStart
[3444] 110204.191501.0674: Task: In Task ConfigureSharePointTask: Windows SharePoint Services is not configured.
[3444] 110204.191501.0674: Setup: Task ConfigureSharePointTask failed.
[3444] 110204.191501.0674: TaskManagement: In TaskScheduler.RunTasks(): The "ConfigureSharePointTask" Task or the "NET" TaskProcessor threw an Exception during the ITaskProcessor.Run() call:System.Runtime.InteropServices.COMException (0x800705B4): This operation returned because the timeout period expired.

[3444] 110204.191501.0674: Setup: An error was encountered on the TME thread: System.Runtime.InteropServices.COMException (0x800705B4): This operation returned because the timeout period expired.

   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_AdsObject()
   at System.DirectoryServices.PropertyValueCollection.PopulateList()
   at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
   at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.get_DomainName()
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.QueryAD(DirectoryEntry root, String filter, String parameter, String[] attributes)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.FindUserSearchResult(DirectoryEntry root, String userLogonName)
   at Microsoft.WindowsServerSolutions.Admin.Common.AD.FindUser(String userLogonName)
   at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointTask.SetUserInfo(ITaskDataLink DataLink, String userLogin, String& userName, String& userEmail)
   at Microsoft.WindowsServerSolutions.IWorker.Tasks.ConfigureSharePointTask.Run(ITaskDataLink DataLink)
   at Microsoft.WindowsServerSolutions.TaskManagement.TaskProcessors.NetTaskProcessor.Run(Task currentTask, ITaskDataLink dataLink)
   at Microsoft.WindowsServerSolutions.TaskManagement.Data.Task.Run(ITaskDataLink dataLink, IDictionary`2 taskProcessorMap)
   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(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle 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)
   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.Control.ControlNativeWindow.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(Int32 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.WizardFrameView.Create()
   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)
[3088] 110204.191501.1922: Setup: Removed the password.
[3088] 110204.191501.2078: Setup: Deleting scheduled task at path Microsoft\Windows\Windows Small Business Server 2008 with name Setup
[3088] 110204.191501.7382: Setup: Removed SBSSetup from the RunOnce.

thanks in advance

Matt

| Post Points: 21

All Replies

Site supremo

Points 84,751

David Overton replied on Sat, Feb 5 2011 3:12 PM

rated by 0 users

Hi Matt,

have you looked at sections on Technet such as http://technet.microsoft.com/en-us/library/dd540850(WS.10).aspx

I would also check what is / isn;t working. If it is just WSS then things should be fine. If AD replication or Exchange is not fully functional then you might want to do a re-install / migration to ensure things are going smoothly

Thanks

David

| Post Points: 21

Lightweight Poster

Points 334

Matt Beardon replied on Sat, Feb 5 2011 6:18 PM

rated by 0 users

Hi David

Thanks for the reply, exchange and AD seem to be ok, the main issue looks like the migration connect to internet wizards, although I can get past this using the fix my network wizard.

Can I uninstall exchange and demote the server from AD and restart the migration - is that the best way? there is a backup but the client is using email on the old server while I check the server. they need the server during the week so downtime is limited to friday nights and saturdays.

I've heard sbs 2011 is supposed to be easier to migrate than sbs2008 whats your view on this?

regards

Matt

| Post Points: 5

Previous | Next

Page 1 of 1 (3 items) | RSS

Migration issues

rated by 0 users This post has 0 verified answers | 2 Replies | 2 Followers

All Replies

rated by 0 users
This post has 0 verified answers | 2 Replies | 2 Followers