SDL Web 8 | Error while adding website using Add-TtmWebsite

Question

I am upgrading to SDL Web 8 from SDL Tridion 2013. I have done the deployments, configuration as per SDL documentation here. I am now trying to add website using Add-TtmWebsite but getting error. cd_core log files show following error

INFO BatchUnmarshaller - Multipart unmarshaller invoked with POST http://XXX.XXX.XXX.X/discovery.svc/$batch DEBUG ODataMessageRouter - Sending error message for exception: com.sdl.odata.api.parser.ODataUriParseException: string matching regex \z' expected buth' found at com.sdl.odata.parser.ODataUriParser.parseUri(ODataUriParser.scala:34) ~[odata_parser-2.0.0-1218.jar:2.0.0-1218] at com.sdl.odata.service.actor.ODataBatchProcessorActor.createODataUri$1(ODataBatchProcessorActor.scala:119) ~[odata_service-2.0.0-1218.jar:2.0.0-1218]

I have tried to find cause of this error but no success. Checked capabilities as suggested here. updated registration also but no luck. Please suggest what could cause this error or how/where I should look further. Many Thanks

Answer 1

There was a similar error noted when we have Discovery service deployed at port 80. As a workaround, deploying discovery with port other than 80 should resolve this error. Can you please check if this is the case here too ?

Answer 2

First, I would suggest to confirm you have a valid and working Discovery service. This can be done with the new discovery-registration.jar file. Copy this to the location of your cd_storage_conf and then in the command prompt run this command:

java -jar discovery-registration.jar read

If this does not work, then you can also try updating the capabilities:

java -jar discovery-registration.jar update

It also could be an issue with OAuth. In the cd_ambient file located where the discovery service is installed, you have several roles, with users and passwords. These are OAuth users (not Tridion CMS users) and you could leave the default accounts /passwords there while you're first testing and installing.

If you modify any config files in the Discovery service folder you'll need to restart the Discovery service. Please post any interesting results you find.

Answer 3

For similar issues encountered around using default ports 80/443 with the Discovery Service in Web 8.5, look for hotfix CD_8.5.0.5811 (or cumulative hotfixes with higher build numbers).