Exception thrown while trying to write legacy log line - Event Server - Mobotix HUB - AD - Encrypted

ChristophAcs · April 23, 2026, 12:09pm

Around my communtiy plugins we write audit logs, works on many machines/installations today an OEM come to me with the issue that no log lines are visible in managment client.

I have checked the logs and there are no exceptions on the SDK side.

github.com/Cacsjep/mscp

CommunitySDK/SystemLogBase.cs

47c9ca550


      
              catch (Exception ex) { _log.Error($"WriteEntry failed: {ex.Message}"); }
          }
          
          protected void WriteAuditEntry(string messageId, Dictionary<string, string> parameters = null, string permissionState = PermissionState.Default)
          {
              if (!_registered) return;
              try
              {
                  LogClient.Instance.AuditEntry(_appId, _componentId, messageId, GetSiteItem(), parameters, permissionState);
              }
              catch (Exception ex) { _log.Error($"WriteAuditEntry failed: {ex.Message}"); }
          }
          
          
          private static Item GetSiteItem()
          {
              try
              {
                  return EnvironmentManager.Instance.GetSiteItem(
                      EnvironmentManager.Instance.MasterSite);
              }

I found the following strange errors in the LegacyLogClient.log file:

2026-04-23 11:08:34.057+02:00 [   105] ERROR      - Unexpected error occurred: System.ArgumentException: Die Kryptografiesammlung des Tokens unterstützt den Algorithmus "
" nicht.

   bei System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass7_0`1.<CreateGenericTask>b__0(IAsyncResult asyncResult)

   bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   bei VideoOS.LogServer.Communication.ClientWrapper`1.<CallWithRetryAsync>d__11`1.MoveNext()

2026-04-23 11:08:34.058+02:00 [   105] WARNING    - Exception thrown while trying to write legacy log line. Error: System.ArgumentException: Die Kryptografiesammlung des Tokens unterstützt den Algorithmus "
" nicht.

   bei System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

   bei System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass7_0`1.<CreateGenericTask>b__0(IAsyncResult asyncResult)

   bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   bei VideoOS.LogServer.Communication.ClientWrapper`1.<CallWithRetryAsync>d__11`1.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei VideoOS.LogServer.Communication.QueueingClient.QueueingClientWrapper`1.<CallWithRetryAsync>d__16`1.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei VideoOS.LogServer.Communication.Writers.LogWriter.<WriteLegacyLoglineTokenAsync>d__19.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei VideoOS.Log.LogClientInternal.<>c__DisplayClass30_0.<<DoLogWrite>b__1>d.MoveNext()

Its Mobotix HUB 2025 R3 and encryption was on and its on AD env.

After turn off encryption, it works, so is this a known issue ?

LegacyLogClient.log (2.9 MB)

Bo_Ellegard_Andersen · April 24, 2026, 6:46am

Quick clarifying question before reporting it as a bug. Is this running as an Event Server plugin or standalone MIP SDK based app or service?

ChristophAcs · April 24, 2026, 6:46am

Hi Bo,

as event server plugin =)

ChristophAcs · April 24, 2026, 6:50am

@Bo_Ellegard_Andersen here also my GH issue: Auditor Plugin does not write entries in AuditLog (MOBOTIX HUB OEM) · Issue #77 · Cacsjep/mscp · GitHub with some notes and logfiles.

Here is my 2 cents: Auditor Plugin does not write entries in AuditLog (MOBOTIX HUB OEM) · Issue #77 · Cacsjep/mscp · GitHub regarding to the issue itself

Bo_Ellegard_Andersen · April 24, 2026, 7:05am

Thank you. A bug report has now been filed.

You’ve been very thorough in the investigation and data provided, and this should help Milestone Development significantly.

ChristophAcs · April 24, 2026, 7:30am

perfect - thank you

ChristophAcs · May 4, 2026, 6:02pm

@Bo_Ellegard_Andersen any news on this ?

Bo_Ellegard_Andersen · May 21, 2026, 9:11am

Sorry, no, I am reaching out to our developers…

ChristophAcs · May 21, 2026, 11:36am

@Bo_Ellegard_Andersen thank you

Bo_Ellegard_Andersen · June 22, 2026, 5:51am

A fix is in testing, I hope soon to be able to announce that it is available for you.

Rik · July 7, 2026, 11:18am

Dear Christoph,
We got an update from Milestone Development.
During testing, Milestone Development found that the installer is braking the Management Client. Further development caused issues with Server Configurator and the Log server was not able to work as expected. Found that much more effort will be needed for that server, and also patching all components that also contain one of the server communication dlls. As a conclusion, they decided that they will not be able to fix this issue with limited resources.

ChristophAcs · July 7, 2026, 11:42am

Thanks fo updating me, does this mean in OEM the mip sdk log stuff is kinda broken and will not fixed ? is this communicated offical ? or did I understand it wrong ?

Rik · July 13, 2026, 2:46pm

Dear Christoph,

We appreciate your feedback. Milestone Development added explanation and workaround options.

If the customer have certificate, that uses ECDSA, WCF Message Security fails because it requires RSA-OAEP key wrapping — an RSA-only algorithm.
That is why they have the mentioned issue.

The idea of the fix was to switch from Message Security (WSHttpBinding) to Transport Security (BasicHttpBinding over HTTPS) when encryption is enabled, so when using certificate like the one mentioned above, the issue won’t be present.
But as described in the previous comment, that would need changes in the rest of the VMS components, that are communicating with the legacy log server.
As a result, MC was in broken state and much more effort will be needed in order to fix that.

Workaround options are:

Replace the system certificate with an RSA certificate — if the customer can replace the ECDSA certificate with an RSA one,
WCF Message Security will work. This is the simplest fix if they control certificate provisioning.

Disable encryption — When encryption is disabled, the Log Server falls back to its self-signed RSA certificate.

ChristophAcs · July 13, 2026, 2:48pm

ok thanks i will forward this to the OEM partner.
when a workaround exists it should be ok=)

BR