Assembly loading failure

  • Thread starter Thread starter Dan Foody
  • Start date Start date
D

Dan Foody

Does anyone have any ideas how to resolve (or at least find the cause
of) the following problem that occurs during loading of an
application? I've never seen this type of error before and it only
happens on one of three machines I have. Thanks.

Here's the fusion log entry:

*** Assembly Binder Log Entry (1/10/2004 @ 1:55:48 PM) ***

The operation failed.
Bind result: hr = 0x80070057. The parameter is incorrect.

Assembly manager loaded from:
C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\fusion.dll
Running under executable C:\Program Files\Linksys Wireless-B Media
Adapter\bin\SharedMediaManager.exe
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: DisplayName = MslRemoting, Version=1.8.7.57, Culture=neutral,
PublicKeyToken=null
(Fully-specified)
LOG: Appbase = C:\Program Files\Linksys Wireless-B Media Adapter\bin\
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : SharedMediaManager, Version=1.8.7.57,
Culture=neutral, PublicKeyToken=null.
===

LOG: Processing DEVPATH.
LOG: DEVPATH is not set. Falling through to regular bind.
LOG: Policy not being applied to reference at this time (private,
custom, partial, or location-based assembly bind).
LOG: Post-policy reference: MslRemoting, Version=1.8.7.57,
Culture=neutral, PublicKeyToken=null
ERR: Error occurred constructing the probing codebase list.
ERR: Unrecoverable error occurred during pre-download check (hr =
0x80070057).
 
Hello Dan,

Thanks for posting in the group.

Based on my understanding, the problem is: You have one application which
got error in loading on one of three machines. The detailed error message
is:
ERR: Error occurred constructing the probing codebase list.
ERR: Unrecoverable error occurred during pre-download check (hr
=0x80070057).

Based on my experience, this error meesage often happens when APPBASE has
errors. The APPBASE should be a valid URL. Setting it to an invalid URL
should result in undefined behavior.

Since the problem only happens on one machine, could you please help check
the following items?

1) Make sure that Appbase are valid on all machines.
2) Make sure that .NET framework version are the same on all machines.
Please apply the most uptodate service pack of frameworks on the systems.

If you have any more concerns on it, please feel free to post here.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top