My Oracle Support Banner

MetaSolv Solution Application Hangs on PSR Order and Receives "FWK005 parse may not be called while parsing" Error and Crashes With "Error Number 39" (Doc ID 1053467.1)

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.15 and later
Information in this document applies to any platform.
***** checked for relevance on 02-April-15 ************


On certain accounts, the application hangs after clicking on the product under the Service Location of a PSR order.  The application eventually displays an "xml parser error" and crashes with an "Error Number 39". Below are the errors received in GUI as well as those captured in the application server logs.

Screenshot of "xml parser error" in the application:

Error text
A data-related error occurred. Please use the detail button for more information.

PBPackageError: SAXException - xml parser error
FWK005 parse may not be called while parsing.

Screenshot of "Error Number 39" in the application:

Error text:
Error Number 39.
Error text = Error accessing external object property atn_count.
Window/Menu/Object = w_service_order.
Error Object/Control = w_service_order.
Script = of_set_services_tabpages.
Line in Script = 152.

Error captured in the appserverlog.xml file:

<log4j:event logger="cmm.invFromPB" timestamp="1262967701890" level="ERROR" thread="ExecuteThread: '89' for queue: 'weblogic.kernel.Default'" dateTime="Fri Jan 08 10:21:41 CST 2010" userName="appadmin" moduleName="cmm.invFromPB" appServerName="DEF_APPSERVER" messageID="10122" productName="nur" className="DEF_CLASS" debugCode="0" machineName="XXXXXXX">
<log4j:message><![CDATA[The server encountered the following Error: ]]></log4j:message>
                <log4j:cause><![CDATA[The server encountered the following Error:]]></log4j:cause>
                <log4j:action><![CDATA[The server encountered the following Error:]]></log4j:action>
<log4j:throwable><![CDATA[org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
                at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
                at MetaSolv.utilities.powerbuilder.PBPackage.fromXML(
                at com.mslv.webapp.pblistener.PBListener.getPBPackageFromRequest(
                at com.mslv.webapp.pblistener.PBListener.doPost(
                at javax.servlet.http.HttpServlet.service(
                at javax.servlet.http.HttpServlet.service(
                at weblogic.servlet.internal.ServletStubImpl$
                at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
                at weblogic.servlet.internal.ServletStubImpl.invokeServlet(
                at weblogic.servlet.internal.WebAppServletContext$
                at weblogic.servlet.internal.WebAppServletContext.invokeServlet(
                at weblogic.servlet.internal.ServletRequestImpl.execute(
                at weblogic.kernel.ExecuteThread.execute(

Error captured in the {SERVER}.mss log:

error in parseorg.xml.sax.SAXException: FWK005 parse may not be called while parsing.
The Database Administrator may report the following query as a top consumer of database resources:




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.