SAX parser errors in services-messages.log

I'm having some issues with a just installed ZCM 11.3a server. I'm getting a lot of errors:
org.jdom.JDOMException: Could not load default SAX parser: org.apache.xerces.parsers.SAXParser: SAX2 driver class org.apache.xerces.parsers.SAXParser not found: org.apache.xerces.parsers.SAXParser
in services-messages.log
I have googled for the error message but can't find anything related to ZCM. Any idea about how to fix it?

jlmendez Wrote in message:
> I'm having some issues with a just installed ZCM 11.3a server. I'm
> getting a lot of errors:
>
> org.jdom.JDOMException: Could not load default SAX parser:
> org.apache.xerces.parsers.SAXParser: SAX2 driver class
> org.apache.xerces.parsers.SAXParser not found:
> org.apache.xerces.parsers.SAXParser
>
> in services-messages.log
>
> I have googled for the error message but can't find anything related to
> ZCM. Any idea about how to fix it?
Which OS did you install ZCM 11.3a on? I'm guessing Linux based.
HTH.
Simon Flood
Novell Knowledge Partner

Similar Messages

Error processing request in sax parser: Error when executing statement...

Hello,
I want to INSERT data from R/3 System to AS400 via JDBC adapter into a DB2 database. The interfaces from R/3 are Ok. but i have some problems to use the JDBC in DB2 Systems. The message in comunitation channel is:
" Error processing request in sax parser: Error when executing statement for table/stored proc. 'SPE106TST' (structure 'STATEMENT'): java.sql.SQLException: SPE106TST de SADMT1 no válido para la operación."
in the SXMB_MONI -> Request Message Mapping payloads this:
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Please Can anyone help me solve this problem? I'm lost.
Best regards,
Edited by: Nicola Occhipinti on May 22, 2008 7:40 PM

Hi Nicola,
This error occurs when the receiver side structure is incorrect.
Your structure seems to be correct.
Please use lower case for action, access and table.
Please check whether the field names are exactly the same as in the actual Database table sadmt1.SPE106TST.
Check if the table has permissions to write.
You can try an alternate structure without using table tag.
<ns0:MT_XMLSQL_SPEC xmlns:ns0="urn:damm.com/pi/EmployeeMasterData">
<STATEMENT>
<sadmt1.SPE106TST action="INSERT">
<access>
<CODEMP>D</CODEMP>
<CODPRO>00202339</CODPRO>
<NOMPRO>ROSIQUE PERALSGENIS</NOMPRO>
<DIRPRO>GIRONA</DIRPRO>
<POBPRO>S. VICENS HORTS</POBPRO>
<RUTA>0</RUTA>
<ORDEN>0</ORDEN>
<NOMINA>S</NOMINA>
</access>
</sadmt1.SPE106TST>
</STATEMENT>
</ns0:MT_XMLSQL_SPEC>
Hope your problem gets solved.
-Shamly

Email receiver qpac-SAX Parsing Error

Hi,
Iam working on a project which needs to receive email from an
external person and the workflow will continue from that point.
>>I have put a email receiver qpac to accomplish the
above task. I use the sender's(from) email address as a
filter for incoming mails and the starting 4 letters of the form
name to fetch the XDP attachment. The process works just fine
when tested by sending a mail from Outlook express. But, in
the case of Lotus Notes, the click of email submit button in
the form opens up a new mail with the XDP Data file as
attachment and names it weirdly with some numbers unlike
outlook express client where in the attachment gets named as
the form name "_data.xdp".
Thus, my email receiver does not pick
this email and the process gets stalled giving some SAX
parser error. Is there any way to customise form/ lotus notes
clients to make it work?
Regards,
Raghava Kumar VSS

Hi Raghava
Just drop the 4 starting letters, and look for the first attachment.
There should only ever be 1 attachment, so you shouldn't have a problem.
Howard
http://www.avoka.com

OBIEE Sax Parser Error in Firefox only?

I was working on a report in Answers and came across the following error when trying to "Display" the results
Sax parser returned an exception. Message: An exception occurred! Type:UnexpectedEOFException, Message:The end of input was not expected, Entity publicId: , Entity systemId: , Line number: 1, Column number: 1862
The report, when viewed on a dashboard works perfectly fine, its ONLY when I try to "Display" the results in Answers I hit the above error.
The interesting thing also is that I tried Internet Explorer, Google Chrome and Firefox
ONLY Firefox is throwing this error.
I am using the latest version of Firefox (ver 22)
OBIEE is version 10.1.3.4.0
Again, everything with the report works just great its just when I try to display the results in answers that it throws an error.

I think my issue just got worse
Now when I log into Answers and try to view the report I see the following error
State: HY000. Code: 1736874543. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 27005] Unresolved column
The biggest issue I am noticing now is that my column names are actually changing!
So when I first log into the report in Answers I see the columns being used are
Type Animal
Type Tree
I click on "Display Results" which yields the above error
Now when I click back to the columns view, the column names have changed to the following
Adjusted Animal = Type
High Yield Tree = Type
The column names have totally changed
I am now guessing there may be an error some where in the RPD, between the physical/presentation and business model layer.
Any insight would be greatly appreciated!

SAX Parser Error in JDBC Adapter

I am using a JDBC adapter to execute SQL statements during mapping runtime. However, it issues me an error regarding the SAX Parser when I have a '&' character in the SQL statement. I am not able to remove the & since it is in the database that I access and it will result to data inconsistency. I think that when the JDBC adapter of XI converts the SQL string to the XML format, it does not include the amp; string to the &, thus causing the SAX Parser to throw the error.
Is there someway I can configure the JDBC adapter in such a way that it will replace the & with &. Or is there a way to display how the JDBC adapter converts the SQL statement to its the XML representation of it?
Thanks a lot.

Hi,
For this kind of situation use some unique character combination like "#@!" for replacing "&" then parse the document and the restore the "&" later .
For this convert the input stream into Strring and then replace the occurences of "&".
regards.

SAX Parser error when installing Oracle CCG 5.5.1

I am trying to install Oracle CCG on Windows 2008. I already have my PeopleSoft system installed on the same box, running weblogic and jdk1.7.0_03.
After setting the required environment variables, when I run the command "install.bat -f ccg-551-install.apf" from ccg_install folder, I get the following error:
Starting Oracle Installation Engine 1.2.1
Running from working directory C:\CCG\ccg_stage\
ORACLE_HOME is C:\app\Administrator\product\11.2.0\dbhome_1
JAVA_HOME is C:\Program Files\Java\jdk1.7.0_03
LAUNCH_CLASSPATH is C:\app\Administrator\product\11.2.0\dbhome_1\jdbc\lib\classe
s12.jar;C:\CCG\ccg_stage\install.jar;"C:\app\Administrator\product\11.2.0\dbhome
_1\lib";C:\Program Files\Java\jdk1.7.0_03\lib;C:\app\Administrator\product\11.2.
0\dbhome_1\lib;%CLASSPATH%
Oracle CCG Installer -- Version 1.2.1 Build(installer12-Maint-1.2.1.2)
Copyright 2009 Oracle. All rights reserved.
Initializing. Please wait...
FileParser: Parse error occurred: Could not load default SAX parser: org.apache.
xerces.parsers.SAXParser: SAX2 driver class org.apache.xerces.parsers.SAXParser
not found: org.apache.xerces.parsers.SAXParser
Could not load default SAX parser: org.apache.xerces.parsers.SAXParser: SAX2 dri
ver class org.apache.xerces.parsers.SAXParser not found: org.apache.xerces.parse
rs.SAXParser
I have tried downloading xerces.jar file and placed in the CLASSPATH folder but it did not help either. I do not have much knowledge about java and need help from someone who has installed CCG on windows.
Thank you in advance

Several things I would recommend here:
1. Use JDK 1.5 instead of 1.7, I'm pretty sure 1.7 isn't supported (Don't ask why) - [http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html|http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html]
2. Make sure to exit out all DOS command windows, then open a new one then go through setting all the environment variables, and using the same DOS command run the install command, otherwise all environment variables will be lost.
I hope that helps.

Plist parsing error when trying to log into iTunes Store

Can't log into App Store on my iPhone 5S, when trying to access my account on my MacBook I get "plist parsing error". Pls help.

Apple’s having trouble with the iTunes Store servers right now. Wait for them to resolve the issue.
(123891)

Error on Service message

Hi Guys,
For a newly created service message, there is an error message for it and it's saying "Organization not available".
I have alraedy checked the STP's Sales data area, and tried to re-populate the info and save again. But the error is still persist in the service message.
Could you pls comment on what else i need to check?
Thanks in advance.

Hi ,
I assume you have maintained your organizational model in tcode ppoma_crm?
Maybe you can check your customizing transaction for the org.determination profile is maintained or not. This is required to determine the serv.org and sales org.
regards,
anthony

Parsing error in file message, can't access Solution Center

I have a HP Deskjet F4480. From initial install I get a message: Parsing error in file C:\Program files\HP\Digital Imaging\bin\hpqsdoc\1033.XML I have uninstalled the printer, downloaded the large install file from HP website and tried to install printer. Still get same error message. Printer prints, copies fine but I want to use it to scan a page and then using OCR copy data. Scanner feature from control panel will copy just fine but don't know how to get to .txt from scanned image, or how to get rid of error message. Have already run the printer diagnostic unit and scanner diagnostic unit and they detect no errors.

navigate to C:\program files\HP\digital imaging\bin\ and there we would find 2 or 3 folders with HPQSCLOC name with an extension like HPQSCLOC(608) or (109).
We have to search for 1033.xml file in all those folders and probably, it would be there in HPQSCLOC folder with numbers in brackets.
Then, we can go to the HPQSCLOC folder and copy the contents of the folder and paste the contents in HPQSCLOC folder with numbers in brackets .
Now, we can delete the HPQSCLOC folder and rename the HPQSCLOC folder with numbers in brackets as HPQSCLOC.
Then, try opening HP Solution center. It should work fine
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"
(Although I am employed by HP, I am speaking for myself and not for HP)

SAX parser error unknownHostException for JDO files

Hi everyone,
The java.sun.com site is down (or perhaps only unreachable from Maine Road Runner) today. If your
JDO file uses a DOCTYPE statement that references the site, and you see this error, that's the
reason.
David Ezzio

Just FYI, Kodo validates .jdo files aginst the metadata DTD even if you
don't include a DOCTYPE declaration. We do a neat trick where the full
DOCTYPE with inline DTD is included in the stream we send to the parser
transparently. Actually you can have this functionality in your own XML
code if you want; it's available via our open source Serp project:
http://serp.sourceforge.net
(see serp.xml.DocTypeReader)
If you hate having to code DOCTYPEs to use a URL (which can go down), a
file location (which places location dependencies in your code), or repeat
the same inline DTD in all your XML files, you should check it out.

Error processing request in sax parser

Hi all,
I am doing an asynchronous interface.
It is an interface from IDOC to JDBC. While testing the interface,am getting the following error
"Error processing request in sax parser: Error when executing statement for table/stored proc. 'put_delivery' (structure 'Statement_Delivery'): java.lang.NumberFormatException: null"
Any kind of help is appreciated.
Regards,
Thireesha.

Hello,
Please refer to SAP NOTE 801367.
In advanced tab, use logSQLQuery-->true. Tt will display the actual sql statement in audit log instead of xml format.
You can copy this sql statement and execute directly in database to check the problem.
-Rahul

Error processing request in sax parser...Excepciu00F3n de E/S: Connection reset

Hello,
I've RFC to JDBC interface.
Sometimes in the RWB me the following error message,
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'LISMATWQ' (structure 'STATEMENT'): java.sql.SQLException: Excepción de E/S: Connection reset</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
How can I prevent?
Thanks very much,

Hello,
the error does not always appear, sometimes the interface works well and others do not (even when the data are the same) I find no solution to this error,
anyone have any idea?
thanks very much

Troubleshoot-Adapter engine:Error Setting the message status to DLNG failed

Dear Experts,
We use SAP RFC- PI-JDBC(MSSQL). here the Data(message) successfully transfered to mssql table but the status is been set to DLNG failed, And it finally shown as SYSTEM ERROR.
QoS required: ExactlyOnce , here The Message has got inserted in that particular table and in PI adapter the status turned to DLNG faild and the service again tries to send the same message which is not possible becoz the data is set for primary value.
2010-09-15 09:59:48 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX:50000/MessagingSystem/receive/AFW/XI Credential (User): YYYY
2010-09-15 09:59:48 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-09-15 09:59:48 Success Message successfully put into the queue.
2010-09-15 09:59:48 Success The message was successfully retrieved from the receive queue.
2010-09-15 09:59:48 Error Setting the message status to TBDL failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
2010-09-15 09:59:48 Success Delivering to channel: CCR_JDBC_ZZZZZ
2010-09-15 09:59:48 Success MP: Entering module processor
2010-09-15 09:59:48 Success MP: Processing local module localejbs/CallSapAdapter
2010-09-15 09:59:48 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2010-09-15 09:59:48 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ
2010-09-15 09:59:49 Success Database request processed successfully
2010-09-15 09:59:49 Success MP: Leaving module processor
2010-09-15 09:59:49 Success The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.
2010-09-15 09:59:49 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
2010-09-15 10:37:01 Success The message was successfully retrieved from the receive queue.
2010-09-15 10:37:01 Success The message status set to DLNG.
2010-09-15 10:37:01 Success Delivering to channel: CCR_JDBC_ZZZZZ
2010-09-15 10:37:01 Success MP: Entering module processor
2010-09-15 10:37:01 Success MP: Processing local module localejbs/CallSapAdapter
2010-09-15 10:37:01 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2010-09-15 10:37:01 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ
2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
Thanks in advance for your valuable answer.

Hi Vinaygam,
2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
See above error, It cannot the Duplicate Key in your log table. Duplicate means repeated as a same data.So kindly check once your data.
IF,I assume your scenario is Synchronous, If you are using any sender JDBC adapter just check with your Quality of Service and set it to "Exactly once".
so kindly do it.
Thank you,
Sateesh
Edited by: sateesh kumar .N on Sep 17, 2010 8:17 AM

XML parsing error, whitespace expected

I'm seeing this "XML parsing" error in the SSRS Logs once in a while and I don't know what is causing it. The weird thing is that the report doesn't get this error everytime, most of the time it will work. I originally thought that
it might be the data that is being returned but I don't know if this is the case. Usually when a user gets an error, they'll just run it again later and it'll work the 2nd time. I looked at the report parameters in the ExecutionLogStorage table and the same
parameters are passed in each time.
Does anyone have any ideas of where I can look to get to the bottom of this one? Any help is appreciated.
The actual error from the logs is below:
processing!ReportServer_0-26!fdc!05/08/2014-13:33:12:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSet1'. ---> System.Data.SqlClient.SqlException: XML parsing: line 1, character 121, whitespace expected
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.DataExtensions.SqlCommandWrapperExtension.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
Thanks,
-Song

Hi Song,
Sorry for the delay.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SAX error in xsd parsing (was: Application only returns "Log is disabled.")

Ok, it seems the underlying error of the "Log is disabled" is with parsing xml. I paste in the relevant bits of the console output of Weblogic 10.3.2.0 below (slightly modified the URL). I made a small testcase in Eclipse reading the same xsd from the same URL with SAX (same JDK as using in weblogic) and it works there. Has anybody an idea? I thought it might be a conflict with SAX versions or so, but couldn't find anything.
Thanks,
Stefan
java.lang.Exception: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://ip/data/blah/V100/other.xsd'.: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.load(AbstractDefinitionContext.java:157)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.load(AbstractDefinitionContext.java:115)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.loadIfNecessary(AbstractDefinitionContext.java:91)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.<init>(WsdlMockRunner.java:94)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockService.start(WsdlMockService.java:206)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockService.start(WsdlMockService.java:492)
at com.eviware.soapui.impl.wsdl.mock.WsdlMockService.start(WsdlMockService.java:67)
at com.eviware.soapui.mockaswar.MockAsWarServlet.init(MockAsWarServlet.java:82)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/schema/xs:schema): faultCode=PARSER_ERROR: Problem parsing 'http://ip/data/blah/V100/other.xsd'.: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlInterfaceDefinition.load(WsdlInterfaceDefinition.java:48)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:66)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinition(WsdlContext.java:30)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.cacheDefinition(AbstractDefinitionContext.java:264)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext.access$400(AbstractDefinitionContext.java:44)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:230)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:140)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1411)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.nex(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
... 20 more
Edited by: user13782455 on 19.01.2011 05:03

earlier it was
org.xml.sax.SAXParseException: s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'USAVER'.anmd now it is
org.xml.sax.SAXParseException: s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'Alert1'.some problem in this Alert1 message is what i guess.. some parsing error.. look closely..
i guess some of the xml characters are not rendered properly in forum software.. or it may be truncated.. so i believe something wrong which is not visible..

SAX parser errors in services-messages.log

Similar Messages

Maybe you are looking for