Syed Jahanzaib Personal Blog to Share Knowledge !

October 26, 2021

Veeam B&R: [nbd] Error: Object reference not set to an instance of an object.

Filed under: Veeam B&R — Tags: — Syed Jahanzaib / Pinochio~:) @ 10:45 AM

Scenario:

  • Veeam B&R 9.5 (Ver 9.5.0.1922) installed on Windows Server 2012R2

We were getting failure error on Veeam daily job report for a particular VM guest ,

Preparing backup proxy VMware Backup Proxy for disk Hard disk 1 [nbd]
Error: Object reference not set to an instance of an object.

It was a VM guest that was recently restored via vcenter to another esxi host (under vcsa).

To further troubleshoot, I exported the JOB log using Veeam article, & observed following

[23.10.2021 04:56:01] < 332> cli| Waiting for the next command.
[23.10.2021 04:56:01] < 3936> cli| Next client command: [closeStg].
[23.10.2021 04:56:01] < 3936> cli| :> X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk
[23.10.2021 04:56:01] < 3936> cli| Closing storage ‘X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’.
[23.10.2021 04:56:01] < 3936> cli| MTA backup apartment was created successfully, id ‘0x000001EA804A1E10’.
[23.10.2021 04:56:01] < 3048> cli| Thread started. Thread id: 3048, parent id: 3936, role: MTA invoke thread
[23.10.2021 04:56:01] < 3048> cli| Entering MTA invoke thread.
[23.10.2021 04:56:01] < 3048> stg| There is no file ‘HostFS://X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’ in the files cache.
[23.10.2021 04:56:01] < 3936> stg| There is no file ‘HostFS://X:\VMBKP\Daily VM BKP job via VCSA\MY_VM_GUEST.16D2021-10-23T030322.vbk’ in the files cache.
[23.10.2021 04:56:01] < 3936> cli| Storage is closed.

To sort the issue I did following & the issue got resolved

  • Remove the VM from the VEEAM job
  • Remove the VM from inventory from particular ESXI host,
  • Re-added the VM in ESXI
  • Added the VM in VEEAM job

Afterwards, the job ran fine without any error.

 

Veeam B&R: Win32 Error / Code: 67 Cannot connect to the host’s administrative share


Continued post from


Scenario:

  • Veeam B&R 9.5 (Ver 9.5.0.1922) installed on Windows Server 2012R2

 

After running the daily job, we were observing following failure notice for particular windows 7/10 OS.

Processing WIN10-LOG Error: Failed to connect to guest agent. Errors: ‘Cannot connect to the host’s administrative share. Host: [WIN10-LOG]. Account: [admin]. Win32 error:The network name cannot be found. Code: 67 Cannot connect to the host’s administrative share. Host: [19.168.0.10]. Account: [admin]. Win32 error:The specified network name is no longer available.

After some R&D , I had to create a new DWORD value in registry at effected windows , & afterwards the issue got resolved.

Edit the registry on effected Windows & perform following

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry doesn’t exist, follow these steps:
    1. On the Edit menu, point to New, and then select DWORD Value.
    2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy and then select Modify.
  5. In the Value data box, type 1, and then select OK.
  6. Exit Registry Editor.

On a safe side , perform following as well,

  • Disable windows based firewall
  • Disable windows UAC

Reboot the affected windows machine & now RUN the backup job on Veeam B&R server.


Exporting VEEAM job LOGS for troubleshooting purposes

It’s a good idea to export JOB logs in order to troubleshoot the error in depth.

Follow below veeam article


Regard’s
Syed Jahanzaib

%d bloggers like this: