Cannot revoke policy

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 3
Commentaires: 2

Hi, has anyone run into this error message below? I removed the server and recreated the backup policy and redeployed but still getting this error message. Please shed some light.

Thanks

Cannot revoke the policy because it was not deployed to the machine.
Additional info:
--------------------
Error code: 35
Module: 164
LineInfo: 3ae4b65385bd39aa
Fields:
Message: Cannot revoke the policy because it was not deployed to the machine.
--------------------

jeu 29/07/2010 - 16:11
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Contributions: 88
Commentaires: 4769

Hello Chio Phanh,

Thank you for bringing up this issue, I will do my best to assist you.

There can be several causes for this problem. Either the deployment/revoking did not complete or the SQL server responsible for these operations is taking some time to process these actions.

The best way to get this resolved would be to contact our Support team with this report, I am confident that we can get this fixed.

Please let me know if you have any other questions.

Thank you.

lun 02/08/2010 - 08:27
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 0
Commentaires: 1

Remove the machine from the mgmt server then add it back in and reapply any applicable polcies. This works even if its the mgmt server that is generating the errors.

jeu 20/01/2011 - 23:49
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 4
Commentaires: 8

So the machine that is generating the error is my situation is the management server.

Are you saying:
- Remove that machine form the AMS
- Delete the policy
- Re-add the machine to AMS
- Make a new policy and assign the the machine?

mer 28/09/2011 - 18:30
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Contributions: 159
Commentaires: 518

Hi Larry

Generally if something has gone wrong like this all that is required is to remove the agent from the AMS then re-add it... when you remove the agent it should also remove any associated policies from both the agent and AMS (this basically cleans things up)... you should find even your old backup policy will then be able to be re-assigned back to the agent once it's been re-added to AMS.

I would also suggest ensuring you have the latest build of ABR installed on your server as it seems the newer builds have better checks in place for when things might go wrong, I have not had many customers report this kind of issue for a while now so though it might be best checking the build you are running as an upgrade might be beneficial.

jeu 29/09/2011 - 01:06
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 4
Commentaires: 8

Not to be dense here,but I actually need to un-install the actual agent form the AMS server - please see attachment with screen shot? So I would select the 'Uninstall Acronis Backup & Recovery 10' ?

This will only uninstall the backup agent and not the whole Acronis product??

And thanks for the reply so soon.

Fichier attaché Taille
78494-97507.jpg 86.61 Ko
jeu 29/09/2011 - 11:49
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Contributions: 159
Commentaires: 518

Hi Larry..

Sorry for the confusion, you should not have to uninstall the agent but simply remove it out of the AMS (Acronis Management Server)...

Here are the steps that should hopefully fix this issue you have run into:
- Load up the ABR10 management console then connect to your management server
- Expand 'Physical machines' (left side of the console) then select ' All physical machines
- Right click on your machine name that is having the issues (right/middle of the window) and select "Delete machine from AMS"
- Once done, Right click on 'All physical machines' and select "Add a machine to AMS"
- Re-Add the machine back into your AMS and apply the required backup policy as usual

When you remove a machine from the management server all that agents centralised policies should be removed from that agent as well, so when you re-add it to the AMS server it should not have any centralised policies and you should not be able to apply the required policy to this agent.

Please let us know how you go.

jeu 29/09/2011 - 23:19
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Contributions: 159
Commentaires: 518

Hi Larry

Thanks for letting us know that fixed up the issue’s... All the best!

lun 03/10/2011 - 05:39