Configuration Error

  • Thread starter Thread starter murphy
  • Start date Start date
M

murphy

I see this error sometimes and fix by rebooting, removing asp.net cache
and rebuilding my solution. This very slow process has now stopped
working. The error log below might mean something the developer who
wrote it but I can't translate it. The file in question is definitely
present in one place. file:///M:/mm_ggipt/GGipt/Qipt/bin/Qiptr.DLL.
The only thing interesting to note is that we are using ClearCase and
M: is ClearCase directory.

Assembly Load Trace: The following information can be helpful to
determine why the assembly 'Qiptr' could not be loaded.


=== Pre-bind state information ===
LOG: DisplayName = Qiptr
(Partial)
LOG: Appbase = file:///M:/mm_ggipt/GGipt/Qipt
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

LOG: Policy not being applied to reference at this time (private,
custom, partial, or location-based assembly bind).
LOG: Post-policy reference: Qiptr
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/qipt/260b95d9/b7578056/Qiptr.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/qipt/260b95d9/b7578056/Qiptr/Qiptr.DLL.
LOG: Attempting download of new URL
file:///M:/mm_ggipt/GGipt/Qipt/bin/Qiptr.DLL.
LOG: Policy not being applied to reference at this time (private,
custom, partial, or location-based assembly bind).
LOG: Post-policy reference: Qiptr, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null
 
An additional note...

1. Index Service is turned off (a reported cause of this kind of
behavior)
2. I was able to get the web to work again by repeating the steps below
several times.

-Mark
 
Hi Mark,

Thanks for your posting. Regarding on the problem you mentioned, there has
some existing issues and most of them are caused by the following things:
1. Using strong-named assembly in asp.net web app which isn't put in the
GAC but in the private bin folder. This may cause some unexpected errors at
runtime.

2. When using Source control tools in Team development, sometimes the
assemlies referenced by your application is updated (build by other
members) however, the reference (metadata)in your application assembly is
not updated which cause the assembly load error. We can try removing the
referenced asssembly and add it(the latest version) again to see whether it
helps.

Please have a look to see whether the above things help. Thanks,


Steven Cheng
Microsoft Online Support

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