SOLVED: Error while running Sitecore Unicorn sync for Habitat Home: System.ArgumentException: Configuration(s) requested were not defined.


When running Habitat Home build using build.ps1, the Sync-Unicorn task fails with the following message:

Error: ERROR: Configuration(s) requested were not defined. (System.ArgumentException)<div class="stacktrace">at Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.SyncVerb.ResolveConfigurations()
<br />   at Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.SyncVerb.Process(IProgressStatus progress, ILogger additionalLogger)
<br />   at Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.SyncVerb.<>c__DisplayClass3_0.<CreateResponse>b__0(IProgressStatus progress)
<br />   at Unicorn.ControlPanel.Responses.WebConsoleResponse.ProcessInternal(IProgressStatus progress)
<br />   at Kamsar.WebConsole.TextWebConsole.Render(Action`1 processAction)
<br />   at Unicorn.ControlPanel.Responses.WebConsoleResponse.Execute(HttpResponseBase response)</div>
****ERROR OCCURRED****
An error occurred when executing task 'Sync-Unicorn'.
Error: One or more errors occurred.
        Unicorn Sync to https://sitecore93sc.dev.local/unicorn.aspx?verb=Sync&configuration=true&skipTransparentConfigs=0 returned an error. See the preceding log for details.
The stack trace is as follows:

Server Error in '/' Application.

Configuration(s) requested were not defined.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Configuration(s) requested were not defined.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ArgumentException: Configuration(s) requested were not defined.]
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.SyncVerb.ResolveConfigurations() +507
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.SyncVerb.Process(IProgressStatus progress, ILogger additionalLogger) +28
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.<>c__DisplayClass3_0.<CreateResponse>b__0(IProgressStatus progress) +175
   Unicorn.ControlPanel.Responses.WebConsoleResponse.ProcessInternal(IProgressStatus progress) +511
   Kamsar.WebConsole.Html5WebConsole.Render(Action`1 processAction) +286
   Unicorn.ControlPanel.UnicornControlPanelPipelineProcessor.ProcessRequest(HttpContext context) +716
   Unicorn.ControlPanel.UnicornControlPanelPipelineProcessor.Process(HttpRequestArgs args) +325
   (Object , Object ) +14
   Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args) +490
   Sitecore.Pipelines.DefaultCorePipelineManager.Run(String pipelineName, PipelineArgs args, String pipelineDomain, Boolean failIfNotExists) +236
   Sitecore.Pipelines.DefaultCorePipelineManager.Run(String pipelineName, PipelineArgs args, String pipelineDomain) +22
   Sitecore.Web.RequestEventsHandler.OnPostAuthenticateRequest(HttpContextBase context) +218
   Sitecore.Nexus.Web.HttpModule.‪‏‪‌‪‍‌‮‬​‬‍‎​‏‍‪‭‎‌‍‪‪‮‮(Object , EventArgs ) +207
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +223
   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +220
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +94

The issue seems to be related to the following line of code in scripts\Unicorn\Unicorn.psm1

$url = "{0}?verb={1}&configuration={2}&skipTransparentConfigs={3}" -f $ControlPanelUrl, $Verb, $parsedConfigurations, $skipValue 

Solution: Update the query parameter "configuration" to "configurations".

The error seems to only show when using -DebugSecurity switch is applied to Sync-Unicorn command in scripts\Unicorn\Sync.ps1




Comments

Post a Comment

Popular posts from this blog

First look at Sitecore XM Cloud: Part 4 - Creating a new Site

Image
 Once you have successfully create an environment, you can go ahead and create your first site. In order to create a new Site, you need to launch the Sitecore Launchpad by clicking on the "XM Cloud Launchpad": Click on "Sites" menu to create a new Site: Click on "Add your first website" button to start the wizard. I chose the "Basic Site" template: Enter a Site name and pick a language and click on "Create website" button. You will see the following screen while your Site is being created: Once the Site is created, you can edit it in Pages or Explorer using the context menu: Explorer view of the Site: 1. "Details" view of page. 2. "Content" view of page: Unfortunately, trying to load the new Site in pages gives "Unable to connect to remote server"
Read more

RESOLVED: Solr Exceptions - Document contains at least one immense term in field

If you implemented Solr with Sitecore using Solr 5.x, you may run into the following error when indexing extremely large content in string fields: org.apache.solr.common.SolrException: Exception writing document id <xxxuniqueid> to the index; possible analysis error. Caused by: java.lang.IllegalArgumentException: Document contains at least one immense term in field="<xxxfieldname>" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 9, 9, 10, 32, 32, 32, 32, 32, 32, 82, 84, 82, 83, 32, 70, 97, 99, 105, 108, 105, 116, 121, 32, 10, 32, 32, 32, 32, 84]...', original message: bytes can be at most 32766 in length; got <intgreaterthan32766> Caused by: org.apache.lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got <intgreaterthan32766> This is due to the fa...
Read more

First look at Sitecore XM Cloud: Part 1 - Getting started with Sitecore Cloud Portal and XM Cloud Deploy

Image
The biggest news of the year in the Sitecore community has been the arrival of Sitecore XM Cloud. In this blog series, I will be showing partner's access to XM Cloud. To get started, one needs to be invited to Sitecore Portal. You can access it at https://portal.sitecorecloud.io/.  Once you create an account and sign-in, you arrive at the following screen which has two main actions: Invite members  Managed projects (Sitecore XM Deploy) If you look closely you will see Sitecore Cloud Portal and XM Cloud Deploy. Invite team members opens up the following screen: "Manage My Projects" option launches the following window In the Part 2 , I will take us through deploying our first XM Cloud instance.
Read more