Try our conversational search powered by Generative AI!
AI OnAI Off
WSDL for AliasManagerService different from minSite to Full site
I was able to determin the configuration difference from the minSite to the full site. The following binding was in the minSite:
<binding name="Ektron.WcfServices.bindingConfig" maxBufferPoolSize="2147483647" closeTimeout="00:01:00" openTimeout="00:01:00" maxReceivedMessageSize="2147483647">
<security mode="None" />
<readerQuotas maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" maxDepth="32" />
</binding>
The full site has:
<binding name="Ektron.WcfServices.bindingConfig" maxBufferPoolSize="2147483647" closeTimeout="00:01:00" openTimeout="00:01:00" maxReceivedMessageSize="2147483647" />
Once I changed the minSite binding to match the full site, the WDSLs matched.
Apr 03, 2017 17:28
This thread is locked and should be used for reference only.
We are developing our new MVC site in front of Ektron and built our aliasing manager pointing at our current site.
As we phase out or current site we plan to put up a minSite to host our new 3-tier model.
In dev we put up the min site and noticed we had failures when pointing to the new minSite.
Digging I have found that the WSDL for workarea/services/AliasManagerService.svc is different from the current site to a minSite of the same version.
Specifically there is extra schema under the
Rather than rediscover the service and maintain two Aliasing Manager libraries as we move forward, do you know how to enable the wsp:Policy in the minSite WSDL for the AliasManagerService?