none
Could not load file or assembly MyexternalAssembly.XmlSerializers RRS feed

  • Question

  • Hi,

    Can any one help on the following run time error

    System.IO.FileNotFoundException occurred
      HResult=-2147024894
      Message=Could not load file or assembly 'au.gov.abr.auth.AbrKeyStore.XmlSerializers, Version=1.4.0.3, Culture=neutral, PublicKeyToken=9a9077ece0cbe050' or one of its dependencies. The system cannot find the file specified.
      Source=mscorlib
      FileName=au.gov.abr.auth.AbrKeyStore.XmlSerializers, Version=1.4.0.3, Culture=neutral, PublicKeyToken=9a9077ece0cbe050
      FusionLog==== Pre-bind state information ===
    LOG: DisplayName = au.gov.abr.auth.AbrKeyStore.XmlSerializers, Version=1.4.0.3, Culture=neutral, PublicKeyToken=9a9077ece0cbe050, processorArchitecture=MSIL
     (Fully-specified)
    LOG: Appbase = file:///D:/EBMS3Client/Software Development Kit/Reference Client/Source Code/DotNET-ReferenceClient-SrcCode-1.0.0.2/ReferenceClient_.NET - Release64/ReferenceClient_0_5/bin/Debug/
    LOG: Initial PrivatePath = NULL
    Calling assembly : System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.
    ===
    LOG: This bind starts in default load context.
    LOG: Using application configuration file: D:\EBMS3Client\Software Development Kit\Reference Client\Source Code\DotNET-ReferenceClient-SrcCode-1.0.0.2\ReferenceClient_.NET - Release64\ReferenceClient_0_5\bin\Debug\ReferenceClient_1_0.vshost.exe.Config
    LOG: Using host configuration file:
    LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
    LOG: Post-policy reference: au.gov.abr.auth.AbrKeyStore.XmlSerializers, Version=1.4.0.3, Culture=neutral, PublicKeyToken=9a9077ece0cbe050, processorArchitecture=MSIL
    LOG: Attempting download of new URL file:///D:/EBMS3Client/Software Development Kit/Reference Client/Source Code/DotNET-ReferenceClient-SrcCode-1.0.0.2/ReferenceClient_.NET - Release64/ReferenceClient_0_5/bin/Debug/au.gov.abr.auth.AbrKeyStore.XmlSerializers.DLL.
    LOG: Attempting download of new URL file:///D:/EBMS3Client/Software Development Kit/Reference Client/Source Code/DotNET-ReferenceClient-SrcCode-1.0.0.2/ReferenceClient_.NET - Release64/ReferenceClient_0_5/bin/Debug/au.gov.abr.auth.AbrKeyStore.XmlSerializers/au.gov.abr.auth.AbrKeyStore.XmlSerializers.DLL.
    LOG: Attempting download of new URL file:///D:/EBMS3Client/Software Development Kit/Reference Client/Source Code/DotNET-ReferenceClient-SrcCode-1.0.0.2/ReferenceClient_.NET - Release64/ReferenceClient_0_5/bin/Debug/au.gov.abr.auth.AbrKeyStore.XmlSerializers.EXE.
    LOG: Attempting download of new URL file:///D:/EBMS3Client/Software Development Kit/Reference Client/Source Code/DotNET-ReferenceClient-SrcCode-1.0.0.2/ReferenceClient_.NET - Release64/ReferenceClient_0_5/bin/Debug/au.gov.abr.auth.AbrKeyStore.XmlSerializers/au.gov.abr.auth.AbrKeyStore.XmlSerializers.EXE.

      StackTrace:
           at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
           at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
      InnerException:


    Regards Prince

    Friday, July 25, 2014 8:58 AM

Answers

  • Hi,

    I wonder if the error occurs when you are using the WCF Service.

    Please try to check the following to see if it helps:

    1- Please check if you are referencing an assembly which in turn referencing an old version of unity. for example let's say you have an assembly called ServiceTest.dll which needs an old version of Unity assembly, now when you reference the ServiceTest you should provide it with the old version of Unity, and that makes the problem.

    2- Maybe the output folder where all projects build their assemblies has an old version of unity.

    Then please try to use FuseLogVw application to find out who is loading the old assemblies, just define a path for the log, and run your solution, then check (in FuseLogvw) the first line where the Unity assembly is loaded, double click it and see the calling assembly, and here you go.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Monday, July 28, 2014 7:30 AM
    Moderator

All replies

  • Hi,

    I wonder if the error occurs when you are using the WCF Service.

    Please try to check the following to see if it helps:

    1- Please check if you are referencing an assembly which in turn referencing an old version of unity. for example let's say you have an assembly called ServiceTest.dll which needs an old version of Unity assembly, now when you reference the ServiceTest you should provide it with the old version of Unity, and that makes the problem.

    2- Maybe the output folder where all projects build their assemblies has an old version of unity.

    Then please try to use FuseLogVw application to find out who is loading the old assemblies, just define a path for the log, and run your solution, then check (in FuseLogvw) the first line where the Unity assembly is loaded, double click it and see the calling assembly, and here you go.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Monday, July 28, 2014 7:30 AM
    Moderator
  • Thank you very much Amy Peng. I will check and let you know.

    Regards Prince

    Monday, July 28, 2014 9:02 AM
  • Dear Amy Peng,

    You are right . I think version 32/64 bit compatibility issue. I will change accordingly


    Regards Prince

    Monday, July 28, 2014 10:42 AM