Retention and errors in log file

[reiso22]

Hi,

We have set "retention policy for events" to 3 months, but noticed older events still available, which are older 4 months.
Therefore we tried to check some logs and noticed, that we get continously following errors in "SchedulingService.log":

2019-02-26 17:28:05.2358 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:05.2670 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:05.2983 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:05.3295 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:05.3608 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:10.4079 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:10.4392 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:10.4704 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:10.5019 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:10.5329 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:15.5801 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:15.6113 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:15.6426 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:15.6738 ERROR 10412 7 Decode via Monitor
2019-02-26 17:28:15.7051 ERROR 10412 7 Decode via Monitor

These error messages seems to have started since we upgraded to Update 4. We are using the free edition. Everything else is working fine.

Any idea what these errors are coming from and why retention seems to be not working? We tried already to set different user account for the VeeamRSS service with no luck.

Thank you.

[wishr]

Hi Reiso,

As usual when logs analysis is required - please reach out to our support team directly for a comprehensive investigation and post your case ID here. Note, that we offer technical support service even for customers using free products.

Thanks

[reiso22]

Case ID: 03436660

[reiso22]

Got following info from support:
"This is an error message which started appearing in update 4 logs. However you are right that this does not affect anything and thus should be matched as Info. This behavior is planned to be corrected in one of the future releases."

[wishr]

Hi,

As far as I see the conversation is still going, so please keep working with the support team on the investigation and let us know if any sort of assistance is required.

Thanks,
Fedor