Access Control Policy apply failed (Not a HASH reference)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2017 05:11 AM - edited 03-12-2019 06:17 AM
Hi Everyone,
Got this 5516_X with Firepower in a box. Firepower is being managed in ASDM. Firepower Software Version 5.4.1.1
Would like to know if you've encountered this error "Access Control Policy apply failed (Not a HASH reference)" when applying the control policy.
What are the possible solutions to solved this problem?
Thanks,
JakeOrthicon
- Labels:
-
NGIPS

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2017 12:28 PM
I have not encountered that error yet.
I would recommend you to make a new Access Control Policy and try to deploy that one. :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2017 12:54 AM
Hi Dennisperto,
I already made a new access control policy and even tried applying the default policy but still didn't work(same error as above) :(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2017 12:57 AM
The correct solution is to contact Cisco TAC.
The fastest solution is to reinstall the Firepower software. This is my recommendation :)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 12:11 PM
There could be multiple reasons. The best way to handle this is to reach out to TAC, if you don't want/you can't reimage.
But if it's a fresh deployment, reimage the device as there could be bad installations from the manufacturer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2017 06:36 PM
Resolved this by upgrading the software. Ty.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2017 12:41 AM
Anyone encountered this kind of error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2017 12:47 AM
Probalby. But they contacted Cisco TAC :)
