GetHostInfo failed after update

[kbov]

Hey here,

After I updated my Veeam infrastructure (Veeam B&R 9.5.0.1536), all my jobs go in failed state. All jobs are related to Windows Server with Exchange server.

Here some details:

Code: Select all

Queued for processing at 12/31/2017 12:14:53 PM 
Required backup infrastructure resources have been assigned 
VM processing started at 12/31/2017 12:14:58 PM 
VM size: 420.0 GB (225.8 GB used) 
Getting VM info from vSphere 00:11
Network traffic will be encrypted 
Using guest interaction proxy ********* (Same subnet) 
Inventorying guest system 00:02
Task failed unexpectedly 
Network traffic verification detected no corrupted blocks 
Processing finished with errors at 12/31/2017 12:15:23 PM 

Code: Select all

[31.12.2017 12:15:20] <20> Info     Inventorying guest system
[31.12.2017 12:15:20] <20> Info     VSSControl: GetHostInfo
[31.12.2017 12:15:20] <20> Info     Getting host information (Secured)
[31.12.2017 12:15:20]      Info             Dropping secure strings.
[31.12.2017 12:15:20]      Info             Dropping secure strings.. Ok.
[31.12.2017 12:15:20]      Info             Requesting public key.
[31.12.2017 12:15:20]      Info             Requesting public key.. Failed.

As far as I understand, the job failed because of this request over the public key. I tried this KB: https://www.veeam.com/kb1813
Still failed

I didn't found any error from Windows Event Log.

Any idea? Thanks for reading

[Mike Resseler]

Hi Kbov,

I have no idea at this moment what could cause this. Can you please log a support case and post the case ID here (and the follow-up after working with our engineers)? They will be able to get much more information out of the logs

Thanks
Mike

[kbov]

Solved. Here our fix:
- .Net Framework updated to 4.6.2
- Microsoft Visual C++ 2008 updated to 9.0.30729.4148

[Mike Resseler]

Thanks for coming back with the fix Kbov.

Did you make this updates on the VBR server alone or also on other servers?

Thanks
Mike

[kbov]

Sorry for the late reply.

Updates was installed both on VBR server and VBR proxy.

[Mike Resseler]

No worries. Thanks for letting us know.