Hi!
We have distributed a client that consumes WSE-enhanced web services.
The client gets the URLs to the web services using a configuration file.
The WSE is not installed on the clients, simply Microsoft.Web.Services2.dll
is put in the same client folder as the main executable. That has always
worked.
Now we needed to raise the value for timeToleranceInSeconds to 900 from its
default value 300. There for the "configSections" and
"microsoft.web.services2" sections was added to the config file. From now all
the clients gets the error message:
System.Configuration.ConfigurationException: WSE032: There was an error
loading the microsoft.web.services2 configuration section.
<?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>
<appSettings file="C:\CD\Cesow\CesowAdministrationClient.User.config">
<add key="***SOMETHING***"
value="http://ws.***SOMETHING***/***SOMETHING***.asmx"/>
</appSettings>
<microsoft.web.services2>
<security>
<timeToleranceInSeconds>900</timeToleranceInSeconds>
</security>
</microsoft.web.services2>
</configuration>
Note that the error is not shown on any development client. I suspect that
the error is not shown because a WSE development installation is done on
these machines.
Must WSE runtime version be manually INSTALLED on clients to make it
possible to read WSE sections in configuration file? We do not want that to
be needed of administration reasons.
linhardt@aol.com - 30 Nov 2005 18:17 GMT
Hi Benjamin,
Did you resolve this problem?
I'm trying to avoid having the user install WSE 2.0 for a web form/web
service application too.
That's news to me that you could just install
Microsoft.Web.Services2.dll in the client application folder. I would
be very interested to hear if you got this to work with your modified
ToleranceInSeconds. I doubt this is Microsoft's intended solution
since the redistribution license for WSE 2.0 requires developers to
user their msi installer.
I've been working on two versions of web form application: (1) one
using a msi installer to install on the client and (2) one allowing the
user to run the client from IE using no-touch deployment.
(1) As far as I can tell, for the client msi installer, you are
supposed to be able to do a nested installation of the WSE msi using
msiexec. (I haven't figured out how to do this in Visual Studio, but
it has something to do with Custom Actions). [Anyone know a good
article/example?]
(2) Regarding no-touch deployment, is it sufficient to put
Microsoft.Web.Services2.dll in the same folder as the application.exe
on the server or does the user have to have WSE installed on their
machine?
If the user doesn't have WSE 2.0, how do you trap the exception? I get
a System.TypeInitializationException in my application which IS NOT
trapped in the Try/Catch block of my applications main routine.
BTW, regarding your comment that you are not getting your error on
development machines, try uninstalling WSE (fControl Panel; add/remove
programs) to test your theory.
-Paul
> Hi!
>
[quoted text clipped - 39 lines]
> possible to read WSE sections in configuration file? We do not want that to
> be needed of administration reasons.