Exception while launching SL Alerter: Type Initializer ZippedMessage

Solved736 viewsDMS Alerter SLAlerter
0
0 Comments

Hi guys,

I face an exception after upgrading to SL Alerter 10.2 (DMA also 10.2) . Did it happen to anyone else?

Jonathan Triboulet [SLC] Selected answer as best 10th February 2022

1 Answer

5
2.58K 2 Comments

Hi Jonathan,

- This issue was reported very recently and also fixed, starting from 10.2.3.0.
The 10.2.0.0 main release should also fixed, starting from CU0 last week.

- The following versions are affected: 10.1.11.0, 10.11.12.0, 10.2.1.0 and 10.2.2.0.

- The issue is caused by RN 30645, but it is fixed with RN 32312 + RN 32431.
1. first fix is a DLL change that needs to be done on the upgrade build server. (for each version).
2. second fix is a server fix for reading out settings for Alerter.

Hope this helps you further

Jonathan Triboulet [SLC] Selected answer as best 10th February 2022
Matthias Declerck [SLC] [DevOps Enabler] commented

For 10.2.0.0, I quickly tested in build 11400 and it all looks fine to me, unless I miss something..
Otherwise said: 10.2 CU0 should be safe.
Jonathan Triboulet [SLC] commented

Thanks a lot Matthias for your answer – I added pictures in the original question of the versions in use. Could it be due to the use of a VPN between the Alerter and the DMA ?
You are viewing 1 out of 1 answers, click here to view all answers.