v11 - host lookup failure now shows as "Error in the application"

[yavor.indzhev]

Same problem here. Started just after upgrade to v.11
Happens only on some VMs.

In addition some of the VMs are failing with:

Code: Select all

11:06:28	Processing XXXXX Error: Failed to open VDDK disk [[XXXXXX] XXXXX/XXXXXX.vmdk] ( is read-only mode - [true] ) Logon attempt with parameters [VC/ESX: [XXXXX];Port: 443;Login: [XXXX\XXXX];VMX Spec: [moref=vm-14409];Snapshot mor: [snapshot-180208];Transports: [nbd];Read Only: [true]] failed because of the following errors: Failed to open disk for read. Failed to upload disk. Skipped arguments: [vddkConnSpec>]; Agent failed to process method {DataTransfer 	07:36

Just opened a ticket:
05001173

[veremin]

Let us wait till support team analyze the debug logs and potentially your virtual and backup infrastructures and find the root cause. We will watch the case investigation. Thanks!

[Anguel]

Now I got another "Error in the application" on a copy job that tries to copy some notebook backups that arrived from unmanaged Veeam Agents.
This time I decided to open a case ID: #02073163

[saahi]

Since upgrading to v11(a) we have been getting this error almost daily at least from one of our more than 100 veeam installations. There is no any specific error which causes this message. This comes from vss writers, repository connection, connection to virtual host, you name it. Getting quite frustraded with this error message. Luckily we have bunch of v10 installations which errors are correctly reporting and quite well pointing to right direction.

This time it was changed password...

[Gostev]

Strange as this bug with the exception handling falling through to this generic error should have been fixed in 11a, and it should now again show the actual errors.
@Egor Yakovlev can you check with developers/QC on this please?

[Egor Yakovlev]

On it.