Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / June 2005

Tip: Looking for answers? Try searching our database.

<cryptography><encryptionFormatters> in sp2/sp3

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ep - 05 May 2005 19:18 GMT
I have a WSE server app that uses the <cryptography> element in the
configuration (seen below).  This worked perfectly in WSE sp1, but when I
upgraded to SP2 and then to SP3, I get the following soap fault from any WSE
web service call.  I know there is not a problem with the config file, it
worked in sp1 and it is correct according to the sp3 documentation.  What is
happening here?

System.Web.Services.Protocols.SoapHeaderException: Server unavailable,
please try later ---> System.Configuration.ConfigurationException: WSE032:
There was an error loading the microsoft.web.services2 configuration
section. ---> System.Configuration.ConfigurationException: WSE028: An
unrecognized configuration element was found: cryptography.

<microsoft.web.services2>
<security>
<cryptography>
<encryptionFormatters>
<add uri="urn:myEncryptionFormatter:algUri:1"
type="MyLibrary.MyEncryptionFormatter, MyLibrary, Version=1.0.2.0,
Culture=neutral, PublicKeyToken=xxxx"
/>
</encryptionFormatters>
</cryptography>
</security>
<diagnostics />
</microsoft.web.services2>
Keenan Newton - 05 May 2005 20:42 GMT
Thats odd.  With the service packs did you change the version number of
the section handler referencing the microsoft.web.services2
configuration section.  Its my only thought as possible problem.
ep - 05 May 2005 21:57 GMT
no, and everything else works except for that <cryptography> element.
custom token managers work fine.

> Thats odd.  With the service packs did you change the version number of
> the section handler referencing the microsoft.web.services2
> configuration section.  Its my only thought as possible problem.
Keenan Newton - 06 May 2005 17:57 GMT
If the version number is different between SP1, SP2, and SP3.  Then I
do beleive it oulw be a good idea to make sure youre configuration file
is referencing the correct version number.  Otherwise I am puzzled
ep - 06 May 2005 19:01 GMT
tried it just for fun
didn't change anything, which it shouldn't since there's a policy file.

> If the version number is different between SP1, SP2, and SP3.  Then I
> do beleive it oulw be a good idea to make sure youre configuration file
> is referencing the correct version number.  Otherwise I am puzzled
Sidd [MSFT] - 23 Jun 2005 06:35 GMT
Hi,

    The <cryptography> element issue was found to be a problem in SP2 and
SP3 and this issue has been addressed internally.

    Let me know if you have any more questions.

Thanks,

Sidd [MSFT]
> tried it just for fun
> didn't change anything, which it shouldn't since there's a policy file.
>
>> If the version number is different between SP1, SP2, and SP3.  Then I
>> do beleive it oulw be a good idea to make sure youre configuration file
>> is referencing the correct version number.  Otherwise I am puzzled

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.