XConfParseMem: Unable to Parse an In-Memory XML Document When Trying to Set 552_PERMANENT_ERROR_STRING in Unified Config
(Doc ID 2324189.1)
Last updated on MARCH 14, 2019
Applies to:
Oracle Communications Messaging Server - Version 7.0.5 and laterInformation in this document applies to any platform.
Goal
Why when trying to set 552_PERMANENT_ERROR_STRING in unified config:
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |