KB‎ > ‎

System.Runtime.InteropServices.ExternalException When Publishing to HTML

 This article is suitable for an IT Adminstrator

Ref: 20090812
Last Edited: September 28th, 2011

The publication log displays the following error:

System.Runtime.InteropServices.ExternalException: Cannot execute a program. The command being executed was "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\vbc.exe" /noconfig @"C:\Documents and Settings\ProcelTriaster\Local Settings\Temp\xb-7iki-.cmdline".
at System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
at System.CodeDom.Compiler.Executor.ExecWaitWithCapture(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
at System.CodeDom.Compiler.CodeCompiler.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs)
at Microsoft.VisualBasic.VBCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
at System.CodeDom.Compiler.CodeCompiler.FromDomBatch(CompilerParameters options, CodeCompileUnit[] ea)
at System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromDomBatch(CompilerParameters options, CodeCompileUnit[] ea)
at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromDom(CompilerParameters options, CodeCompileUnit[] compilationUnits)
at System.Xml.Xsl.XsltOld.Compiler.CompileAssembly(ScriptingLanguage lang, Hashtable typeDecls, String nsName, Evidence evidence)
at System.Xml.Xsl.XsltOld.Compiler.CompileScript(Evidence evidence)
at System.Xml.Xsl.XsltOld.Compiler.Compile(NavigatorInput input, XmlResolver xmlResolver, Evidence evidence)
at System.Xml.Xsl.XslTransform.Compile(XPathNavigator stylesheet, XmlResolver resolver, Evidence evidence)
at System.Xml.Xsl.XslTransform.Load(String url, XmlResolver resolver)
at Triaster.ProcessNavigator.AnalystEdition.clsTaskManager.ProcessApplyTransformTask(Encyclopaedia& encTaskAttributes)
at Triaster.ProcessNavigator.AnalystEdition.clsTaskManager.ProcessTask(XmlNode& xmlTaskNode)
at Triaster.ProcessNavigator.AnalystEdition.clsTaskManager.ProcessTaskSet(XmlNode& xmlTaskSetNode)

Processing continues for other tasks. The error is intermittent.

The cause is not known and is currently under investigation. It is however a failure in the XSL compiler which prevents reports and search files being produced. This is possibly caused by a serialization bug in the .NET framework, so extensive disk activity could make it more likely.

A possible cause is the XslTransform class was made obsolescent in a recent release of the .NET framework and replaced with the XslCompiledTransform class. Build 4.62.9 has been produced and removes all calls to the XslTransform class and is currently undergoing testing to see if this prevents the problem.

The error is intermittent and does not occur after repeated publishes. Build 4.62.9 appears to have resolved the issue.
Applies to:
  • Process Navigator 4.60, 4.61, 4.62

Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on 0870 402 1234.

                    Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk