Skip to main content

XM Cloud - Publish error "Invalid Authority connection string. Required parameter 'url' is missing"

Hi Team,

If you are exploring and working on XM Cloud and have set up XM Cloud instance on your local environment, You might run into following issue on publish

 

Because Sitecore XM Cloud instance works on Experience edge and there is no content delivery server which reads from WEB DB, It always publishes on experience edge

Because we are habitual (at-least i am) to publish the API KEY after creation, Because it is mentioned in the steps below url (point-6)

https://doc.sitecore.com/xp/en/developers/hd/211/sitecore-headless-development/create-a-sitecore-api-key.html


and that is why in my other non cloud XM instance (stand alone on-prem), i am habitual to create an API and publish it, and i was doing the same in my XM Cloud Local instance too.

But with local XM Cloud docker instance, It does not work that way, Because local does not work with experience edge, and when you see publishing wizard it only has one publishing target i.e "Experience edge" and that why above error comes


so when you publish anything, It gives below exception 

#Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Sitecore.ExperienceEdge.Connector.ContentHubDelivery.Exceptions.EdgeApiException: [ExperienceEdge Publishing]: An error has occurred while publishing JobStart event 93cf8ce8-8c97-4397-9e13-5fe028ada15b for publishing job '638156301229470000'. Please see inner exception for more details. ---> Sitecore.Exceptions.ConfigurationException: Invalid Authority connection string. Required parameter 'url' is missing.

Solution

1) You actually have to do nothing, because your local rendering hosts in docker for XM Cloud, runs against CM instance, so everything should work OOTB and you do not need to publish anything as there is no content delivery role concept which reads from WEB db.

2) If you still want to publish and want to play around with any use cases etc. you can create a new publishing target called "web" and while publishing select that "web" as the target and not experience edge (not sure if this support will be there in future or not as there is no content delivery role)

everything should work !!!

I saw people asking similar questions and hence thought to pen it down


Labels:

Comments

Post a Comment

Popular posts from this blog

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

Sitecore SXA "Add here" button not available and not able to move components from experience editor

 Hi Folks, Hope you all are doing just fine and getting yourself vaccinated and staying home, Today i would like to share one information or a scenario which we encountered last week. Scenario We are using Sitecore SXA (Version is not important here as it will same for all), and one of our content author logged a bug that, they neither able to see "Add here" button on specific place holder nor they are able to move the component on the page in different location, Move option was disabled, and they wanted to have a freedom of moving component here and there and also "Add here" is a vital functionality to add component to specific place holders.   Troubleshooting With my surprise as i have never seen this behavior before,  1) I first check their access rights but they had all of needed permissions and they were able to do things normally before. 1) I started looking into place holder restriction and different settings of allowed renderings to see if there are no such ...
Post a Comment
Read more