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

Why SitecoreAI - Getting into the shoes of the customer how to select right CMS

Hi Team, Lately, I have been talking to lot of our customers / potential customers and having pre-sales demos where one question always comes is "Why Sitecore" ?  Now this question can be for any product which is out for sell. And as a technician I always get into product technical features, but at the same time as a pre-sales guy, it also makes me think, surely all competitive products have same features, so definitely answer to this is not in the technicalities.  If you step back and think, we are also a customer in our daily life and buy lot of things, what is that process we go through? When we buy, how can your customer decide if this is a right fit for you or not, why we select A over B? Is it price? is it service? Is it a brand? Is it about features? Is it about brand loyalty?  When it is a technical product, I am sure it cannot start with the technicalities of the product or selecting product itself, 100% not, I feel decision is always business strategy first and ...
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 creative exchange export appends hyphen(-) number to the static assets

Hello There, So, today i will be sharing some information which i think will be useful for many as this might come as a blocker just like me, where i was planning for a next sprint for which i was checking prerequisites and suddenly found out that, Export functionality of SXA is not working properly, it was exporting things but i open the page which was exported (index.html), it was loading without any CSS or JS functioning. Problem I have been using SXA but i never had this issue before, where page or site gets exported but when we open the page, it comes up without CSS or JS functioning properly on the page. So, first thing like any developer i opened up the source of the HTML and tried to see why CSS is not working properly and checked its path and found out following  I was surprised at first point as i never saw this behavior, but one thing was confirmed that, SXA is adding these "-number" at the end of CSS when we export so, i tried to de-assemble the DLL just to see wh...
Post a Comment
Read more