ServiceControl 5.0.4 and 4.33.2 – Patch releases available

Announcements
1

Hi everyone,

We’ve just released ServiceControl 5.0.4 and 4.33.2.

Fixed bugs

  • #3933 False Custom check error notification about disk space threshold in SC 5.0
  • #3921 Incorrect ordering of events in Dashboard and Events page
  • #3906 Specific characters can not be used in account names and password for new instances
  • #3929 CVE-2024-0056
  • #3926 Custom lifetime manager to prevent Windows Service start timeout - Custom lifetime concrete types
  • #3917 ServiceControl primary and audit instances fail to start during RavenDB recovery

How to know if you are affected

  • #3933, you are affected if you have are using ServiceControl 5.0.0 or later.
  • #3921, you are affected if you have are using ServiceControl 5.0.0 or later.
  • #3906, you are affected if you are adding a new instance in Service Control Management, where it is not possible to add in type specific characters such as /, _, -, +, and = in acccount names
  • #3917, you are affected if you are using primary or audit instances of ServiceControl 4.26.0 or later.

Symptoms

#3933

After upgrading or installing the ServiceControl of version 5.0.0 or higher, a false custom check error notification about the diskspace is sent even though it is within threshold limits.

#3921

After upgrading or installing the ServiceControl of version 5.0.0 or higher, the api sends back an incorrect ordering of events.

#3906

In Service Control Management, when adding a new instance, it’s impossible to type specific characters such as /, _, -, +, and = in the account names field. The keys instead check or uncheck the checkbox for the expansion panels.

#3917

ServiceControl primary and audit instances fail to start and the following message is logged:

ERROR Unhandled exception was caught.
Raven.Client.Exceptions.Database.DatabaseLoadTimeoutException: Raven.Client.Exceptions.Database.DatabaseLoadTimeoutException: Database audit after 00:00:30 is still loading, try again later. Database initialization log:

Any subsequent restarts by the Windows Service Control Manager fail with the same error message.

When to upgrade

If you are affected by #3917, you should upgrade immediately to prevent unnecessary ServiceControl outages.

If you are only affected by #3933, #3921, #3906, you should upgrade during your next maintenance window.

Where to get it

You can download the new versions of ServiceControl from our website.

With thanks,
The team in Particular

Please read our support policy for more details.

2 Likes