Skip to main content
Question

Veeam Service Provider - Windows Agent job suddenly are failing

  • August 11, 2025
  • 5 comments
  • 288 views

  • Comes here often

Hi All,

We have the Veeam Service Provider Console 8.1 installed and it is generally working fine, but suddenly on many job for Windows Agents, operation mode Workstation, we see this error message.

 

Error: Cannot set many inner exceptions to exception System.Exception

 

VSPC and VBR is installed on the same VM. As a first step we upgraded VBR to the latest version. Windows Agent Version are on 6.3

Any hint is highly appreciated.

Thanks,

Edy

 

 

5 comments

MarkBoothman
Forum|alt.badge.img+7
  • Influencer
  • August 11, 2025

What database is your VSPC instance running under. Have you check the event logs and veeeam logs in %program data%\veeam

 

It sounds like a DB type issue and I would check if it’s SQL express its not hit the limit.

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • August 11, 2025

What is the target for the Veeam Agent backups?  You mention VSPC but that is more a management tool than target.  Is it local storage, VBR repo, Cloud Connect repo?  Check the DB as Mark said but also more details would be helpful.


waqasali
Forum|alt.badge.img+4
  • On the path to Greatness
  • August 12, 2025

Hi ​@Edy 

 

This issue may be related to compatibility between VSPC 8.1 and Windows Agent 6.3.

 

Try updating both VSPC and Veeam Agent to the latest available builds. Also, check if VSPC and VBR running on the same VM is causing resource contention.

 

Moving VBR to a separate VM has helped in similar cases. Review logs for deeper insight and consider restarting VSPC services after updates.


  • New Here
  • August 18, 2025

Hello,

I have an environment experiencing the same error, where some Hyper-V VBR backup jobs targeting Cloud Connect are failing with the error: "Error: Cannot set many inner exceptions to exception System.Exception."

Details: The VBR version is 12.2, VSPC is 8.1, and Cloud Connect is 12.3.1. Could there be an issue related to this version combination? Or could it be a different error altogether?


  • Author
  • Comes here often
  • August 19, 2025

Hi - sorry for not getting back. We resolved, we contacted support and submitted the log of the Windows Agent.

 

[12.08.2025 11:49:26.626]   <110>   Error (3)    Failed to set integrity stream to True for storage 'TI-Backup_Atlas12025-08-12T114857.vbk:8d153cb8-d7e4-4570-aa7c-5acc3cf2cd3d:12.08.2025 11:48:57:12.08.2025 11:48:57'.
[12.08.2025 11:49:26.626]   <110>   Error (3)    Incorrect function.
[12.08.2025 11:49:26.626]   <110>   Error (3)    Agent failed to process method {ReFs.SetFileIntegrity}.
[12.08.2025 11:49:26.626]   <110>   Error (3)     (System.AggregateException)
[12.08.2025 11:49:26.626]   <110>   Error (3)    Incorrect function. (Veeam.Backup.Common.CCppComponentException)
[12.08.2025 11:49:26.626]   <110>   Error (3)       in c++: Error code: 0x00000001
[12.08.2025 11:49:26.626]   <110>   Error (3)       in c++: Failed to set file integrity attribute true
[12.08.2025 11:49:26.626]   <110>   Error (3)       in c++: Failed to set integrity stream for 
[12.08.2025 11:49:26.626]   <110>   Error (3)    Agent failed to process method {ReFs.SetFileIntegrity}. (Veeam.Backup.Common.CCppComponentException)

 

The solution is not noted in this KB https://www.veeam.com/kb4381