"Laura Papez" <LauraPapez@discussions.microsoft.com> wrote in message
news:F4E77DA3-018D-4F5B-A978-8A7255B0A461@microsoft.com...
> Hi,
>
> I have created a secure Web Service via WSE with the use of WS-Policy. The
> service have been test using a .Net Console application and everything
works.
>
> However, the Web Service needs to be called from a VB6 application
(running
> on Win2K/XP). I re-created the client console application as a .NET dll.
> Using .NET/COM Interop I installed the class library in the GAC and
executed
> regasm.exe with the /tlb and /codebase options (registered the type
libraries
> for the .NET assembly). I tried calling the Web Service and the following
> error was reported back:
>
> System.Web.Services.Protocols.SoapHeaderException: WSE402: The message
does
> not conform to the policy it was mapped to.
>
> It *appears* that the .NET dll was unable to see/use the app.config and
> policyCache.config files and the call to the web service failed (btw, the
> .NET dll uses the same policyCache.config file as per the console (which
> worked) i.e. this is not a policy issue).
>
> How can I get the .NET dll to read the config files when invoked by a VB6
> application? Is there a round-about hack?
>
> Many Thanks,
>
> Laura Papez.
>
> N.B. project developed using VB.NET, ASP.NET, & WSE 2.0 SP2 (policies and
> X.509
> certificates) on XP.
>

"SA" wrote:

> Laura:
>
> Verify the filename of your app.config file.
>
> I believe it should be the name of your first .NET assembly, not the name of
> the VB 6 exe. Or it could be the other way around...
>
> --
>
> ---
>
> Sven.
>
> "Laura Papez" <LauraPapez@discussions.microsoft.com> wrote in message
> news:F4E77DA3-018D-4F5B-A978-8A7255B0A461@microsoft.com...
> > Hi,
> >
> > I have created a secure Web Service via WSE with the use of WS-Policy. The
> > service have been test using a .Net Console application and everything
> works.
> >
> > However, the Web Service needs to be called from a VB6 application
> (running
> > on Win2K/XP). I re-created the client console application as a .NET dll.
> > Using .NET/COM Interop I installed the class library in the GAC and
> executed
> > regasm.exe with the /tlb and /codebase options (registered the type
> libraries
> > for the .NET assembly). I tried calling the Web Service and the following
> > error was reported back:
> >
> > System.Web.Services.Protocols.SoapHeaderException: WSE402: The message
> does
> > not conform to the policy it was mapped to.
> >
> > It *appears* that the .NET dll was unable to see/use the app.config and
> > policyCache.config files and the call to the web service failed (btw, the
> > .NET dll uses the same policyCache.config file as per the console (which
> > worked) i.e. this is not a policy issue).
> >
> > How can I get the .NET dll to read the config files when invoked by a VB6
> > application? Is there a round-about hack?
> >
> > Many Thanks,
> >
> > Laura Papez.
> >
> > N.B. project developed using VB.NET, ASP.NET, & WSE 2.0 SP2 (policies and
> > X.509
> > certificates) on XP.
> >
>
>