Hybrid Cache Error

[AaronSadlerUK]

Which Umbraco version are you using?

17.0.0

Bug summary

When booting the site after a build I get the below Hybrid Cache error:

InvalidOperationException: All calls to HybridCache with the same key should use the same data type; the same key is being used for 'Umbraco.Cms.Infrastructure.HybridCache.ContentCacheNode' and 'Umbraco.Cms.Infrastructure.HybridCache.ContentCacheNode' data

Specifics

No response

Steps to reproduce

A refresh of the site loads the site fine.

Expected result / actual result

No response

---

This item has been added to our backlog AB#61023

[github-actions]

Hi there @AaronSadlerUK!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[andrejd22]

The same issue occurs in versions 16.3.0 and 16.3.1. Refer to: #20539

[AndyButland]

There seem to have been a few reports of this but I'm struggling to replicate it I'm afraid. If anyone is able to trigger it from a clean install and provide steps, or even share a small sample database that shows the issue, it would be appreciated.

On the face of it seems quite odd, as the message is reporting using different types but describing what seems to be the same thing.

Also would be interested to know if you have an L2 cache configured (e.g. using Redis or a database).

[tony-einfinity]

I just recreated it with a completely fresh install of Umbraco 16.3 using a SQL server database.

I just created a new Umbraco project in Visual Studio, upgraded the Nuget package to 16.3 and run through the setup wizard.

After that I created a document type called "Page" with a template and added two properties one for "Title" and one for "Content", I allowed the document type to be added at root and to itself.

I then created a single page at the root, saving and publishing it, the page loaded as expected.

I stopped the project running and immediately ran it again and was presented this screen.

Waiting around 10-15 seconds and then hitting refresh the page I created loaded as it should have initially.

[AndyButland]

Thanks @tony-einfinity, Unfortunately I'm still not seeing it after following what seem to be quite simple replication steps.

Just to replay (I'm running on Windows):

dotnet new install Umbraco.Templates::16.3.1
dotnet new umbraco --name TestProject1631
cd .\TestProject1631\
dotnet run

Setup document types and content as you describe.

Ctrl+C to stop the site.

dotnet run

Expect to see exception thrown, but I don't.

[inetzo]

I get the same error since Umbraco 16 (and 17). I always create Umbraco projects by selecting the "Umbraco Project (Umbraco HQ)" template in Visual Studio 2022. Every new Umbraco 16+ project created this way gets this error. I have this on multple computers running Visual Studio.

[inetzo]

Here's the full error log:

System.InvalidOperationException: All calls to HybridCache with the same key should use the same data type; the same key is being used for 'Umbraco.Cms.Infrastructure.HybridCache.ContentCacheNode' and 'Umbraco.Cms.Infrastructure.HybridCache.ContentCacheNode' data at Microsoft.Extensions.Caching.Hybrid.Internal.DefaultHybridCache.<GetOrCreateStampedeState>g__ThrowWrongType|64_1[TState,T](String key, Type existingType, Type newType) at Microsoft.Extensions.Caching.Hybrid.Internal.DefaultHybridCache.<GetOrCreateStampedeState>g__TryJoinExistingSession|64_0[TState,T](DefaultHybridCache this, StampedeKey& stampedeKey, StampedeState2& stampedeState)
at Microsoft.Extensions.Caching.Hybrid.Internal.DefaultHybridCache.GetOrCreateStampedeState[TState,T](String key, HybridCacheEntryFlags flags, StampedeState2& stampedeState, Boolean canBeCanceled, IEnumerable1 tags)
at Microsoft.Extensions.Caching.Hybrid.Internal.DefaultHybridCache.GetOrCreateAsync[TState,T](String key, TState state, Func3 underlyingDataCallback, HybridCacheEntryOptions options, IEnumerable1 tags, CancellationToken cancellationToken)
at Umbraco.Cms.Infrastructure.HybridCache.Services.DocumentCacheService.GetNodeAsync(Guid key, Boolean preview) in C:\Repos\TestProject1631\src\Umbraco.PublishedCache.HybridCache\Services\DocumentCacheService.cs:line 111
at Umbraco.Cms.Infrastructure.HybridCache.Services.DocumentCacheService.GetByKeyAsync(Guid key, Nullable1 preview) in C:\Repos\TestProject1631\src\Umbraco.PublishedCache.HybridCache\Services\DocumentCacheService.cs:line 90 at Umbraco.Cms.Infrastructure.HybridCache.DocumentCache.GetByIdAsync(Guid key, Nullable1 preview) in C:\Repos\TestProject1631\src\Umbraco.PublishedCache.HybridCache\DocumentCache.cs:line 35
at Umbraco.Cms.Infrastructure.HybridCache.DocumentCache.GetById(Boolean preview, Guid contentId) in C:\Repos\TestProject1631\src\Umbraco.PublishedCache.HybridCache\DocumentCache.cs:line 39
at Umbraco.Cms.Core.Routing.ContentFinderByUrlNew.FindContent(IPublishedRequestBuilder docreq, String route) in C:\Repos\TestProject1631\src\Umbraco.Core\Routing\ContentFinderByUrlNew.cs:line 131
at Umbraco.Cms.Core.Routing.ContentFinderByUrlNew.TryFindContent(IPublishedRequestBuilder frequest) in C:\Repos\TestProject1631\src\Umbraco.Core\Routing\ContentFinderByUrlNew.cs:line 99
at Umbraco.Cms.Core.Routing.PublishedRouter.FindPublishedContent(IPublishedRequestBuilder request) in C:\Repos\TestProject1631\src\Umbraco.Core\Routing\PublishedRouter.cs:line 486
at Umbraco.Cms.Core.Routing.PublishedRouter.RouteRequestInternalAsync(IPublishedRequestBuilder builder, Boolean skipContentFinders) in C:\Repos\TestProject1631\src\Umbraco.Core\Routing\PublishedRouter.cs:line 246
at Umbraco.Cms.Core.Routing.PublishedRouter.RouteRequestAsync(IPublishedRequestBuilder builder, RouteRequestOptions options) in C:\Repos\TestProject1631\src\Umbraco.Core\Routing\PublishedRouter.cs:line 117
at Umbraco.Cms.Web.Website.Routing.UmbracoRouteValueTransformer.RouteRequestAsync(IUmbracoContext umbracoContext) in C:\Repos\TestProject1631\src\Umbraco.Web.Website\Routing\UmbracoRouteValueTransformer.cs:line 197
at Umbraco.Cms.Web.Website.Routing.UmbracoRouteValueTransformer.TransformAsync(HttpContext httpContext, RouteValueDictionary values) in C:\Repos\TestProject1631\src\Umbraco.Web.Website\Routing\UmbracoRouteValueTransformer.cs:line 113
at Microsoft.AspNetCore.Mvc.Routing.DynamicControllerEndpointMatcherPolicy.ApplyAsync(HttpContext httpContext, CandidateSet candidates)
at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.SelectEndpointWithPoliciesAsync(HttpContext httpContext, IEndpointSelectorPolicy[] policies, CandidateSet candidateSet)
at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.g__AwaitMatch|10_1(EndpointRoutingMiddleware middleware, HttpContext httpContext, Task matchTask)
at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 112
at Umbraco.Cms.Web.Common.Middleware.UmbracoRequestMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\Repos\TestProject1631\src\Umbraco.Web.Common\Middleware\UmbracoRequestMiddleware.cs:line 122
at Umbraco.Cms.Web.Common.Middleware.UmbracoRequestMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\Repos\TestProject1631\src\Umbraco.Web.Common\Middleware\UmbracoRequestMiddleware.cs:line 128
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Umbraco.Cms.Web.Common.Middleware.PreviewAuthenticationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\Repos\TestProject1631\src\Umbraco.Web.Common\Middleware\PreviewAuthenticationMiddleware.cs:line 80
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Umbraco.Cms.Web.Common.Middleware.UmbracoRequestLoggingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\Repos\TestProject1631\src\Umbraco.Web.Common\Middleware\UmbracoRequestLoggingMiddleware.cs:line 42
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at SixLabors.ImageSharp.Web.Middleware.ImageSharpMiddleware.Invoke(HttpContext httpContext, Boolean retry)
at Umbraco.Cms.Api.Management.Middleware.BackOfficeAuthorizationInitializationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) in C:\Repos\TestProject1631\src\Umbraco.Cms.Api.Management\Middleware\BackOfficeAuthorizationInitializationMiddleware.cs:line 51
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.InterfaceMiddlewareBinder.<>c__DisplayClass2_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)`

[AndyButland]

Thanks for the further information and reports, I have been able to replicate this now, and made some progress to a resolution. Am still testing and verifying.

[AndyButland]

Fixed via #20554 for 17.0 and also 16.3.2 (which I'll look to put out tomorrow).