Neste caso, foi uma unidade mapeada usando o comando subst , causando o resultado.
Para desativar, abra CMD e digite subst [drive] /d
Para remapear depois, digite subst [drive] [path]
A tentativa de migrar dados de C: para D: por meio do console do SBS está falhando.
O assistente começa a funcionar, mas cai nos primeiros segundos.
Publicarei os registros completos, mas as linhas importantes parecem ser as seguintes:
An exception of type 'Type: System.IO.FileNotFoundException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Message: The system cannot find the file specified. (Exception from HRESULT: 0x80070002) Stack: at TaskScheduler.TaskSchedulerClass.GetFolder(String Path) at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: GetServerBackupTaskStatus: fail to find the task ---> ErrorCode:0
Eu estive google por dias sem sorte.
Descobri que mscorlib é um componente de .net e descobri várias instâncias do arquivo em %windir% , %windir%\winsxs , %windir%\Microsoft.net
Alguém se deparou e consertou isso antes?
---------------------------------------------------------
[1516] 110315.190856.1105: Storage: Initializing...C:\Program Files\Windows Small Business Server\Bin\MoveData.exe
[1516] 110315.190856.2875: Storage: Data Store to be moved: Exchange
[1516] 110315.190856.5305: TaskScheduler: Exception System.IO.FileNotFoundException:
[1516] 110315.190856.5605: Exception:
---------------------------------------
An exception of type 'Type: System.IO.FileNotFoundException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 03/15/2011 19:08:56
Message: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
Stack: at TaskScheduler.TaskSchedulerClass.GetFolder(String Path)
at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
[1516] 110315.190856.5625: Storage: Exception Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException:
[1516] 110315.190856.5635: Exception:
---------------------------------------
[b]An exception of type 'Type: Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException, Common, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.[/b]
Timestamp: 03/15/2011 19:08:56
Message: Failed to find the task path
Stack: at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()
---------------------------------------
An exception of type 'Type: System.IO.FileNotFoundException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 03/15/2011 19:08:56
Message: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
Stack: at TaskScheduler.TaskSchedulerClass.GetFolder(String Path)
at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
[1516] 110315.190856.5665: Storage: Error Retrieving Server Backup Task Status: ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: GetServerBackupTaskStatus: fail to find the task ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Common.WindowsTaskSchedulerException: Failed to find the task path ---> System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
at TaskScheduler.TaskSchedulerClass.GetFolder(String Path)
at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Common.WindowsTaskScheduler..ctor(String taskPath, String taskName)
at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Storage.Common.ServerBackupUtility.GetServerBackupTaskStatus()
at Microsoft.WindowsServerSolutions.Storage.MoveData.Helper.get_ServerBackupTaskState()
[1516] 110315.190857.6216: Storage: Backup Task State: Unknown
[1516] 110315.190857.9347: Storage: Launching the Move Data Wizard!
[1516] 110315.190857.9397: Wizard: Admin:QueryNextPage(null) = Storage.MoveDataWizard.GettingStartedPage
[1516] 110315.190857.9417: Wizard: TOC Storage.MoveDataWizard.GettingStartedPage is on ExpectedPath
[1516] 110315.190857.9577: Wizard: Storage.MoveDataWizard.GettingStartedPage entered
[1516] 110315.190857.9657: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.GettingStartedPage) = Storage.MoveDataWizard.DiagnoseDataStorePage
[1516] 110315.190857.9657: Wizard: TOC Storage.MoveDataWizard.DiagnoseDataStorePage is on ExpectedPath
[1516] 110315.190857.9657: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.DiagnoseDataStorePage) = Storage.MoveDataWizard.NewDataStoreLocationPage
[1516] 110315.190857.9657: Wizard: TOC Storage.MoveDataWizard.NewDataStoreLocationPage is on ExpectedPath
[1516] 110315.190857.9657: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.NewDataStoreLocationPage) = null
[1516] 110315.190857.9697: Wizard: ----------------------------------
[1516] 110315.190857.9697: Wizard: The pages visted:
[1516] 110315.190857.9697: Wizard: Current Page := [TOC Storage.MoveDataWizard.GettingStartedPage]
[1516] 110315.190857.9697: Wizard: [TOC] : TOC Storage.MoveDataWizard.DiagnoseDataStorePage
[1516] 110315.190857.9697: Wizard: [TOC] : TOC Storage.MoveDataWizard.NewDataStoreLocationPage
[1516] 110315.190857.9697: Wizard: Step 1 of 3
[1516] 110315.190907.0406: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.GettingStartedPage) = Storage.MoveDataWizard.DiagnoseDataStorePage
[1516] 110315.190907.0416: Wizard: Storage.MoveDataWizard.GettingStartedPage exited with the button: Next
[1516] 110315.190907.0416: WizardChainEngine Next Clicked: Going to page {0}.: Storage.MoveDataWizard.DiagnoseDataStorePage
[1516] 110315.190907.0496: Wizard: Storage.MoveDataWizard.DiagnoseDataStorePage entered
[1516] 110315.190907.0606: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.DiagnoseDataStorePage) = Storage.MoveDataWizard.NewDataStoreLocationPage
[1516] 110315.190907.0606: Wizard: Admin:QueryNextPage(Storage.MoveDataWizard.NewDataStoreLocationPage) = null
[1516] 110315.190907.0606: Wizard: ----------------------------------
[1516] 110315.190907.0606: Wizard: The pages visted:
[1516] 110315.190907.0606: Wizard: [TOC] visited: TOC Storage.MoveDataWizard.GettingStartedPage
[1516] 110315.190907.0606: Wizard: Current Page := [TOC Storage.MoveDataWizard.DiagnoseDataStorePage]
[1516] 110315.190907.0616: Wizard: [TOC] : TOC Storage.MoveDataWizard.NewDataStoreLocationPage
[1516] 110315.190907.0616: Wizard: Step 2 of 3
[19772] 110315.190907.0656: Storage: Starting System Diagnosis
[19772] 110315.190907.0656: Storage: Getting Data Store Information
[19772] 110315.190907.1086: Storage: Create the list of storage and DB directory path
[19772] 110315.190907.1246: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks..ctor
[19772] 110315.190907.1546: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.Initialize
[19772] 110315.190907.1596: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[19772] 110315.190907.1606: Messaging: Exchange install path: C:\Program Files\Microsoft\Exchange Server\bin
[19772] 110315.190908.4157: Messaging: E12 Monad runspace created ID: Microsoft.PowerShell
[19772] 110315.190908.4237: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190908.4287: Messaging: Executed management shell command: get-exchangeserver
[19772] 110315.190910.2369: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190910.2369: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[19772] 110315.190910.5699: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.GatherAdminInfo
[19772] 110315.190910.5699: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190910.5719: Messaging: Executed management shell command: get-user -Identity "dmagroup.local\Administrator"
[19772] 110315.190911.0870: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.0880: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.0880: Messaging: Executed management shell command: get-mailbox -Identity "d2ae2bf0-48a7-4ce9-9e72-bb3c765454ac"
[19772] 110315.190911.1300: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.1310: Messaging: User Administrator is mail enabled and can use MessagingManagement to send mail.
[19772] 110315.190911.1310: Messaging: Email address used for user: [email protected]
[19772] 110315.190911.1440: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.1440: Messaging: Executed management shell command: get-group -Identity "Domain Admins"
[19772] 110315.190911.1630: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.1640: Messaging: User Administrator is a member of Domain Admins and can use MessagingManagement to manage Exchange.
[19772] 110315.190911.1640: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.GatherAdminInfo
[19772] 110315.190911.1640: Messaging: MessagingManagement enabled for Exchange management: True
[19772] 110315.190911.1640: Messaging: MessagingManagement enabled for mail submission: True
[19772] 110315.190911.1640: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingTasks.Initialize
[19772] 110315.190911.1640: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Tasks.TaskMoveExchangeData.CreateDataStoreDriveList
[19772] 110315.190911.1670: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[19772] 110315.190911.1670: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.1670: Messaging: Executed management shell command: get-storagegroup -Server "SERVER01"
[19772] 110315.190911.2990: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.3070: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[19772] 110315.190911.3070: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.3070: Messaging: Executed management shell command: get-mailboxdatabase -Server "SERVER01"
[19772] 110315.190911.4440: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.4520: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.Initialize
[19772] 110315.190911.4520: Messaging: Begin Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.4520: Messaging: Executed management shell command: get-publicfolderdatabase -Server "SERVER01"
[19772] 110315.190911.5240: Messaging: End Microsoft.WindowsServerSolutions.Messaging.Management.MessagingRunspace.StaticExecute
[19772] 110315.190911.5510: Storage: Data Store Drive/s Details:Name=C:\,Size=12675712420
[19772] 110315.190911.5510: Storage: Data Store Size Details: Current Total Size=12675712420 Required Size=12675712420
[19772] 110315.190911.5510: Storage: MoveData Task can move the Data Store=True
[19772] 110315.190911.8401: Storage: An error was encountered when performing system diagnosis : ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: WMI error occurred while accessing drive ---> System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
at Microsoft.WindowsServerSolutions.Storage.Common.DataStoreInfo.LoadAvailableDrives()
at Microsoft.WindowsServerSolutions.Storage.Common.MoveDataUtil.CanMoveData(DataStoreInfo storeInfo, MoveDataError& error)
at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.DiagnoseDataStore(Object sender, DoWorkEventArgs args)
[1516] 110315.190912.0331: Storage: An error occured during the execution: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: Diagnosing the Data Store failed (see the inner exception) ---> ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.Storage.Common.StorageException: WMI error occurred while accessing drive ---> System.Management.ManagementException: Not found
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Storage.Common.DriveUtil.IsDriveRemovable(String drive)
at Microsoft.WindowsServerSolutions.Storage.Common.DataStoreInfo.LoadAvailableDrives()
at Microsoft.WindowsServerSolutions.Storage.Common.MoveDataUtil.CanMoveData(DataStoreInfo storeInfo, MoveDataError& error)
at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.DiagnoseDataStore(Object sender, DoWorkEventArgs args)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Storage.MoveData.DiagnoseDataStorePagePresenter.backgroundWorker_RunWorkerCompleted(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.Storage.MoveData.MainClass.LaunchMoveDataWizard()
at Microsoft.WindowsServerSolutions.Storage.MoveData.MainClass.Main(String[] args)
Ok, vamos começar pelo topo. Primeiro de tudo, sua análise sobre o arquivo está correta, mas não irá ajudá-lo.
mscorlib.dll é a biblioteca principal do framework .NET. É onde o FileNotFoundException é implementado. A mensagem de erro não indica que há um problema com mscorlib.dll .
O FileNotFoundException é lançado porque o programa que você estava usando (o assistente de migração) tentou acessar o arquivo que simplesmente não existia.
No entanto, neste momento, não tenho certeza se isso é mesmo um problema aqui, já que o registro simplesmente continua. Então, ele ignorou o erro (que leva aos seguintes erros) ou simplesmente não é crítico. No entanto, vamos dar uma breve olhada.
No início do seu log, três exceções estão sendo lançadas. Todos os rastreamentos de pilha e descrições de exceção soam como se o assistente estivesse enumerando as tarefas do Backup do Windows Server no agendador de tarefas (o SBS usa o Agendador de tarefas para configurar as tarefas de backup). Durante esse processo de análise das tarefas de backup, ele tenta obter acesso a uma pasta (possivelmente o local de destino de backup) e essa pasta não existe. Assim, o erro no log.
O assistente trata essas exceções como não críticas, o que pode ser deduzido do fato de que ela continuou gravando no log e nessa linha, que indica que um estado desconhecido é um resultado esperado do processo:
[1516] 110315.190857.6216: Storage: Backup Task State: Unknown
Então, ocorreu um erro e o estado não pôde ser determinado. Vamos seguir em frente.
É aqui que a próxima edição acontece. O último, fatal, que fará com que o mago aborte.
O elemento-chave dessa mensagem de erro é
WMI error occurred while accessing drive
O assistente tentará obter algumas informações na sua unidade e falhará em algum momento.
Essa mensagem de erro resultará em resultados muito melhores na web. Mas eu recomendo que você faça a pesquisa e julgue quais resultados são úteis para você (possivelmente, seu disco de destino é um disco dinâmico )
Desculpe-me por não poder oferecer uma solução direta, mas espero que minha análise ajude você a resolver o problema. Seria bom se você relatasse e escrevesse sua própria resposta se fosse capaz de resolver o problema:)
Tags windows-sbs