Crystal Report runtime is locking [closed]

3

Hello, I'm trying to fix an error in my application, I used FUSLOGVW.exe to find out which ones are missing the dlls that were missing. It's giving me back this msg: But the dll msvcm80.dll hand is part of my project, how can I do it to include it? See error msg error:

  

***** Assembly Binder Log Entry (06/30/2015 @ 08:12:41) ***

     

The operation failed. Result of association: hr = 0x80131040. None   description available.

     

Assembly Manager loaded from:   C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ clr.dll Running under   executable C: \ System \ SisEco.exe   --- Follows a detailed error log.

     

=== Pre-Associated State Information === LOG: DisplayName = msvcm80, Version = 8.0.50727.4940, Culture = Neutral,   PublicKeyToken = b03f5f7f11d50a3a (Fully-specified) LOG: Appbase =   file: /// C: / System / LOG: Initial PrivatePath = NULL LOG: Dynamic Base   = NULL LOG: Base Cache = NULL LOG: AppName = SisEco.exe Calling assembly: (Unknown).   === LOG: this association starts in the default load context. LOG: Using Application Configuration File:   C: \ System \ SisEco.exe.Config LOG: Using Configuration File from   host: LOG: using machine configuration file   C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ config \ machine.config.   LOG: Post-Policy Reference: msvcm80, Version = 8.0.50727.4940,   Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a LOG: the search for   GAC was not successful. LOG: trying to download new URL   file: /// C: /System/msvcm80.dll. LOG: Assembly download was   Successful. Attempting to configure the file: C: \ System \ msvcm80.dll   LOG: Entering the configuration phase executed from the source.   LOG: The assembly name is: msvcm80, Version = 8.0.50727.4927,   Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a AVI: the comparison of   assembly name resulted in incompatibility: Revision Number ERR: a   assembly reference did not match assembly definition   localized. ERR: failed configuration phase executed from   origin with hr = 0x80131040. ERR: Failed to complete configuration of   assembly (hr = 0x80131040). Probing shut down.

     

* Assembly Binder Log Entry (30/06/2015 @ 08:12:41) *

     

The operation failed. Result of association: hr = 0x80131040. None   description available.

     

Assembly Manager loaded from:   C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ clr.dll Running under   executable C: \ System \ SisEco.exe   --- Follows a detailed error log.

     

=== Pre-Associated State Information === LOG: DisplayName = msvcm80, Version = 8.0.50727.4940, Culture = Neutral,   PublicKeyToken = b03f5f7f11d50a3a (Fully-specified) LOG: Appbase =   file: /// C: / System / LOG: Initial PrivatePath = NULL LOG: Dynamic Base   = NULL LOG: Base Cache = NULL LOG: AppName = SisEco.exe Calling assembly: (Unknown).   === LOG: this association starts in the default load context. LOG: Using Application Configuration File:   C: \ System \ SisEco.exe.Config LOG: Using Configuration File from   host: LOG: using machine configuration file   C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ config \ machine.config.   LOG: Post-Policy Reference: msvcm80, Version = 8.0.50727.4940,   Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a LOG: the search for   GAC was not successful. LOG: trying to download new URL   file: /// C: /System/msvcm80.dll. LOG: Assembly download was   Successful. Attempting to configure the file: C: \ System \ msvcm80.dll   LOG: Entering the configuration phase executed from the source.   LOG: The assembly name is: msvcm80, Version = 8.0.50727.4927,   Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a AVI: the comparison of   assembly name resulted in incompatibility: Revision Number ERR: a   assembly reference did not match assembly definition   localized. ERR: failed configuration phase executed from   origin with hr = 0x80131040. ERR: Failed to complete configuration of   assembly (hr = 0x80131040). Probing shut down **

    
asked by anonymous 30.06.2015 / 14:53

1 answer

0

After breaking his head and almost going crazy, I discovered what caused the error.

The ODBC data source was configured only for "User Data Source."

I just switched to the "System Data Source" that everything is working perfectly.

    
01.07.2015 / 22:06