Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

ProjectMessageNotifier: Input string was not in a correct format.

Vote:
 

Hello

After upgrade to 11.13, we are seing these in the error log. They show up sporadically and then in long series of repetition of same error.

2019-11-29 12:25:54,110 [634] ERROR EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier: Input string was not in a correct format.
2019-11-29 12:25:54,111 [279] ERROR EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier: Input string was not in a correct format.
2019-11-29 12:25:54,179 [581] ERROR EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier: Input string was not in a correct format.
2019-11-29 12:25:54,180 [223] ERROR EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier: Input string was not in a correct format.
2019-11-29 12:25:54,239 [596] ERROR EPiServer.Cms.Shell.UI.Rest.Projects.Notifications.Internal.ProjectMessageNotifier: Input string was not in a correct format.
...
...

I didn't find anything wrong. And noone uses projects functionality, so basically there are no workflows in use. Also I tried to run Episerver notifications scheduled job, but it reports 0 messages to process and no errors are logged at the time.

Is this related to some missing configuration, or any ideas?
Thanks

#210957
Dec 13, 2019 11:17
Vote:
 

Hi

I'm experiencing the same issue on production environment with a site that runs on Episerver.CMS.Core 11.11.2.

Please advice what can be done to avoid this.

Regards

Ritu

#214645
Jan 09, 2020 18:35
Vote:
 

Am seeing the same in cms.core.11.14.0

#217179
Feb 19, 2020 3:23
Vote:
 

Looks like it's a bug, according to Quan Mai.

#217197
Feb 19, 2020 9:33
Vote:
 

Read, thanks!

It doesn't contain the bug Id though, so it will be a bit of a sport to track when is it going to be released, but still moving forward. All the best!

#217227
Feb 19, 2020 17:12
Vote:
 

The bug is CMS-15434, which is accepted by the CMS UI team, but is not made public.

Note that the bug will make it easier to diagnose the problem, not fix it 

#217228
Feb 19, 2020 19:56
Vote:
 

Any update on this bug? It's bloating our log something fierce. Yesterdeay alone we had 92,966 of these entries.

#253361
Apr 16, 2021 17:37
Vote:
 

If you upgrade to at least CMS UI 11.23.7, the log now contains the whole stacktrace which would make easier to understand what is wrong

#253394
Apr 17, 2021 8:42
Vote:
 

Are there any common causes we can look at before upgrading to 11.23.7? I'm concerned about log size and performance when we include a stack trace on an issue happening nearly 100,000 times a day.

Unfortunately, production is the only tier we see this error in.

#253562
Apr 19, 2021 14:30
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.