Avast WEBforum

Business Products => Avast Business => On-Premise Management Console & Clients => Topic started by: pjirsak on October 09, 2019, 05:35:03 PM

Title: Avast Business On-Premise Management Console Version 7.16
Post by: pjirsak on October 09, 2019, 05:35:03 PM
Release Notes: Avast Business On-Premise Management Console (October 9, 2019)
Console version: 7.16
Agent version: 4.16
Windows Antivirus: 19.7
Mac OS X Antivirus: 13.13

Release Summary
This release contains improvements and bug fixes to our Avast Business On-Premise Management Console.

Improvements
1.   [CBC-8095]   Added support for completely offline networks
2.   [CBC-9213]   Updated PostgresSQL to v10.4
On-Premise Management Console has been upgraded to the current cloud version along with many small or large improvements and bug fixes.

Bugs
3.   [CBC-9186]   Fixed an issue with a default policy being generated twice
4.   [CBC-7107]   Fixed an issue with registration of a device which has the console installed on itself
5.   [CBC-6731]       Fixed an issue with upgrading the on-premise console
6.   [CBC-6876]   Fixed an issue with upgrading the on-premise console
7.   [CBC-6965]   Fixed an issue with the password validation so it does not allow using the same e-mail address as for the account
8.   [CBC-7052]   Fixed an issue with problematic console starts after upgrading to 6.1
9.   [CBC-7099]   Fixed an issue with showing an error message after putting a wrong password
10.   [CBC-6998]   Fixed an issue with a session expiration when a browser is closed

Avast Business On-Premise Management Console Version 7.16 Release Notes (http://bit.ly/35gdJtt)

Actual installation package is going to be available for upgrade early next week.
      
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Infratech Solutions on October 09, 2019, 05:37:19 PM
How is the correct procedure for the update?
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: cuputraerwin on October 11, 2019, 09:10:11 AM
Dear Avast Support Team/ Friends,

I just download latest " avast business management console on premise " offline installer via avast website,
and after installed, it's still use 6.0.14 version.

Base on manual,

I read that it will show notification if there is any new update available,
but until now i didn't get any notification on my avast console to update to 7.16.  ;D
It's normal or i need to do something to trigger the update challange?

If not, Then How to update from 6.0.14 to 7.16? :D

Thanks and Best Regards,
Erwin
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Asyn on October 11, 2019, 09:15:18 AM
Actual installation package is going to be available for upgrade early next week.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Lukas Mizoch on October 16, 2019, 11:41:29 AM
It's almost middle of week. 😉
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Infratech Solutions on October 18, 2019, 12:06:28 PM
Technically, 7.16 is ready. Now it's under the security inspection procedure which took longer than expected.

Plan was last week, early this week. Now AVAST is working with team on new ETA.

It should be very very soon.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: claudiuc on October 25, 2019, 10:20:52 AM
Another week, no updates...  >:(
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Lukas Mizoch on November 03, 2019, 04:21:05 PM
Almost month… ⌛
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: mikeav73 on November 05, 2019, 03:33:31 PM
Dear Avast Support Team/ Friends,

I just download latest " avast business management console on premise " offline installer via avast website,
and after installed, it's still use 6.0.14 version.

Base on manual,

I read that it will show notification if there is any new update available,
but until now i didn't get any notification on my avast console to update to 7.16.  ;D
It's normal or i need to do something to trigger the update challange?

If not, Then How to update from 6.0.14 to 7.16? :D

Thanks and Best Regards,
Erwin

Hello, I have the exact same problem  ;)

@ Avast support team
 Is there any update on this new version of the console?

Thank you in advance.

Kind regards,

Mike
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: claudiuc on November 08, 2019, 09:18:49 AM
One month later, complete silence...
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: mschedler1 on November 22, 2019, 12:10:23 AM
They released another version for the cloud today... but still nothing for On-Premise... c'mon Avast. >:(
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: mickey.b on December 02, 2019, 06:57:19 PM
One month later, complete silence...
They released another version for the cloud today... but still nothing for On-Premise... c'mon Avast. >:(

I apologize, but we are still testing the newest on-prem console, and the final release is currently scheduled in about week or two (however, this could change). For anyone who's interested, here's the test OBC v7.16 (without the complete Offline Update Support at the moment)...

https://share.avg.com/steam/SMB/OBC%207.16%20without%20offline%20support/avast_business_mc_setup.exe (https://share.avg.com/steam/SMB/OBC%207.16%20without%20offline%20support/avast_business_mc_setup.exe)

The final version will include the offline support, and you should be able to install this test version directly on-top of the current v6.0.14 on-premise console. Please Submit idea at https://portal.productboard.com/afb/1-avast-business-management-console-and-antivirus/tabs/1-planned (https://portal.productboard.com/afb/1-avast-business-management-console-and-antivirus/tabs/1-planned)

Happy testing! ;D
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: mschedler1 on December 04, 2019, 09:18:12 PM
Be advised... upgraded from 6.0... I now have systems showing an error about an Agent Version needing update while others don't show that field at all (running upgrades did not help)... And it uninstalled Web and Email Shields from ALL settings templates for Windows Servers (I know these were active before this upgrade). Agent Version might be a glitch that I can ignore, but to remove shields like that... on three terminal servers with 40+ users... not good.
And strangely, in the General Settings tab for Windows Workstations, Program Updates has BOTH Automatically and Manually options selected... can't be changed to one or the other as far as I can tell. I'll have to try creating a new template and see what that looks like.
Edit: New Template did not help... Program Updates on newly created template shows both options selected.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: claudiuc on December 05, 2019, 10:07:43 PM
The final version will include the offline support, and you should be able to install this test version directly on-top of the current v6.0.14 on-premise console. Please Submit idea at https://portal.productboard.com/afb/1-avast-business-management-console-and-antivirus/tabs/1-planned (https://portal.productboard.com/afb/1-avast-business-management-console-and-antivirus/tabs/1-planned)

Happy testing! ;D

We need offline support ASAP! 7.x without offline is useless!
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: pjirsak on December 18, 2019, 01:45:38 PM
Hi all, I am happy to announce that the update 7.16 of our On-Premise Management Console has been finally released and is available for update.

Also, I'd like to apologise you for the inconveniences related with the postponed release.
Best, Pavel
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Jarosław30 on December 19, 2019, 12:59:08 AM
I have critical issue after upgrading On Premise Console to latest version 7.16. Installer finished normally, it just upgraded Postgres, created backup dump, installed MS C++ 2017 and upgraded console, but at the end it refuses to start. Avast Console Service won't start. Log files shows error:

2019-12-19 00:07:12.740 ERROR [] [] o.s.boot.SpringApplication [main]: Application run failed (SpringApplication.java:842)
java.lang.IllegalStateException: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
       at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:276)
       at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:237)
       at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:200)
       at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:173)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
       at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)
       at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)
       at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)
       at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)
       at com.avast.bc.BusinessConsoleApplication.main(BusinessConsoleApplication.java:50)
Caused by: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
       at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:166)
       at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:67)
       at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
       at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:114)
       at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:269)
       ... 12 common frames omitted
2019-12-19 00:07:12.846 ERROR [] [] com.avast.bc.StartupListener [main]: Start failed: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]] (BusinessConsoleApplication.java:58)

Need urgent fix.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Joseph367 on December 19, 2019, 03:48:31 AM
How to download it please?  I usually prefer to do clean installs rather than upgrades.  Is there a link to download it from? 
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Infratech Solutions on December 19, 2019, 08:46:53 AM
Download link: https://www.avast.com/download-thank-you.php?product=BMS-DOWNLOAD&locale=en-ww
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Lukas Mizoch on December 19, 2019, 10:15:08 AM
I have critical issue after upgrading On Premise Console to latest version 7.16. Installer finished normally, it just upgraded Postgres, created backup dump, installed MS C++ 2017 and upgraded console, but at the end it refuses to start. Avast Console Service won't start. Log files shows error:

2019-12-19 00:07:12.740 ERROR [] [] o.s.boot.SpringApplication [main]: Application run failed (SpringApplication.java:842)
java.lang.IllegalStateException: java.lang.IllegalStateException: Logback configuration error detected:

Didn't you sometimes earlier change log settings in your config?
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Infratech Solutions on December 19, 2019, 10:25:10 AM
Check the permisions on the file logbak.xml on C:\Program Files\AVAST Software\Management Console\console\config
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Jarosław30 on December 19, 2019, 10:25:54 AM
No, I didn't. Log settings were default ones.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Jarosław30 on December 19, 2019, 10:31:20 AM
This file have 'Full control' for groups SYSTEM and Administrators. That's all.
Avast console was launched on user Administrator which is a member of group Administrators
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Infratech Solutions on December 19, 2019, 10:34:13 AM
Can you read the file? Test to give access to ALL and restart.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: GeorgeP on December 19, 2019, 10:43:16 AM
This file have 'Full control' for groups SYSTEM and Administrators. That's all.
Avast console was launched on user Administrator which is a member of group Administrators

This appears to be an issue we've come across previously - can you please send me your registered details so I can forward you a workaround?

Thanks,

George
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Jarosław30 on December 19, 2019, 10:48:02 AM
I just sent you an email.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: GeorgeP on December 19, 2019, 11:06:35 AM
I just sent you an email.

Thank you - information is on its way. Based on the results, we will post a KB about the issue here.

Thanks,

George
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Andy_78 on December 19, 2019, 04:19:44 PM
I'm having a very similar issue.  I just created a new thread.

I have critical issue after upgrading On Premise Console to latest version 7.16. Installer finished normally, it just upgraded Postgres, created backup dump, installed MS C++ 2017 and upgraded console, but at the end it refuses to start. Avast Console Service won't start. Log files shows error:

2019-12-19 00:07:12.740 ERROR [] [] o.s.boot.SpringApplication [main]: Application run failed (SpringApplication.java:842)
java.lang.IllegalStateException: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
       at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:276)
       at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:237)
       at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:200)
       at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:173)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
       at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
       at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)
       at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)
       at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)
       at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)
       at com.avast.bc.BusinessConsoleApplication.main(BusinessConsoleApplication.java:50)
Caused by: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
       at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:166)
       at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:67)
       at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
       at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:114)
       at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:269)
       ... 12 common frames omitted
2019-12-19 00:07:12.846 ERROR [] [] com.avast.bc.StartupListener [main]: Start failed: java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]] (BusinessConsoleApplication.java:58)

Need urgent fix.
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: johan27 on December 20, 2019, 08:24:02 AM
Similar problems for me!!


2019-12-19 22:32:44 Commons Daemon procrun stderr initialized
Logging system failed to initialize using configuration from '../config/logback.xml'
java.lang.IllegalStateException: Logback configuration error detected:
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@30:31 - no applicable action for [totalSizeCap], current ElementPath  is [[configuration][appender][rollingPolicy][timeBasedFileNamingAndTriggeringPolicy][totalSizeCap]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@78:85 - no applicable action for [rollingPolicy], current ElementPath  is [[configuration][appender][rollingPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@79:30 - no applicable action for [fileNamePattern], current ElementPath  is [[configuration][appender][rollingPolicy][fileNamePattern]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@80:23 - no applicable action for [minIndex], current ElementPath  is [[configuration][appender][rollingPolicy][minIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@81:23 - no applicable action for [maxIndex], current ElementPath  is [[configuration][appender][rollingPolicy][maxIndex]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@84:89 - no applicable action for [triggeringPolicy], current ElementPath  is [[configuration][appender][triggeringPolicy]]
ERROR in ch.qos.logback.core.joran.spi.Interpreter@85:26 - no applicable action for [maxFileSize], current ElementPath  is [[configuration][appender][triggeringPolicy][maxFileSize]]
   at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:166)
   at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:67)
   at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
   at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:114)
   at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:269)
   at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:237)
   at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:200)
   at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:173)
   at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
   at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
   at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
   at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
   at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)
   at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)
   at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)
   at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)
   at com.avast.bc.BusinessConsoleApplication.main(BusinessConsoleApplication.java:50)
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: GeorgeP on December 20, 2019, 01:21:39 PM
Hi,

We will be posting a KB later today regarding this issue, you can use these steps in the meantime:

-   Download the logback.zip:

https://share.avg.com/steam/SMB/logback.zip

-   Extract the logback.xml to the disk.
-   Rename the existing logback.xml in C:\Program Files\Avast Software\Management Console\console\config\ (e.g. logback.xml.old).
-   Copy the logback.xml from the extracted zip to the config folder.
-   Start the Avast Business Management Console service.
-   Restart both of the Avast Business Management Console services.
-   The Avast Business Management Console should now be accessible.

Any issues please let me know.

Thanks,

George
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: johan27 on December 20, 2019, 01:52:07 PM
Hi,

We will be posting a KB later today regarding this issue, you can use these steps in the meantime:

-   Download the logback.zip:

https://share.avg.com/steam/SMB/logback.zip

-   Extract the logback.xml to the disk.
-   Rename the existing logback.xml in C:\Program Files\Avast Software\Management Console\console\config\ (e.g. logback.xml.old).
-   Copy the logback.xml from the extracted zip to the config folder.
-   Start the Avast Business Management Console service.
-   Restart both of the Avast Business Management Console services.
-   The Avast Business Management Console should now be accessible.

Any issues please let me know.

Thanks,

George


It worked!! Thanks George!


Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: Andy_78 on December 20, 2019, 03:07:14 PM
Worked for me as well, thank you.

Hi,

We will be posting a KB later today regarding this issue, you can use these steps in the meantime:

-   Download the logback.zip:

https://share.avg.com/steam/SMB/logback.zip

-   Extract the logback.xml to the disk.
-   Rename the existing logback.xml in C:\Program Files\Avast Software\Management Console\console\config\ (e.g. logback.xml.old).
-   Copy the logback.xml from the extracted zip to the config folder.
-   Start the Avast Business Management Console service.
-   Restart both of the Avast Business Management Console services.
-   The Avast Business Management Console should now be accessible.

Any issues please let me know.

Thanks,

George
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: GeorgeP on December 20, 2019, 05:10:03 PM
Thank you for the feedback, we have published a KB article about this issue here:

https://kb.support.business.avast.com/GetPublicArticle?title=Service-Stops-Upgrading-OnPremise-716

Thanks,

George
Title: Re: Avast Business On-Premise Management Console Version 7.16
Post by: PUOLEPARG on March 23, 2020, 10:58:15 AM
Hello,
We are On March 2020
The console version 17.16 is it online for download and update?

I'm always on 6.0.14 version

and i wait always the same functions to cloud version (planning reports / export reports / etc...)

THank you