I found out what's going on here. the CompressionFilter was never rebuilt and
the dll was referenced to the WSE2.0 SP3. I don't understand why it is not
the batch build. I had to manually rebuilt the project and copied the new dll
to the exe directory and it worked just fine. Anyway, your Assembly binding
viewer does give me a lot clue. Thanks again,
"Zebra" wrote:
> Thanks, Steven.
>
> I checked that the GSDNCompressionFiliter.dll is in the same place as the
> exe. I ran the Assembly Binding Viewer and got the following message. I think
> it is the Post-policy reference: Microsoft.Web.Services2,
> Version=2.0.3.0...... causing the problem since the version should be 2.0.2.0
> which is WSE2.0 Sp2 that I installed. I did install WSE2.0 SP3 at one time
> and removed it and reinstalled WSE2.0 SP2, somehow it still remembers the
> 2.0.3.0 version somewhere. I don't know how to clean up WSE2.0 SP3
> completedly from my machine. Please let me know what you think. I included
> the Assembly Binding details that I got. Thank you so much for your help.
>
>
> *** Assembly Binder Log Entry (6/16/2006 @ 11:48:17 AM) ***
>
> The operation failed.
> Bind result: hr = 0x80070002. The system cannot find the file specified.
>
> Assembly manager loaded from:
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
> Running under executable
> C:\Gsdn_Build\GSDNet_SignalStrength\GSDNetConnection\bin\Debug\GSDNetConnection.exe
> --- A detailed error log follows.
>
> === Pre-bind state information ===
> LOG: User = JDNET\tx17815
> LOG: DisplayName = Microsoft.Web.Services2, Version=2.0.3.0,
> Culture=neutral, PublicKeyToken=31bf3856ad364e35
> (Fully-specified)
> LOG: Appbase =
> file:///C:/Gsdn_Build/GSDNet_SignalStrength/GSDNetConnection/bin/Debug/
> LOG: Initial PrivatePath = NULL
> LOG: Dynamic Base = NULL
> LOG: Cache Base = NULL
> LOG: AppName = NULL
> Calling assembly : GSDNCompressionFiliter, Version=1.0.2355.28133,
> Culture=neutral, PublicKeyToken=null.
> ===
> LOG: This bind starts in default load context.
> LOG: Using application configuration file:
> C:\Gsdn_Build\GSDNet_SignalStrength\GSDNetConnection\bin\Debug\GSDNetConnection.exe.Config
> LOG: Using machine configuration file from
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
> LOG: Publisher policy file is found at
> C:\WINDOWS\assembly\GAC\Policy.2.0.Microsoft.Web.Services2\2.0.2.0__31bf3856ad364e35\Policy.2.0.Microsoft.Web.Services2.xml.
> LOG: Post-policy reference: Microsoft.Web.Services2, Version=2.0.3.0,
> Culture=neutral, PublicKeyToken=31bf3856ad364e35
> LOG: GAC Lookup was unsuccessful.
> LOG: Attempting download of new URL
> file:///C:/Gsdn_Build/GSDNet_SignalStrength/GSDNetConnection/bin/Debug/Microsoft.Web.Services2.DLL.
> LOG: Attempting download of new URL
> file:///C:/Gsdn_Build/GSDNet_SignalStrength/GSDNetConnection/bin/Debug/Microsoft.Web.Services2/Microsoft.Web.Services2.DLL.
> LOG: Attempting download of new URL
> file:///C:/Gsdn_Build/GSDNet_SignalStrength/GSDNetConnection/bin/Debug/Microsoft.Web.Services2.EXE.
> LOG: Attempting download of new URL
> file:///C:/Gsdn_Build/GSDNet_SignalStrength/GSDNetConnection/bin/Debug/Microsoft.Web.Services2/Microsoft.Web.Services2.EXE.
> LOG: All probing URLs attempted and failed.
>
> --
> Thanks,
> Zebra
>
>
> "Steven Cheng[MSFT]" wrote:
>
> > Hello Zebra,
> >
> > Thanks for posting in the webservice newsgroup.
> >
> > From your description, I understand you've upgrade an ASP.NET 1.1
> > webservice which uses WSE 2.0 to ASP.NET 2.0/vs 2005. The application runs
> > well on most machines, but failed with error at initiailze time on one
> > machine ,correct?
> >
> > Based on the error message you posted, the WSE runtime is complaining about
> > a filter component you configured in the WSE configuration section. I
> > reported the "GSDNCompressionFiliter.CompressionInputFiliter,
> > GSDNCompressionFiliter" filter class can not be located, have you checked
> > the deployment of this class/assembly to see whether it is correctly put in
> > the application's assembly bin dir (or if its strong-named you can put it
> > into GAC).
> >
> > And for troubleshooting assembly loading issue, .net framework sdk provides
> > a tool for tracing the assembly binding/locating:
> >
> > #Assembly Binding Log Viewer (Fuslogvw.exe)
> >
http://msdn2.microsoft.com/en-us/library/e74a18c4.aspx > >
> > You can use this tool to check how to runtime is locating the problem
> > assembly.
> >
> > Hope this helps.
> >
> > Regards,
> >
> > Steven Cheng
> > Microsoft MSDN Online Support Lead
> >
> >
> > ==================================================
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================
> >
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> > Get Secure!
www.microsoft.com/security > > (This posting is provided "AS IS", with no warranties, and confers no