Activation not possible when NOTICE filed is not UTF8
SummaryThis article will explain if the NOTICE field is not in UTF 8 format activation will fail.
SynopsisIs there a way to accept an activation even if the NOTICE field is not in correct value of UTF 8?
When activating using wrong UTF 8 value it fails with an error message:
appcomptranutil.exe -p xxx\xxxx\xxxx\responseXML.xml
ERROR: API function 60009 failed, result 51306
First (or only) signature invalid
Response processing failed.
The response XML supplied is not a valid composite response.
Exit(4) error when processing response.
- Activation request and request xmls are encoded in UTF -8. [<?xml version="1.0" encoding="UTF-8"?>]
- Supporting non UTF-8 character encoding with in UTF-8 encoded XML is not possible.