System.Runtime.InteropServices.SEHException?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Carsten

    #1

    System.Runtime.InteropServices.SEHException?

    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.Reflecti on.Assembly.nLo adImage(Byte[] rawAssembly, Byte[]
    rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark)
    at System.Reflecti on.Assembly.Loa d(Byte[] rawAssembly, Byte[]
    rawSymbolStore, Evidence securityEvidenc e)
    at System.CodeDom. Compiler.CodeCo mpiler.FromFile Batch(CompilerP arameters
    options, String[] fileNames)
    at System.CodeDom. Compiler.CodeCo mpiler.FromSour ceBatch(Compile rParameters
    options, String[] sources)
    at System.CodeDom. Compiler.CodeCo mpiler.FromSour ce(CompilerPara meters
    options, String source)
    at
    System.CodeDom. Compiler.CodeCo mpiler.System.C odeDom.Compiler .ICodeCompiler. CompileAssembly FromSource(Comp ilerParameters
    options, String source)
    at System.Xml.Seri alization.Compi ler.Compile()
    at System.Xml.Seri alization.TempA ssembly..ctor(X mlMapping[] xmlMappings)
    at System.Xml.Seri alization.XmlSe rializer.FromMa ppings(XmlMappi ng[]
    mappings)
    at System.Web.Serv ices.Protocols. SoapClientType. .ctor(Type type)
    at System.Web.Serv ices.Protocols. SoapHttpClientP rotocol..ctor()
    at ITPractice.INFR Aquant.Remote.R emoteINFRAquant ..ctor() in
    G:\Qinterline\S OURCE CODE\INFRAquant \INFRAquant\Web
    References\Remo te\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


Working...