Hi tinto1970,
Thank you for sharing the details on the case and what's been tested so far, and sorry to hear about the troubles.
I can understand the logic on the registry value -- personally, I would expect we get a corresponding SQL timeout exception from Veeam on this as the actual failing message, but perhaps Support saw something in the logs which indicated something similar.
Just out of curiosity, are you adding the VBR hosts by FQDN or the short hostname/IP? I'd be curious if IP worked; I seem to recall when the Enterprise Manager authentication changed (v11 I think?) this could cause issues based on the EM certificate, and testing with IP might be reasonable.
Thank you for sharing the details on the case and what's been tested so far, and sorry to hear about the troubles.
I can understand the logic on the registry value -- personally, I would expect we get a corresponding SQL timeout exception from Veeam on this as the actual failing message, but perhaps Support saw something in the logs which indicated something similar.
Just out of curiosity, are you adding the VBR hosts by FQDN or the short hostname/IP? I'd be curious if IP worked; I seem to recall when the Enterprise Manager authentication changed (v11 I think?) this could cause issues based on the EM certificate, and testing with IP might be reasonable.
Statistics: Posted by david.domask — Apr 22, 2025 7:53 am







