Not seeing anything like this as of yet but it is only my homelab servers I have upgraded.  Will wait to see what happens when we begin our production updates in the next week.

There was another issue with V11 servers.

But I think I started the server too fast after rebooting in this case.

Closing the console and restarting the Veeam Guest Catalog Service cleared this message and the Catalog Cleanup Process finished successful the next time.

I have the latest of v11, including the newly released patch, @JMeixner and am not seeing these errors.

Thanks @coolsport00 , with V11 it was probably my own fault. But with V12 the error persists.

Actually...in scrolling down a bit further...I do see this error. It appears the error is stemming from the VBR server itself refusing a connection on port 9393. This was 2 days ago. I received the error shortly after installing the Patch it seems. I don’t know how often ‘Catalog Cleanup’ runs. But, I haven’t seen the error since the 7th. Are you seeing this every day?

UPDATE: I sorted the Job Name column and see I have had a successful run of that job as of yesterday. So maybe it was a one-off warning? Hopefully….

It seems to run after server start and then every day.

With V11 is seems to be a timing problem. Not all services are properly started after server reboot and this causes the error. This would explain, why it runs successful at the next day.

Good to know. Thanks for the additional info.

Ahaaa…. Now one day is over since upgrading the V12 server just two minutes ago ).

And now the Catalog Cleanup has finished successfully…

So, it seems, that it is a timing issue with V12, too.

@JMeixner 

Try to restart Veeam Guest Catalog Service on VBR server

Yes, I have done this.

On V11 this resolves the issue immediately. On V12 not.
 

I’ve also noticed this error in some environments but as the next attempts succeeded, I just thought that the services weren’t started/ready after the update.