C
Carsten
Hi,
I have a problem with instantiating a Web service. When the constructor for
the proxy is called a SEHException is thrown. The call stack is shown below:
System.Runtime.InteropServices.SEHException: External component has thrown
an exception.
at System.Reflection.Assembly.nLoadImage(Byte[] rawAssembly, Byte[]
rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark)
at System.Reflection.Assembly.Load(Byte[] rawAssembly, Byte[]
rawSymbolStore, Evidence securityEvidence)
at System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters
options, String[] fileNames)
at System.CodeDom.Compiler.CodeCompiler.FromSourceBatch(CompilerParameters
options, String[] sources)
at System.CodeDom.Compiler.CodeCompiler.FromSource(CompilerParameters
options, String source)
at
System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSource(CompilerParameters
options, String source)
at System.Xml.Serialization.Compiler.Compile()
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[]
mappings)
at System.Web.Services.Protocols.SoapClientType..ctor(Type type)
at System.Web.Services.Protocols.SoapHttpClientProtocol..ctor()
at ITPractice.INFRAquant.Remote.RemoteINFRAquant..ctor() in
G:\Qinterline\SOURCE CODE\INFRAquant\INFRAquant\Web
References\Remote\Reference.cs:line 30
It becomes stranger because the same web service is easily created in a test
application and from with NUnit as part of the unit test. But inside my main
application the above fault occurs. If the same code is run on another
almost identically configured machine it runs without problems. Both
machines run Windows XP with the latest security updates, also the SP 1 for
..NET 1.1.
Does anyone have an explanation for the exception thrown?
Regards,
Carsten
I have a problem with instantiating a Web service. When the constructor for
the proxy is called a SEHException is thrown. The call stack is shown below:
System.Runtime.InteropServices.SEHException: External component has thrown
an exception.
at System.Reflection.Assembly.nLoadImage(Byte[] rawAssembly, Byte[]
rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark)
at System.Reflection.Assembly.Load(Byte[] rawAssembly, Byte[]
rawSymbolStore, Evidence securityEvidence)
at System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters
options, String[] fileNames)
at System.CodeDom.Compiler.CodeCompiler.FromSourceBatch(CompilerParameters
options, String[] sources)
at System.CodeDom.Compiler.CodeCompiler.FromSource(CompilerParameters
options, String source)
at
System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSource(CompilerParameters
options, String source)
at System.Xml.Serialization.Compiler.Compile()
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings)
at System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[]
mappings)
at System.Web.Services.Protocols.SoapClientType..ctor(Type type)
at System.Web.Services.Protocols.SoapHttpClientProtocol..ctor()
at ITPractice.INFRAquant.Remote.RemoteINFRAquant..ctor() in
G:\Qinterline\SOURCE CODE\INFRAquant\INFRAquant\Web
References\Remote\Reference.cs:line 30
It becomes stranger because the same web service is easily created in a test
application and from with NUnit as part of the unit test. But inside my main
application the above fault occurs. If the same code is run on another
almost identically configured machine it runs without problems. Both
machines run Windows XP with the latest security updates, also the SP 1 for
..NET 1.1.
Does anyone have an explanation for the exception thrown?
Regards,
Carsten