On the gateway (not SMS) where the policy load is failing, try this command to find any non-ASCII characters in the compiled policy located on the gateway, it will highlight the offending characters if there are any:

All that means is that you don't have any non-ASCII characters in your compiled policy which can be one of the many causes of this issue. TAC will need to run a debug of the policy installation on the gateway to determine what problematic element of the compiled policy is aborting the load into the kernel.

We had this problem plague us after upgrading our MGMT to 80.10. Came to find out it was the strings dictionary table filling up. For us at least that was the issue. I think that somehow things got horked up with the upgrade and the entries were no longer lining up. I would check that and see if it is your problem.