Clients not reporting to console after upgrading to 22.4.2699.724

Avast Business On-Premise Management Console & Clients
1

Hi, on server with on-premise console we upgraded program to 22.4.2699.724. After restart no clients are reporting to console, they all are on-line, but their reporting time is wrong.

2

I cannot even use update task – after 40 minutes no computer did anything.

3

One more thing. In log I see these error:

2022-05-23 13:02:22.361 ERROR [00000000000000000000000000000001] [1653303742314-291] c.a.b.e.CommonExceptionLogger [ClientPool:com.avast.business.web.configuration.thread.CloudThreadPool$5@2e82c4ad]: Illegal licensingSchemaId: b2b-ssp-1s-3y_v1 for brand:AVAST (CommonExceptionLogger.java:120)
java.lang.IllegalArgumentException: Illegal licensingSchemaId: b2b-ssp-1s-3y_v1 for brand:AVAST

And I cannot see licences in console.

4

Comfirmed, same behaviour here. >:(

I suposse that the “sever error” on subcriptions is because the migration from Avast Business Antivirus to Avast Essential Business Security.

5

Hi guys, I forwarded it, let’s see…

6

Dev-Reply:

Can we get more info? accountKey, companyName, companyId, WK or something?
It would be great to get the technical support package from one station at least.

7

I already opened ticket with support and sent them logs.

But they confirmed that problem is with license-name changes in current week.

8

Great, thanks for the feedback.

9

Dev-Info: We have found some Wallet keys where customer use On Premise console along with Cloud console. This is not supported. Every console should have their own wallet key. Support received list of customers with that issue.

10

I’m having the same issue with the license section of the On-Premise Console (version 7.29.990).
If I open subscriptions (8 days remaining btw) I get an internal server error with the exact same “llegal licensingSchemaId: b2b-ssp-1s-3y_v1 for brand:AVAST” in my main.log file.