Avast WEBforum
Business Products => Avast Business => On-Premise Management Console & Clients => Topic started by: mschedler1 on February 08, 2021, 11:27:46 PM
-
I had this fixed before by adding the "MaxConnections" entry to the .ini file... BUT now that these have all been moved to Registry, it is no longer working. The Entries exist in the locations below, but I'm getting this stupid error again. This is on my Terminal Servers where people need to get email... 50 (program default) is NOT high enough. Two registry entries exist and are set as below.
Anyone know anything about this at all... I searched the forum... there's a thread in there that is nearly identical but contains no resolution.
HKEY_LOCAL_MACHINE\SOFTWARE\AVAST Software\Avast\properties\EmailShield\EmailScanner\MaxConnections = 100
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AVAST Software\Avast\properties\EmailShield\EmailScanner\MaxConnections = 100
Log shows:
[2021-02-03 15:53:43.429] [info ] [MailShield ] [ 1900: 5280] IMAP Closing connection due to MaxConnections
[2021-02-03 15:53:43.429] [info ] [MailShield ] [ 1900: 5280] Processes: thunderbird.exe[50]
-
Whilst I don't have any experience using the On-Premise Management Console & Clients (as an avast free user).
That said the error should give an indication on the number of connections and by what process/es, that it exceeds the maximum number of concurrent connections.
A screenshot of that may help determine the function eating all of the connections.
So you would have to increase the MaxConnections to a figure greater than that.
Or you could set it to 0 as zero 0 = no limit.
I don't know if this would work on the On-Premise Management Console & Client, client machine or if this would be to be set on the console or not.
-
Thunderbird is the client and yes, due to the fact that I have at least 20 users logged in the program default of 50 is the issue. Adding the "MaxConnections" option (LONG AGO) solved the issue, BUT it came back when the settings from the .INI files were converted to registry entries (Client ver. 20.7 I believe).
The needed entry (see my previous post) was migrated automatically by the upgrade and it is in the registry but obviously not working. Thunderbird by default uses 5 connections per user... as soon as I pass 10 users, the errors start. As I said, I dealt with this issue LONG ago and the .INI entry was working... until the upgrade.
Notice the LOG's second line contains "Processes: thunderbird.exe[50]" which I might indicate that the client default has reverted to 50 as I suspect.
-
This is certainly the difference in the On-Premise Management Console & Clients having different settings to that of a stand alone Avast PC installation. So that too I guess would apply in the registry settings.
I don't know if you have tried a higher MaxConnections figure or setting it to 0 as suggested. Or if this is a general restriction in the software.
Other than this, information I have gleaned on avast5.ini and limited experience using the registry equivalent in the Windows PC Avast product I have no experience of the On-Premise Management Console & Clients.
Edit: I have tried to draw some attention to this topic.
-
Bump!
-
Still an issue... don't always get this and I did bump the MaxConnections setting (in Registry) up to 150... but I am getting the error anyway.
This is the error (again):
An error occurred while sending mail: The mail server sent an incorrect greeting: concurrent connection limit in Avast exceeded(pass:0, processes:thunderbird.exe[50]).
I'm going to attempt to get assistance from support but that hasn't gone too well the last few times.
-
I have reported it, but haven't had any 1nput to your topic, hence my Bump to bring the topic up the list of active topics.
Have you use the support ticket system ?
You should get an email response with a support ticket ID number ?
-
Just finished it... Request# is 12709420 if that helps in any way.
-
Just finished it... Request# is 12709420 if that helps in any way.
It helps in that, if you don't get any response after a few days we can try to chase up the ID Number.
-
FWIW... After the usual hoops (gather/send logs and dump files) I received a response from Support:
"There is an issue with the web shield that is causing the settings to not apply correctly we have an open case with dev at this time looking into fixing this issue."
No indication on how long before the fix is pushed out. At least this time I didn't have to struggle to make someone understand the issue (is that cynical? a bit maybe).
-
Thanks for the clarification.
-
It's been almost a month and I'm still getting complaints of this from my Terminal Server users... Is it possible to find out how long they expect this to take? This is frustrating!
-
If you have an open case, presumably you have an email contact in relation to this open case (ID) ?
Unfortunately as an Avast User there is not much I can do other than try to report it.
-
Well it looks like Program Version 21.2 is out (it has installed on at least two of my devices), but there's no release notes posted yet. Maybe it's in this new release.
-
Well it looks like Program Version 21.2 is out (it has installed on at least two of my devices), but there's no release notes posted yet. Maybe it's in this new release.
Seek and you will find, though the notes are not detailed. The latest program release topic is a sticky topic at the top of the list.
Regular Windows consumer version https://forum.avast.com/index.php?topic=255221.0
However I don't know if all of the stuff would be the same for the business product.
EDIT, I checked the On-Premise Management Console & Clients, listing and can see no Program Update sticky.
-
I did see that post. I'm not sure if there's anything in the "highlighted bug fixes" matching my issue. The support email I got from them says, "the Web Shield is causing the settings to not apply correctly..." so there's that. The 21.2 update is not pushing out automatically yet, but a manual update will so maybe I'll just push it out to the servers after I verify it doesn't break anything on my system.
-
Thanks for the feedback.
I have also reported this, so hopefully it will draw some attention.
-
I did see that post. I'm not sure if there's anything in the "highlighted bug fixes" matching my issue. The support email I got from them says, "the Web Shield is causing the settings to not apply correctly..." so there's that. The 21.2 update is not pushing out automatically yet, but a manual update will so maybe I'll just push it out to the servers after I verify it doesn't break anything on my system.
Avast for Business 21.2 has just been released, see https://forum.avast.com/index.php?topic=260104.0
If you wish to upgrade your devices to 21.2 prior to the automatic upgrade, then you can create a new Task (Update device – Program update task) from your console.
A system reboot will be required to complete the installation. There will be no forced reboot unless you have set this in your device policy settings. Servers will never reboot regardless of your device policy settings.