Scripting Agent Initialization Failed
Exchange Server kurulumlarında aşağıdaki hata ile karşılabilirsiniz.

Error:
The following error was generated when "$error.Clear();
Set-WERRegistryMarkers;
" was run: "Microsoft.Exchange.Provisioning.ProvisioningBrokerException: Provisioning layer initialization failed: '"Scripting Agent initialization failed: "File is not found: 'E:\Program Files\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml'.""' ---> Microsoft.Exchange.Provisioning.ProvisioningException: "Scripting Agent initialization failed: "File is not found: 'E:\Program Files\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml'."" ---> System.IO.FileNotFoundException: "File is not found: 'E:\Program Files\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml'."
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentConfiguration.Initialize(String xmlConfigPath)
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentConfiguration..ctor(String xmlConfigPath)
--- End of inner exception stack trace ---
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentConfiguration..ctor(String xmlConfigPath)
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentClassFactory.get_Configuration()
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentClassFactory.GetSupportedCmdlets()
at Microsoft.Exchange.Provisioning.ProvisioningBroker.BuildHandlerLookupTable(CmdletExtensionAgent[] enabledAgents, Exception& ex)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__83_0()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed)".
Bu sorun daha çok Exhange Server migration senaryolarında ortaya çıkıyor. Çözümü ise çalışan bir Exhange Server üzerinde aşağıdaki komutu çalıştırmak.
Disable-CmdletExtensionAgent "Scripting Agent"
Bu işlemden sonra kurulumu yeniden çalışmayı deneyin sorunsuz kurulum yapacaktır.
Kurulumlar bittien sonra tekrardan aşağıdaki komutu çalıştırmanız gerekiyor.
Enable-CmdletExtensionAgent "Scripting Agent"
Post Views: 103
Son Yazılar
Arşivler
Kategoriler
Son yorumlar
- RDS “We can’t sign into your account”, Temp Profil Sorunu ve Çözümü için Mehmet Sait YILMAZ
- RDS “We can’t sign into your account”, Temp Profil Sorunu ve Çözümü için Can Karapınar