ProjectMessageNotifier: Cannot access a disposed object

London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / Problems and bugs /

ProjectMessageNotifier: Cannot access a disposed object - Object name: 'IServiceProvider'

Dan Valea

Vote:

Hi,

We just upgraded our project to the latest CMS packages and we keep getting the error below each time we publish content (CMS or Catalog) via a scheduled job. Publishing seems to be working fine even with the error being thrown, but it seems to take more time now. It happens both locally and in DXP.

fail: EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier[0]
      System.ObjectDisposedException: Cannot access a disposed object.
      Object name: 'IServiceProvider'.
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ThrowHelper.ThrowObjectDisposedException()
         at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
         at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
         at EPiServer.Notification.Internal.DefaultSubscriptionRepository.ClearSubscriptionAsync(Uri subscriptionKey)
         at EPiServer.Notification.Internal.DefaultSubscriptionService.ClearSubscriptionAsync(Uri subscriptionKey)
         at EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier.UnsubscribeFromAllActivitiesFromPublishedVersion(ContentReference contentLink)
         at EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier.ActivityCreated(Object sender, ActivityCreatedEventArgs e)

Packages used:

#317580

Feb 23, 2024 6:48

KlawitterB

Vote:

We are also currently upgrading to this version and have noticed this in our logs.

#317886

Feb 28, 2024 7:50

huseyinerdinc

Vote:

We, too, receive this error every time a content is updated.

#318275

Feb 29, 2024 11:56

Robert Svallin

Vote:

Thank you for your feedback on this error, I have been able to reproduce it on 12.20.3 and have asked that the devs take a look at it. Currently the reported bug is not published, but once they have had a look at it you should find it at https://world.optimizely.com/support/bug-list/bug/CMS-32816.

#318447

Mar 04, 2024 18:04

Andy

Vote:

That bug is now closed as duplicate but what is the duplicate bug-ticket number?

#318956

Edited, Mar 14, 2024 13:06

Quan Mai

Vote:

the bug CMS-32880 which is now fixed and will be released with CMS.Core 12.21.0

#318960

Mar 14, 2024 14:10

This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.