Skip to main content

XM Cloud - Reference environment configuration 'xmcloudlocal' doesn't exist

Hi Team,

Recently, I have been setting up XM Cloud instance in my local and sending some changes back to XM Cloud, and for that i needed to do serialization of the content from cloud to local and than local to push into XM Cloud.

Because i was using the documentation given on 

Walkthrough: Setting up your full-stack XM Cloud local development environment (sitecore.com) 

Because if you are like me, you just follow the steps first to see how things work, in one of those steps, i encountered below exception 


 Error

Reference environment configuration 'xmcloudlocal' doesn't exist"

With my surprise, because i am following the documentation steps, so it should just work, i double checked that i have not missed any steps, The site documentation was mentioning below 

I double checked my user.json file to see if i have this ref value as "xmcloudlocal" available or not, and with my surprise, it was not there, but i had entry with ref "xmcloud", so i change my above command to below

dotnet sitecore connect --ref xmcloud --cm https://xmcloudcm.localhost --allow-write true -n local

and command just worked, to double check this behavior i created a Sitecore ticket asking them if the documentation needs to be updated? Because clearly everyone will get same error if they follow it, and they acknowledged the behavior and reproduced on their end and promised to send a documentation change request at their end

I hope this will be corrected soon.

 



Labels:

Comments

Post a Comment

Popular posts from this blog

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

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...
9 comments
Read more

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...
2 comments
Read more