Forum Discussion
commandline_be_
Nimbostratus
Jul 22, 2018ASM Policy fails to import because of schema failure (65535)
Dear,
Foremost question is how to fix this, the policy was exported from an ASM and imports fine on another ASM.
I've setup a Virtualbox Big-IP VE Trial license following the need to resear...
samstep
Cirrocumulus
Aug 03, 2018You have non-ASCII characters in your parameter names, which may cause issues with XML format. Don't try to manually edit the XML file as this is exactly what is causing the "Schemas validity error".
Try exporting the policy as Binary (.plc format) as this is effectively a mySQL backup format which should get restored/imported with no issues.
If you are saying that a colleague is able to import it it might be due to a different version of ASM your colleague is using!
If you still have the problem it is worth raising a Support case with F5 Support.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects