November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
I am facing the same issues and have a ticket open with Optimizely
My package versions are as follows
<PackageReference Include="Advanced.CMS.AdvancedReviews" Version="1.3.6" />
<PackageReference Include="EPiServer.CloudPlatform.Cms" Version="1.3.2" />
<PackageReference Include="EPiServer.CMS" Version="12.22.3" />
<PackageReference Include="EPiServer.CMS.AspNetCore" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.HtmlHelpers" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.Mvc" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.Routing" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.TagHelpers" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.Templating" Version="12.17.0" />
<PackageReference Include="EPiServer.CMS.UI" Version="12.22.3" />
<PackageReference Include="EPiServer.CMS.UI.Core" Version="12.22.3" />
<PackageReference Include="EPiServer.Find" Version="15.1.2" />
<PackageReference Include="EPiServer.Find.Blocks" Version="15.1.2" />
<PackageReference Include="EPiServer.Find.Cms" Version="15.1.2" />
<PackageReference Include="EPiServer.Find.Personalization" Version="15.1.2" />
<PackageReference Include="EPiserver.Forms" Version="5.6.0" />
<PackageReference Include="EPiServer.Forms.Samples" Version="4.2.0" />
<PackageReference Include="EPiServer.Framework" Version="12.17.0" />
<PackageReference Include="EPiServer.Hosting" Version="12.17.0" />
<PackageReference Include="EPiServer.Labs.LanguageManager" Version="5.1.3" />
<PackageReference Include="EPiServer.Marketing.Automation.Forms" Version="3.1.2" />
<PackageReference Include="EPiServer.MarketingAutomationIntegration.Salesforce" Version="5.1.2" />
<PackageReference Include="EPiServer.OptimizelyIdentity" Version="1.0.1" />
<PackageReference Include="Geta.NotFoundHandler.Optimizely" Version="5.0.7" />
<PackageReference Include="Geta.Optimizely.Categories" Version="1.0.0" />
<PackageReference Include="Geta.Optimizely.Sitemaps" Version="3.1.1" />
<PackageReference Include="Microsoft.Extensions.Configuration" Version="6.0.1" />
<PackageReference Include="Microsoft.Extensions.Configuration.Abstractions" Version="6.0.0" />
<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="7.0.1" />
<PackageReference Include="Stott.Optimizely.RobotsHandler" Version="2.6.1" />
System.Net.WebSockets.WebSocketException:
at System.Net.WebSockets.ManagedWebSocket.ThrowIfEOFUnexpected (System.Net.WebSockets, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Net.WebSockets.ManagedWebSocket+<EnsureBufferContainsAsync>d__74.MoveNext (System.Net.WebSockets, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCore`1.ThrowForFailedGetResult (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1+StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Net.WebSockets.ManagedWebSocket+<ReceiveAsyncPrivate>d__63`1.MoveNext (System.Net.WebSockets, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Threading.Tasks.Sources.ManualResetValueTaskSourceCore`1.GetResult (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1+StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Threading.Tasks.ValueTask`1+ValueTaskSourceAsTask+<>c.<.cctor>b__4_0 (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
at EPiServer.Shell.UI.Messaging.Internal.DefaultWebSocketHandler+<ProcessWebSocketRequestAsync>d__7.MoveNext (EPiServer.Shell.UI, Version=12.22.3.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7)
Hey, thanks for reaching out.
I saw that the case @Minesh created is being handled by our support. But could I ask, besides seeing these errors in the log, does the application run as the they should? It seems from the first post that the application failed to start, but later seems to have started. Did it crash again? If so, continuously?
We use WebSocket to handle the communication when sending notifications between users. We did a change regarding the notifications in 12.20.0, but since you report this after the upgrade I dont think this should be caused by that. If your applications run (but logging errors), do you know if the notifications work for your users?
Hey @Robert
Another of our clients is on 12.20.0 and we are seeing the error for them also, with both of mine the application generally runs as normal. But with one of our clients I am running a migration and the WebSocket errors seens to be causing an issue during the migration and causing it to fail every so often.
I have tested the notifications roughly 1 week back and they seemed to work fine.
Minesh
This issue was resolved by the patching Episerver did to the packages in the latest version. So if you upgrade to the latest version, it doesn't happen anymore
Seeing this:
What did you try?
Where does this error occur? When you start the CMS or the site in general?
Is this from console output or from the log?
Also, clean up your post, it is bearly readable.