MainFrameActions: Packaging (Windows (64-bit)): ScriptCompiler.LoadPreCompiledScriptAssemblies: Loading precompiled script DLLs
MainFrameActions: Packaging (Windows (64-bit)): ScriptCompiler.LoadPreCompiledScriptAssemblies: Found 6 script DLL(s).
MainFrameActions: Packaging (Windows (64-bit)): ScriptCompiler.LoadPreCompiledScriptAssemblies: Loading script DLL: E:\New Folder\4.7\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll
MainFrameActions: Packaging (Windows (64-bit)): Program.Main: ERROR: AutomationTool terminated with exception:
MainFrameActions: Packaging (Windows (64-bit)): Program.Main: ERROR: Exception in AutomationTool: Failed to load script DLL: E:\New Folder\4.7\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll: Could not load file or assembly ‘AutomationScripts.Automation, Version=4.0.0.0, Cultur
MainFrameActions: Packaging (Windows (64-bit)): e=neutral, PublicKeyToken=null’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
MainFrameActions: Packaging (Windows (64-bit)): Stacktrace: at AutomationTool.ScriptCompiler.LoadPreCompiledScriptAssemblies(List1 OutScriptAssemblies) MainFrameActions: Packaging (Windows (64-bit)): at AutomationTool.ScriptCompiler.FindAndCompileAllScripts(List1 AdditionalScriptsFolders)
MainFrameActions: Packaging (Windows (64-bit)): at AutomationTool.Automation.Process(String[] CommandLine)
MainFrameActions: Packaging (Windows (64-bit)): at AutomationTool.Program.MainProc(Object Param)
MainFrameActions: Packaging (Windows (64-bit)): at AutomationTool.InternalUtils.RunSingleInstance(MainProc Main, Object Param)
MainFrameActions: Packaging (Windows (64-bit)): at AutomationTool.Program.Main()
MainFrameActions: Packaging (Windows (64-bit)): Program.Main: ERROR: Failed to load script DLL: E:\New Folder\4.7\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll: Could not load file or assembly ‘AutomationScripts.Automation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
MainFrameActions: Packaging (Windows (64-bit)): ProcessManager.KillAll: Trying to kill 0 spawned processes.
MainFrameActions: Packaging (Windows (64-bit)): Program.Main: AutomationTool exiting with ExitCode=1
MainFrameActions: Packaging (Windows (64-bit)): Domain_ProcessExit
MainFrameActions: Packaging (Windows (64-bit)): ProcessManager.KillAll: Trying to kill 0 spawned processes.
MainFrameActions: Packaging (Windows (64-bit)): copying UAT log files…
MainFrameActions: Packaging (Windows (64-bit)): RunUAT.bat ERROR: AutomationTool was unable to run successfully.
MainFrameActions: Packaging (Windows (64-bit)): BUILD FAILED
Hi vardennnn,
We’ll need more information to offer support:
- Is this the full log?
- What device are you packaging for
- Post your dxdiag
- Can this be reproduced in a clean project
- If this can be reproduced in a clear project, please provide a detailed list of steps to reproduce the issue on our end
Thanks,
.
Hi vardennnn,
Since we have not heard back from you in a few days we are closing this post for tracking purposes. However, if you are still having a problem packaging your project, please respond with the requested information and we will continue to investigate.
Thanks,
.
Just wondering: Is it possible to “close” a question without marking it as “resolved”? It is rather frustrating to go to questions that appear to be resolved (because they are marked so), just to find out that they in fact are not.
…and strangely enough, commenting seems to remove the “resolved” mark.
While it is possible to close the issue without marking it “resolved,” at that point the post is no longer editable from the user’s end. We mark posts “resolved” this way because sometimes the issue is resolved without feedback from the user or abandoned and this way we can keep up with “live” issues. However, if the issue persists without an actual resolution, you can simply reopen it by responding with the requested information and we will continue to investigate problem.
Also, if you posted the question, you can “unaccept” the answer by selecting the check in the circle at the upper left of the answer.