stop spam in Windows Event Viewer

5 years ago • updated by 1 year ago • 11

Atm when a computer is Offline (no internet connection) an error event will be logged every few seconds (i think it's something like 1-2-3-5-10-15... ?). This will spam the eventvwr logs (error source:ScreenConnect Client id:0 : System.Net.Sockets.SocketException (0x80004005): ...)

Wouldn't it be better to make it report it once and the eventually report when connection is back ?

Vote

Replies 11
Oldest first
- Newest first
- Oldest first

5 years ago

Yes, painful looking through the mess control makes in the event viewer. I get complaints all the time saying something is wrong because it creates soo many entries.

5 years ago

Is this the latest version? It shouldn't be spamming like that.

5 years ago

all latest Linux version

5 years ago

Look at this cluster.... What a mess. Running 19.6 and will be updating to 20.3 soon.

Just fills and fills the event logs.

3 years ago

Updated photo form 2021.8.

3 years ago

21.11 and it still happens.

Our Cloud Hosted Instance of Control went down for over 8 hours this past weekend and our customers are now extremely angry because we filled their event logs and monitoring systems with millions of alerts.

We just need a simple.. Lost Connection / Connection Returned with some safety for connections that flap. Maybe remember the timestamp from the last write to ensure the event logs are not being spammed.

Look at the garbage below.

System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at ScreenConnect.SocketNetworkConnection.Receive(Byte[] buffer)
   at ScreenConnect.NetworkConnection.<.ctor>b__0_0(BlockBufferReadStream stream)
   at ScreenConnect.BlockBufferReadStream.OnNeedsBufferCycled()
   at ScreenConnect.BlockBufferReadStream.Read(Byte[] buffer, Int32 offset, Int32 count)
   at ScreenConnect.Extensions.ReadByteDefault(Stream stream)
   at ScreenConnect.BlockBufferReadStream.ReadByte()
   at System.IO.BinaryReader.ReadByte()
   at ScreenConnect.MessageSerializer.Deserialize(BinaryReader reader, Type requireBaseClass)
   at ScreenConnect.EndPointManager.ReceiveMessage(BinaryReader reader, Type requiredBaseMessageType)

3 years ago

We are an MSP and we have 100 or so clients that we use ScreenConnect with. Every......single......one .......of them shows these exact errors repeating every so often. Has been going on for years. I REALLY wish that Labtech....ConnectWise....who ever they are these days wout FIX THIS!!

3 years ago

I agree with the posters above. It seems running an RMM system these days really just means cause more issues than before???

I am also finding support is that bad, I actually avoid contacting them knowing the immense amount of my time that will be wasted.

Level 1 read all of their generic trouble shooting and get you to do all the usual, before passing the issue onto someone with brains.... usually all ended by 'its a known issue with no ETA on a fix. Nice.

1 year ago

...anyone else notice no comments from ConnectWise on any of this? It's almost like they are ignoring all of their users....or don't care.

1 year ago

I actually contacted ConnectWise support on this very issue which is how I found this thread. Here's what they said. I asked if it would ever be implemented or if they had an ETA.

May have to right-click Open Image in New Tab to view...

Customer support service by UserEcho