Skip to main content
  • EN

I’m using Veeam Backup & Replication 12.3 integrated with a virtual infrastructure running on Nutanix AHV 6. I have a backup job configured with Application-Aware Processing enabled to back up a SQL Server instance hosted on a VM named SRV_GESTAOX. However, when running the job, I receive the following error:


17/04/2025 17:09:22 :: SRV_GESTAOX : Object reference not set to an instance of an object.  
17/04/2025 17:09:23 :: Job finished with error at 4/17/2025 5:09:23 PM

As part of the troubleshooting process, I’ve already tried using the local Administrator account and tested credentials using the format hostname\username. The credentials test in the Veeam job configuration passes successfully, so authentication doesn’t seem to be the issue.

What could be causing this .NET-style error, and what steps would you recommend to further troubleshoot or fix the problem?

In my experience this error message is pretty undescriptive to what is actually going on in the background. It doesn’t seem to imply your credentials are incorrect, and like you said it passes all credential tests.

If it was me the first thing I’d be doing it creating a Veeam support case and uploading logs. Perhaps try digging into the job log yourself while waiting on support’s response. 

Thanks for your input! Yeah, I agree,  the error is really vague and doesn’t give much direction. I’ve already opened a support case. In the meantime, I’ll also dig into the job logs myself and see if I can find anything more specific.

 

I’ll update here if I discover something useful.

Also check which version of the plugin you are using and update it if necessary - KB4299: Build Numbers and Versions of Veeam Plug-in for Nutanix AHV

Hi ​@matheusgiovanini 

  • try checking the C:\ProgramData\Veeam\Backup\VeeamGuestHelper\ logs.
  • On SQL server in conjunction with backup failure check event viewer
  • check with “vssadmin list writers” and “vss list shadows” for errors
  • restart the sqlwriter service
  • remove the AAP function from the job and relaunch job
  • restart VBR server
  • try recreating a new job

please report the fix from support
Thanks

Hello everyone,

Following a Webex session with support, a patch was applied to the Veeam server. The jobs are now running successfully.

Case #07676207

Thanks all for the help! 

Here is the recap sent by support:
 

The patch applied: https://storage2.veeam.com/v1/support?name=Fix_870050_41ce8a8a9d.zip


Please note: Before applying this patch, I recommend opening a support case first.

Veeam usually strongly discourages using private fix patches. Like you said, they really should be opening a case first before trying a patch that might not fit them.

I’m not sure if they also frown on sharing private fixes with others as well.

Comment


Terms & Conditions