Cannot access ABR10 Advanced Workstation management server

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 4
Commentaires: 2

Hello,

I have ABR10 Advanced Workstation (Licensing, Console and management server) installed on a Windows Server 2003 R2 SP2 (64-bit) server. It had been running fine for about 6 months but recently I've had issues connecting to the management server.

What happens is when I open up the console and try to connect to the management server, I get a message that says "Cannot connect to xxx. The required service on remote machine not started. Start the service and retry the connection".

When I look at the "Acronis Management Server Service" on the management server, it is stopped. When I restart it, it stops after a short time (20 seconds?) but immediately if I try to access the management server.

I had ABR10 build 10.0.11639 but downloaded the latest and upgraded to 12497 to see if it would resolve the issue. But it did not and I still cannot connect to the management server.

If anyone had similar issues and knows how to fix this issue, I would appreciate it greatly.

Thank you very much for your help.

mer 13/10/2010 - 23:45
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Contributions: 5
Commentaires: 46

Yes, this happened to me.

Check the Managed Machine Service and see what account it is using. This issue is to do with 'logon as a service' in group policies/local policies as upon an upgrade/install the Acronis account changes it's id slightly with a different set of numbers after the name Acronis12341234124 etc. So therefore it can't log on as a service and then ends after so many seconds.

Remove the old references in Active Directory and re-add it with logon as a service right in Group Policies. You will also need to do an gpupdate force.

jeu 14/10/2010 - 08:18