Invalid XML Character Causing ASAP To Stop Processing Work Orders (Doc ID 2213024.1)

Last updated on JANUARY 11, 2017

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Goal

An invalid XML character is causing ASAP to stop processing work orders

We have followed the work-around/fix given in the following KM Notes for CTRL-G and CTRL-C characters.

However, again in production environment, we encountered the same error for CTRL-H character. At this point in time, we have handled that as well. In future, there will be a possibility of other unknown such characters.

We are looking if we could enhance ASAP product so that instead of applying the workaround, such errors should be handled automatically by ASAP.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms