Sitecore 10.1.0 Unicorn 4.1.5.0 page load issue: The physical root path of this SFS tree, is longer than the configured max base path length 110. If the tree contains any loopback paths, unexpected behavior may occur. You should increase the Rainbow.SFS.SerializationFolderPathMaxLength setting in Rainbow.config to greater than 141 and perform a reserialization from a master content database.

Error: 

Server Error in '/' Application.

The physical root path of this SFS tree, is longer than the configured max base path length 110. If the tree contains any loopback paths, unexpected behavior may occur. You should increase the Rainbow.SFS.SerializationFolderPathMaxLength setting in Rainbow.config to greater than 141 and perform a reserialization from a master content database.

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.InvalidOperationException: The physical root path of this SFS tree, c:\inetpub\wwwroot\sc1010latestsc.dev.local\App_Data\Unicorn\MySitecoreSln.Feature.CustomCoreMenu\MySitecoreSln.Feature.CustomMenu.Core.Items, is longer than the configured max base path length 110. If the tree contains any loopback paths, unexpected behavior may occur. You should increase the Rainbow.SFS.SerializationFolderPathMaxLength setting in Rainbow.config to greater than 141 and perform a reserialization from a master content database.

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:

[InvalidOperationException: The physical root path of this SFS tree, c:\inetpub\wwwroot\sc1010latestsc.dev.local\App_Data\Unicorn\MySitecoreSln.Feature.CustomCoreMenu\MySitecoreSln.Feature.CustomMenu.Core.Items, is longer than the configured max base path length 110. If the tree contains any loopback paths, unexpected behavior may occur. You should increase the Rainbow.SFS.SerializationFolderPathMaxLength setting in Rainbow.config to greater than 141 and perform a reserialization from a master content database.]
   Rainbow.Storage.SerializationFileSystemTree.get_MaxRelativePathLength() +282
   Rainbow.Storage.SerializationFileSystemTree.get_MaxItemNameLengthBeforeTruncation() +71
   Rainbow.Storage.SerializationFileSystemTree.PrepareItemNameForFileSystem(String name) +143
   System.Linq.WhereSelectArrayIterator`2.MoveNext() +145
   System.Linq.Buffer`1..ctor(IEnumerable`1 source) +284
   System.Linq.Enumerable.ToArray(IEnumerable`1 source) +90
   Rainbow.Storage.SerializationFileSystemTree.GetPhysicalFilePathsForVirtualPath(String virtualPath) +270
   Rainbow.Storage.SerializationFileSystemTree.GetItemsByPath(String globalPath) +122
   Unicorn.Predicates.PredicateRootPathResolver.GetRootSerializedItems() +157
   Unicorn.ControlPanel.ControlPanelUtility.HasAnySerializedItems(IConfiguration configuration) +91
   System.Linq.Enumerable.All(IEnumerable`1 source, Func`2 predicate) +177
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.<CreateBodyControls>d__2.MoveNext() +168
   System.Linq.Buffer`1..ctor(IEnumerable`1 source) +284
   System.Linq.Enumerable.ToArray(IEnumerable`1 source) +90
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.RenderControlPanel.CreateResponse(UnicornControlPanelRequestPipelineArgs args) +70
   Unicorn.ControlPanel.Pipelines.UnicornControlPanelRequest.UnicornControlPanelRequestPipelineProcessor.Process(UnicornControlPanelRequestPipelineArgs args) +182
   (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, Boolean failIfNotExists) +36
   Unicorn.ControlPanel.UnicornControlPanelPipelineProcessor.ProcessRequest(HttpContext context) +539
   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
   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



Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4330.0


Solution:

This Foundation.Serialization.Settings.confg file that increases the path length was missing. So, I added the same to web root config path (<web app root path>\App_Config\Include\Foundation) and reloaded the unicorn page.

But then, there was a different problem waiting for me:  When I checked the showconfig.aspx, the Foundation.Serialization.Settings.confg file wasn't getting patched. After a lot of iis reset , restart etc. + coffee, 


I tried disabling the Rainbow.config in the App_Config\Include folder and the Foundation.Serialization.Settings.confg was getting picked up. 

Then, after some trial and error, I realized that a better approach will be to rename this Foundation.Serialization.Settings.confg file as Rainbow.Settings.config and if it is present in the same location as the Rainbow.config, the patch gets applied -


Note: Ensure to disable or remove the  Foundation.Serialization.Settings.confg file  from the <web app root path>\App_Config\Include\Foundation folder!

Comments

Popular Posts