Unable to save HIPS DNS policy

[rbenson09]

When trying to add a domain and save the HIPS DNS Blocking policy, we get a prompt that says "10.x.x.x says Unable to save policy". We were able to save just fine yesterday. We tried duplicating the policy but get the same error.

[AdithyanT · Accepted solution]

Hi @rbenson09,

Thank you for your post. Usually these errors are backed by more information present in the orion.log present in c:\Program Files\McAfee\ePolicy Orchestrator\Server\Logs. by default.

I have a KBA for your to look into in case you have not already seen them. Please let me know if this is of any use here:

https://kc.mcafee.com/corporate/index?page=content&id=KB90983&locale=en_US

I sincerely hope this helps!

[YashT]

Hello @rbenson09 ,

When migrating Host IPS 7.0 policies to Host IPS 8.0, the ePO server might display the following error:

Unable to Save Policy

Cause
This error occurs with any Host IPS 7.0 policies that exceed a total of 2 MB in size.

The entire policy is sent as JSON data between the browser and the ePO server during the policy migration operation. The ePO server Tomcat service is configured to limit POST data to a maximum of 2 MB.

This can be found in : 
Unable to Save Policy (when migrating Host Intrusion Prevention 7.0 policies to 8.0 in ePolicy Orchestrator)
Technical Articles ID: KB77154

Also another reason for the policy not getting saved is due to collation mismatch.

ePO 5.x supports all Microsoft SQL Server collations using the following two SQL collation properties:
Case Insensitivity (CI)
Full ASCII character set support - This set is included in all Unicode-based character sets.
If your SQL Server uses SQL collation that meets the above criteria, it is supported.

NOTES:
The SQL collation of the SQL Server must match the collation of the ePO database.
ePO is primarily tested with SQL_Latin1_General_CP1_CI_AS, which is the default for English United States. Test striping is performed against some of the default SQL collations for non-English languages.

You will find this in : KB73717.