jhunkele
-
4/21/2006 3:44:14 PM
Re: Content Staging Sync problems
The problem was that the web.config files had caode that was added without my knowing it and this code is needed for the Content Staging to occur.
Above the appSettings I needed:
<configSections> <section name="microsoft.web.services2" type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration, Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </configSections>
Then in the system.web section I needed:
<webServices> <soapExtensionTypes> <add type="Microsoft.Web.Services2.WebServicesExtension, Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="1" group="0" /> </soapExtensionTypes> </webServices>
Finally, at the bottom of the configuration section I needed:
<microsoft.web.services2> <security> <securityTokenManager type="Kentico.CMS.SyncWebService.WebServiceAuthorization, Kentico.CMS.SyncWebService" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" qname="wsse:UsernameToken" /> <x509 allowTestRoot="true" allowRevocationUrlRetrieval="false" verifyTrust="true" /> </security> </microsoft.web.services2>
I've also run into a lot of problems setting up Content Staging and the Kentico documentation is somewhat limited.
Best way to do it is set up your DEV environment and then duplicate everything for your PROD environment. Make sure ASP.NET has access to both directories and the C:\Windows\temp directory on each machine involved. Also make sure there is a ASP.NET State Service running. There are a lot of gotcha's setting this up, so it's not as easy as the instructions say. Hope this helps someone else. Good luck.
|