2023.1.x upgrade issue for random users - "There is an unclosed literal string. Line xxx, position xx"

[cmulford (Chris Mulford)]

We recently upgraded to 2023.1.10 (cloud flex 2) and have several users that get this error when launching various apps. Has anyone run across this one? We have had no luck with support.
We reported it on one user while testing Pilot but they want blame windows and the suggested we re-image the PC.

Now we have several in live. The transactions compete but they must refresh after the error is acknowledged. We can use that users Epicor credentials on another PC and the error still occurs.

Things we’ve tried with no effect.
-Clear cache, Program Data folder and AppData folder.
-Removed all personalization’s.
-Uninstall and re-install the client.
-Gave the user a new windows profile.

Full error…
" ## System Information ##

AppServer Connection: https://xxxxx.epicorsaas.com/xxxxx
Form Name: Customer Shipment Entry
Customization Name:
Menu ID: SRGO0001
Software Version: 11.2.300.0

============

Application Error

Exception caught in: System.Xml

Error Detail

============
##!Message:##! There is an unclosed literal string. Line 159, position 87.
##!Program:##! System.Xml.dll
##!Method:##! Throw

Client Stack Trace

==================
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r)
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.ReadElementFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Parse(String text, LoadOptions options)
at Ice.Cloud.ProxyBase1.SetResponseHeaders(HttpResponseHeaders httpResponseHeaders) at Ice.Cloud.ProxyBase1.HandleContractAfterCall(HttpResponseHeaders httpResponseHeaders)
at Ice.Cloud.ProxyBase1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy) at Ice.Cloud.ProxyBase1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
at Erp.Proxy.BO.CustShipImpl.UpdateMaster(CustShipDataSet ds, Boolean doValidateCreditHold, Boolean doCheckShipDtl, Boolean doLotValidation, Boolean doCheckOrderComplete, Boolean doPostUpdate, Boolean doCheckCompliance, Boolean ipShippedFlagChanged, Int32 ipPackNum, Int32 ipBTCustNum, String& opReleaseMessage, String& opCompleteMessage, String& opShippingMessage, String& opLotMessage, String& opInventoryMessage, String& opLockQtyMessage, String& opAllocationMessage, String& opPartListNeedsAttr, String& opLotListNeedsAttr, String& shipCreditMsg, Boolean& cError, Boolean& compError, String& msg, String& opPostUpdMessage, Boolean& updateComplete, Boolean& checkComplianceError, Boolean& changeStatusError, Boolean& checkShipDtlAgain)
at Erp.Adapters.CustShipAdapter.UpdateMaster(Boolean doValidateCreditHold, Boolean doCheckShipDtl, Boolean doLotValidation, Boolean doCheckOrderComplete, Boolean doPostUpdate, Boolean doCheckCompliance, Boolean ipShippedFlagChanged, Int32 ipPackNum, Int32 ipBTCustNum, String& opReleaseMessage, String& opCompleteMessage, String& opShippingMessage, String& opLotMessage, String& opInventoryMessage, String& opLockQtyMessage, String& opAllocationMessage, String& opPartListNeedsAttr, String& opLotListNeedsAttr, String& shipCreditMsg, Boolean& cError, Boolean& compError, String& msg, String& opPostUpdMessage, Boolean& updateComplete, Boolean& checkComplianceError, Boolean& changeStatusError, Boolean& checkShipDtlAgain)
at Erp.UI.App.CustShipEntry.Transaction.Update()

[klincecum (Kevin Lincecum)]

Do you have any BPMs on CustShip → UpdateMaster ?

[cmulford (Chris Mulford)]

Yes but still occurs when BPM disabled. It’s not just CustShip. It’s happening on various seemingly random menu items for different users. Some examples like Quick Job entry, Eng workbench, create order from quote, etc. Same error for all but the line/position numbers change.

Here is one from quote entry.

[klincecum (Kevin Lincecum)]

@cmulford

It’s not just CustShip. It’s happening on various seemingly random menu items for different users.

Sorry…

[Olga (Olga Klimova)]

How does Trace Option Form look like in your client?

[cmulford (Chris Mulford)]

Not enabled and blank in all but the EO browser path and Current Log file path. Nothing the XML logging box.

[Olga (Olga Klimova)]

and yet you have caller trace enabled somewhere.
What about User Account Maintanance UI, Tracing tab?

[jkane (John Kane)]

Is this only happening in Client?

[cmulford (Chris Mulford)]

No tracing set in userfile.

Only in client. (We are a a long way from getting our customs to a browser) I might have one to try though, going to get with that user.

[jkane (John Kane)]

I have seen this happen a lot in our Pilot environment but only in the Client. I have not looked into it or reported it because it is Pilot. I’ve wondered if it is due to a change in the Web UI that is not in the Client UI.

I’m interested to see where this goes…

[Olga (Olga Klimova)]

what about serverTraceFlagsSettings node in the client sysconfig?

[cmulford (Chris Mulford)]

I had reported it in Pilot and it rolled right into Production.

[cmulford (Chris Mulford)]

We’ve uninstalled, deleted the c:\Epicor folder and installed a new client from download epicorsaas. It is the default client config.

[cmulford (Chris Mulford)]

It did not occur in browser. This user has it occur when printing Production Detail from the client.

[cmulford (Chris Mulford)]

Olga was on the right track for this one. Turns out the issue was with the classic user tracing options. Even if the enable trace logging is set to false the errors would occur if the server trace dataset option was set true. Being greyed out was not enough. You have to enable trace logging in order to mark the dataset options as false and then disable the trace logging. As soon as I did this and verified that all the dataset options were not checked, the errors no longer occur for that user.

[gpayne (Greg Payne)]

@cmulford Thanks for this post. I was testing an OnPrem dev system to 23.2 this weekend and it appeared that a bunch of my bpms were broken,. I was getting a lot of system xml errors. like Unexpected end of file while parsing Name has occurred. I finally changed enough stuff to get this unclosed literal error.

@Olga I had to stop tracing on the app server to get them to stop.

[Olga (Olga Klimova)]

You should report it if you can provide steps to repro it.

[gpayne (Greg Payne)]

To prove it out, I disabled all bpms in the host.config and did delete all and then get details with tracing which ran without issue. Then I reenabled all bpms and ran delete all and get details and there was not an error. Grrrr

[gpayne (Greg Payne)]

I dug a little more today and found the issue only happens with bpm tracing on not debug or baq, so I will report the issue.

Except for not seeing the execution time of the bpm I think I like just debug since I can see all of the Event log write entries much clearer.

[gpayne (Greg Payne)]

CS0004019691 created. I did find with another routine that throws the unclosed literal string, but it has over 1000 lines it adds to the ServerLog file.