Orders not processing after ME/MII patch upgrade

[Former Member]

Hi Experts,

Orders are not processing after updating the latest  ME/MII patch. We have updated the below ME/MII patches.After that we are getting below error. The orders are failing to process. Could you please throw some light on this.

SAPMECORE 6.1.4.12

SAPMEINT 6.1.4.8

SAPMEINTCTC 6.1.4.2

XMII 14.0.4.5

Error:

Message:			Deprecated scope of type SERVERSESSION_AT_LEAST_ONE_APP_SCOPE is used! Please replace the usage of scopes with new mechanism based on "Cross application session communication API".
Severity:			Info
Date:			2014-04-21
Time:			19:36:32:475
Category:			/System/UserInterface
Location:			com.sap.tc.webdynpro.services.session.SynchronizedScopeMaintainer
Application:			sap.com/tc~lm~itsam~ui~lv~client_ui
Thread:			Thread[HTTP Worker [@1780477457],5,Dedicated_Application_Thread]
Data Source:			j2ee\cluster\server0\log\system\userinterface_00.log

Message:			Error transfering attributes org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
Severity:			Error
Date:			2014-04-21
Time:			18:43:29:825
Category:			com.sap.xmii.Illuminator.gui.homepage.HomePageBuilder
Location:			com.sap.xmii.Illuminator.gui.homepage.HomePageBuilder
Application:			sap.com/xapps~xmii~ear
Thread:			Thread[HTTP Worker [@1639942021],5,Dedicated_Application_Thread]
Data Source:			j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
Passport User Activity ID:			d70f5fc8c9ad11e3b330000000d33042
Message ID:
Session:			7865

Regards,

Bala.

[former_member182330]

Hi Bala,

Probably you need to run MEINT migration CTC wizard as per note 1992119. Have you already done this before/after upgrade? It would be a good habit to check each patch release notes to see if additional actions are required for upgrade.

Regards,
Konstantin

[alexander_teslyuk]

Dear Bala,

There is an error 'An invalid or illegal XML character is specified', so I would recommend to check some failed iDOC if there is some special character.

Also, I saw a case where such error was fixed in MII 14.0 SP3 p1. What ME, MII, MEINT, NW versions do you use?

Br, Alex.