Hi Community,
I’m facing an issue where Veeam ONE Reporting Service (VeeamRSS.exe) cannot communicate with Veeam ONE Monitoring Service (VeeamDCS.exe).
The error message states:
The Monitoring service appears to be stopped or inaccessible. Has anyone encountered this before?
Any insights or best practices to resolve this would be greatly appreciated. Kindly note that support case already been open for this.
Start by clearing the event logs and reboot the server. Then you can see fresh logs that might show the issue. Have you tried to manually start the services that are not properly started to see what errors come up? How long has it been happening? Could it be a Windows patch that caused the breakage? Did you check to see if any patches for VEEAM are available? Are they all applied?
Start by clearing the event logs and reboot the server. Then you can see fresh logs that might show the issue. Have you tried to manually start the services that are not properly started to see what errors come up? How long has it been happening? Could it be a Windows patch that caused the breakage? Did you check to see if any patches for VEEAM are available? Are they all applied?
this cause while checking DB connection towards the Veeam One Reporting server. but i will follow that you mentioned start by clearing the event logs
What version of VONE are you using would also be helpful? If v12 maybe try updating to v13? I have seen this before many times and it can be a variety of things. Let support assist to see what the cause is.
Hi
Currently application version is 12, and I tried to upgrade to version 13, but it failed during the upgrade. I checked the error logs did not find anything. What happened after the failed error application was not upgraded, but its database was upgraded to version 13. I think so, that's why this error comes, and right now I'm not able to connect to the DB as well because of a version compatibility issue with the DB
Hi
Currently application version is 12, and I tried to upgrade to version 13, but it failed during the upgrade. I checked the error logs did not find anything. What happened after the failed error application was not upgraded, but its database was upgraded to version 13. I think so, that's why this error comes, and right now I'm not able to connect to the DB as well because of a version compatibility issue with the DB
Then support will help with this and get it sorted. I would suggest staying on that path.
That is the problem. you upgraded the database to 13 and the version is still 12. Did you take a snapshot before the upgrade to revert back to? Do you have a previous backup that you can reinstall to v12 and restore the database from? I always take a snapshot before upgrading.
That is the problem. you upgraded the database to 13 and the version is still 12. Did you take a snapshot before the upgrade to revert back to? Do you have a previous backup that you can reinstall to v12 and restore the database from? I always take a snapshot before upgrading.
Yes, I have a lot of old restore points, and yesterday, support was with me during the session, and we performed a restore using the old restore point to restore the VM. Still, again, it took a new DB version instead of the old DB version. He said I have escalated this case to the next tier of team, and logs have already been sent to support and are waiting for the response.
Hi,
do you have all-in-one? or do you have spread VeeamOne solution across few VMs?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
