Skip to main content

Maybe this is just me, but has anyone else been having issues with the Management Agent dropping out from reporting to the Service Provider Console? 

It seems like since the upgrade to 8.1 I’ve had a few agents that have started dropping on occasion.  If I attempt to restart the Management Agent service, it times out stopping the service.  If I manually kill Veeam.MBP.Agent.exe and then start the service again it runs fine, connect and start communicating with the console properly again.  This morning I had three agents that I had to do this to and one of them wasn’t reporting point usage to the console for the 1st of the month point recording although after I killed and started the agent manually it did phone home the point utilization. That said, I wasn’t able to approve the company reporting because it had errored out previously so I had to tell it to generate the report and have that process override the approval of the reporting or that company. 

Strangely, I had another company error out even though it did report point usage and it was communicating correctly with the agent as well but it just noted that it failed to approve the usage report and to contact technical support.

It doesn't happen a lot with the agent losing connection, but I swear I’ve had this issue on a couple of different machines over the past couple months and wanted to see if anyone else had experience any similar issues.

Have not had this happen since moving to 8.1.  Had some issues with agents updating but was able to fix that.

Only time for me this sometimes happens is during patching for us but I ensure when that is done a check is in place to ensure the VSPC Agent service is running. 😎


Hello 
I have some VSPC agents with this kind of problem


I have to check with my Support Team to identify the root cause. 


Hello 
I have some VSPC agents with this kind of problem


I have to check with my Support Team to identify the root cause. 

When I see this I check both the VSPC Agent service and also the VBR services to ensure the main Backup Service is running.  Many times it is the backup service not running that can cause this I find.

 
 
 

We have observed exactly this behavior since the update from v8.1.0.21377 to v8.1.0.21999.
Kill Veeam.MBP.Agent.exe and restart service on the customer side fixes the problem for a short time.


We’ve seen similar issues and its usually been WMI on the local machine.


We’ve seen similar issues and its usually been WMI on the local machine.

Is there a workaround to solve the problem in the long term? 


The only solution our team have is to rebuild the WMI repository on the affected machine. I would suggest that in the 1st instance.


Comment