Scripting Agent Initialization Failed: "File is not found" error came up during an Exchange 2016 Setup into an existing Exchange 2010 environment.
More...
The error message is descriptive enough to make us understand that it is something to do with scripting agent within the Exchange environment. The scripting agent is not one of those features that every organization uses either.
Preparing Setup COMPLETED
Stopping Services COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Exchange Management Tools FAILED
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: 'C:\Program File
s\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml'.""' ---> Microso
ft.Exchange.Provisioning.ProvisioningException: "Scripting Agent initialization failed: "File is not
found: 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConf
ig.xml'."" ---> System.IO.FileNotFoundException: "File is not found: 'C:\Program Files\Microsoft\Exc
hange Server\V15\Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml'."
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentConfiguration.Initialize(String xmlConfigPa
th)
at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentConfiguration..ctor(String xmlConfigPath)
--- End of inner exception stack trace ---
The issue here is that the Exchange 2010 has scripting agent enabled and while running the 2016 setup, it is expecting the "ScriptingAgentConfig.xml" file within the folder structure of the Exchange 2016 server.
There are two ways we can go about solving the issue.
First solution is to :
Second solution is to :
Have you come across this error at all? Any other workarounds to get past the error?
I found a third method:
Go to C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents
Locate ScriptAgentConfig.xml.sample and remove .sample (rename) or copy it to ScriptAgentConfig.xml
Re-run the setup
Thanks Tim
thabks so much
Great thank you.
Glad it helped you Shaun