Problem with WSE and Win98...(MVP Replies prefered)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello to everyone,

I have the following problem:

I MUST host my client application on Windows 98, with .NET Framework 1.1

I am using Visual Studio .NET 2003.

I'm using WSE to send text files that must be digitally signed, and use SSL.

WSE 2.0 sp3 does not install under win98, so I did some tricks,

I copied the dll Microsoft.Web.Services2.dll to the same path as the
executables, and it worked fine...

But there's a problem, if the computer on the client has more than 5
minutes, an exception will occur:
"An error was discovered processing the <Security> header"

To solve this problem, we must alter Web.Config on the client and on the
server.
On the server we must put:

<security>
<defaultTtlInSeconds>86400</defaultTtlInSeconds>
<timeToleranceInSeconds>86400</timeToleranceInSeconds>
</security>

Note: 86400 is 24 hours * 60 min * 60 seconds

And on the client, at the <WindowsApplication1>.exe.config the following
code:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<microsoft.web.services2>
<security>
<defaultTtlInSeconds>86400</defaultTtlInSeconds>
<timeToleranceInSeconds>86400</timeToleranceInSeconds>
</security>
<diagnostics />
</microsoft.web.services2>
</configuration>

Fine until then, but now an other exception occurs:

"there was an error loading the microsoft.web.services2. configuration
section"
To solve this problem, we must get from the GAC (using command prompt,
navigating to C:\Windows\Assembly) the file

Policy.2.0.Microsoft.Web.Services2.dll with its correpondent xml policy
file.

But for installing on the GAC this dll, we need gacutil.exe file, that ships
with Visual Studio .NET, and also the dll msvcr71.dll

Fine!

Then my problem:

When using a X509 certificate to digitally sign my file, I get a WSE
exception saying that the program can only run under windows 2000/XP/2003

So what can I do? Hope you can help me. Do I have to purchase a separate
component? Is there another way to send an attachment? I also tried to used
the Pocket Soap Toolkit 3.0 without success!

Thanks,

Raphaël Désalbres














.

Relevant Pages

  • Re: Mustunderstand exception raised but method still called
    ... SoapHttpClientProtocol on your client proxy ... BUT if you sending a usernametoken via WSE, then you should be using the ... Point 2 must be correct if you are generating the exception seen below ... Then load your custom UsernameTokenManager type into the ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: How to handle username token exception at client side(web service user)
    ... Does not enough A try/catch block at proxy call/soap client call for your ... > I am use WSE 2.0. ... ope envelope) at ... SoapContext exception. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: How to call Web Service Securely
    ... Maybe I am complicating WSE too much - can you point me to a simple ... you could provide a logon screen in the client app and create a NetworkCredential ... tokens - but that is tied to .NET 2.0 ... make a web method via dialup to my IIS Web Service. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • RE: Cant open Websites With VS2008
    ... Faulting module name: SHELL32.dll, version: 6.1.7100.0, time stamp: 0x49eea6b3 ... If it is Vista or 2008, please open Visual Studio as administrator first. ... please we need the following log and exception ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.general)
  • Re: Authentication in WSE
    ... can't control the Exception publishing mechanism, it's controlled by WSE ... >> the usual best practices for secure authentication, ... >> Though I am relatively new to WSE, my understanding is that the custom ...
    (microsoft.public.dotnet.framework.webservices.enhancements)