forge

Web Services Extensions (WSE) 2.0 and SharePoint

One of my clients recently needed to have WSE installed on the same server as SharePoint.  Their policy caused some issues with SharePoint web services.  After a support call we came up with this solution to running WSE and SharePoint in the same virtual server…

1. Create a blank policyCache.config file – or remove the nodes underneath /policyDocument/mappings and /policyDocument/policies from your existing policyCache.config file.

2. Add to the /policyDocument/mappings node the following nodes:

 

<defaultEndpoint>

Help Your SharePoint User

<defaultOperation>

<request policy=”” />

<response policy=”” />

<fault policy=”” />

</defaultOperation>

</defaultEndpoint>

3. Save the file into the C:\Program files\Common Files\Microsoft Shared\Web Server Extensions\60\ISAPI directory as policyCache.config

4. Perform an IISRESET.

That should make WSE and SharePoint get along much better.