Forum Discussion
John_Buchanan
Jan 18, 2016Nimbostratus
Was hoping what you'd mentioned was the key, but this happens even without opening/editing the policy file. I can export from my first ASM pair and immediately attempt to import to my 2nd ASM pair and I receive this error. Is it possible that some unusual character(s) or syntax in one of my named parameters could cause this?
I think I'll try one or two more things and then reach out to F5 directly.