Content Server 16.2.4 Not Providing CWS Content Web Services Connection Externally

Marlyn Norris

We are currently experiencing an issue with Content Server 16.2.4 not providing CWS Content Web Services connection externally since upgrade from version 16.2.3. When attempting to use Postman to get an authorization ticket it comes back with no payload return values. This was previously working in Content Server version 16.2.3 consecutively. It is critical we have this CWS available asap as it is now effecting our ability to connective interfaces to Content Server. Any ideas on what is causing this?

Regards,

Marlyn Norris

Nizar Ghazal

Hi Marlyn,

I wouldn't nominally use Postman to test out any part of CWS, as I would use that for the REST API, instead.

For CWS, I would use SOAP UI or I'd write a simple console application in C# or Java.

However, one of the first things to check, is the WSDL up and generating the document you expect?

http://your_contentserver.com/cws/Authentication.svc?wsdl

In a browser, does it return an XML document? In the schemaLocation field (should be visible without scrolling down), does the URL match the FQDN/IP that you intend? I know some applications have a fit if it's bound differently.

In your Content Server instance, make sure that nothing changed about the ports or instance name, as in OTHOME/webservices/dotnet/cws/web.config there should be a host and port value, to let your web server talk to CS.

Make sure your web server is up and talking, too.

If none of the above helps you solve it, open a support ticket, they'll take a look at what's going on, for you.

If the schema comes back and everything looks good, you may needs CWS logs, or a packet capture.

Thanks,

Nizar