Skip to main content
  • EN

Hello,

 

Working for an MSP with a large amount of customers running B&R 12 (12.1, 12.2, and 12.3), all of our customer’s individual backup servers are having their available storage space taken up by a log text file in the below folder:

C:\ProgramData\Veeam\ErrorMonitoring\veeam_error_log.txt

The file is consistently updated each minute with error messages pertaining to failed connection attempts, despite their being no issues with any jobs failing due to similar reasons:

 

<2025-03-19 10:01:10] Errors detected in Veeam log: o2025-03-19 10:01:10] Error detected: 2024-09-23 18:41:13.3469 4ERROR ] 4908 9__10] TmBsCpJobsMonitor: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-23 18:41:13.3781 7ERROR ] 4908 9__10] DefaultCollector: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-23 18:41:13.3781 7ERROR ] 4908 9__10] DefaultCollector: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4453 4ERROR ] 14312 3__76] TmAgentMonitor: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4453 4ERROR ] 14312 3__44] TmBsCpJobsMonitor: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4609 6ERROR ] 14312 3__73] DefaultCollectorExtension: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4609 6ERROR ] 14312 3__73] DefaultCollectorExtension: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4609 6ERROR ] 14312 3__86] DefaultCollectorExtension: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4609 6ERROR ] 14312 3__86] DefaultCollectorExtension: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; n2025-03-19 10:01:10] Error detected: 2024-09-24 17:19:31.4609 6ERROR ] 14312 3__76] DefaultCollector: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

 

(That is just a brief snippted of the log - each line is at least 20 times longer than the above with the same messages repeated, and a new generated line each minute).

 

Is there a way to limit the size of this generated log? I have tried altering values within the registry for values such as “MaxLogCount”, “MaxLogSize”, and “AgentLogOptions”, however these don’t appear to affect this particular folder and log.

 

Many thanks.

Hi ​@SBKCallum -

Have you seen this KB? https://www.veeam.com/kb1825

It appears you have the right idea of registry items to change. But, for that specific log file, it may be your best bet to reach out to Veeam Support on how best to control the size/rotation of that specific log file.

Best.

The KB Shane posted is great but if you find that you are not having the desired affect with the settings then as stated contacting Support for this one is probably the best thing.  I am sure there is a setting somewhere they can help tweak hopefully.  Let us know how you make out.

That doesn’t look like a normal veeam log file, namely because it’s not a .log file which is how veeam always stores its logs.

That directory doesn’t exist on my servers, I would advise open a support case, as this really doesn’t look like a correct log file (not sure why that .txt is in the Veeam programdata directory, but it should not be there)

I’m not confident that file is produced by Veeam, though the error text from the file does look like our log format.

Actually, more I look at it, looks like some monitoring tool/script, because it even tells “errors detected in Veeam Log” - we don’t do that, so this really looks like some third party script/tool

Thanks guys for your ideas. We’re going to try raising this with Veeam support to see if they have any ideas.

 

We did try the registry fixes from the article ​@coolsport00 sent but this did not work. Interesting point from ​@ddomask - it does seem to be an odd way of storing the log file in a seperate folder and format to the other Veeam logs, so we’re also going to scrape our systems to see if anything is interfering/monitoring and generating these logs - possibly our Anti-Virus?

 

I’ll drop some updates if we resolve this for future reference - for now, a batch script to clear the file every hour is helping keep the used space down.

 

Cheers guys :)

@SBKCallum,

Try using Process Monitor (ProcMon) https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Point it at the C:\ProgramData\Veeam\ErrorMonitoring directory and start capturing, go get a coffee or enjoy a walk, come back and check what process has been accessing it.

Comment


Terms & Conditions