Xml is not well formed and caller ID issues

XML is not well formed happens when i click on links from facebook mobile...links to youtube videos, or any other external links. This used to work before, just started happening out of nowhere.
Also, caller ID doesnt display names from contacts, just the number they are calling from...1-10 calls will show the contact name.
any information would be great, thank you!

Since you have a "BlackBerry Browser" I'm assuming you're on a BES? Have you talked with your IT department? Is the device locked when the caller ID doesn't work? Do you have content protection enabled?
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

Similar Messages

What is a (xml parsing error:not well-formed) and how to fix this

what is a (xml parsing error:not well-formed) and how to fix this
== URL of affected sites ==
http://sudburyfinecars.subarudealer.ca
== Troubleshooting information ==
XML Parsing Error: not well-formed
Location: http://sudburyfinecars.subarudealer.ca/WebPage.aspx?WebSiteID=205
Line Number 258, Column 152:

I found the solution to my own problem by using Internet Explorer instead of Firefox, it turn out that the site i was trying to get into is an old site using proxy servers that Firefox doesn't read properly giving me the XML parsing error:not well-formed.
Its not Firefox's fault its just letting you know that this could be a problem site if it lets you in.

Could not initiate the BPEL process :the input xml is not well formed err

Hi
I am calling a bpel process from the bpel console. It is a syncronous process and just fetches values from the database. I see that when ever i call this for some inputs i get the following error , in the response.
Could not initiate the BPEL process because the input xml is not well formed, the reason is :
Error parsing envelope: (1, 6168) Invalid char in text. Please correct the input xml.
When i see the log i have the following message
fault.collaxa.cube.ws> <AdapterFramework::Outbound> Returning outbound XMLRecord for OutputParameters
Exception: Error parsing envelope: (1, 6168) Invalid char in text.
e.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
e.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
e.ws.saaj.soap.MessageImpl.getSOAPBody(MessageImpl.java:935)
ate__ws._jspService(_ngDoInitiate__ws.java:455)
erver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
.runtimev2.JspPageTable.service(JspPageTable.java:453)
.runtimev2.JspServlet.internalService(JspServlet.java:591)
.runtimev2.JspServlet.service(JspServlet.java:515)
let.http.HttpServlet.service(HttpServlet.java:856)
nd.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
urity.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
ity.AccessController.doPrivileged(Native Method)
rity.auth.Subject.doAsPrivileged(Subject.java:517)
I understand that the error is coming with parsing the output from the database values. Further i see the process is completed successfully when i see the flow and log and the out is present in the output response. Has any body faced this issue. What is that character that it is nto able to parse as the error says.
Thanks
-Pradip

hi
I have tried it using both xml and the initiate tab. I get the same error every time i do it for a particular value. i further think that this is occuring for the out put response that is got from the data base as the log says. ( given in the initial post). I can surely paster the input xml for you
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/db/top/InputXXESIOEHEADERSIFACE">
<ns1:XxesiOeHeadersIfaceCollection>
<ns1:XxesiOeHeadersIface>
<ns1:orderSource></ns1:orderSource>
<ns1:originalsystemreference></ns1:originalsystemreference>
<ns1:customerNumber></ns1:customerNumber>
<ns1:Country></ns1:Country>
</ns1:XxesiOeHeadersIface>
</ns1:XxesiOeHeadersIfaceCollection>
</soap:Body>
</soap:Envelope>

Client Proxy: XML message not well-formed unexpected symbol 'target

Hi,
I'm trying to get a client proxy to work based on several blogs (1387,1672)
The error I'm getting now is:
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'" p2="" p3="" p4="">PARSING.GENERAL</SAP:Code>
<SAP:Text language="EN">Parsing error: XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'</SAP:Text>
</SAP:ErrorHeader>
The proxy has been generated successfully
in SXMB_ADM R/3 role is application system and uses dest://rfc_dest
The rfc destination does not accept ?type=entry but apparently also does not need it. When I test the connection it gives a statuscode 200 (not 500)
SLDCHECK works fine.
Not sure where to look for this error?
Any ideas?
Thanks
Tom

Hello Smitha,
I forgot to mention that the message is still in R/3, it has not arrived in XI yet, so the error is visible in SXMB_MONI in R/3.
Also it is just a dummy message, It only contains one node and that is called differently:
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:IF021_HTTP_MSG xmlns:ns1="http://oce.com/xi/eu1/R3CCSEU/IF021_Ordrsp_TD_to_Ordrsp_CCS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<IF021_DT>GetOrdRsp</IF021_DT>
</ns1:IF021_HTTP_MSG>
Any mappings only take place in XI itself, and even there I have no node called target.
Regards
Tom

"Could not initiate the BPEL process because the input xml is not well form

hi all,
i am new to BPEL and tring to create a BPEL WebServices. now i got struck up with one issue like below
"Could not initiate the BPEL process because the input xml is not well formed, the reason is : Error parsing envelope Please correct the input xml."
But according to BPEL compiler there are no errors in the design and deployment as well. when i tries to initiate the deployed WS i am facing the above issue.
can anybody help me to fix this issue. Thanks in advance.
Regards,
Kalyan

hi' Kalyan,
The issue seems to be due to XSD file which you are importing while making the new BPEL process,
the XSD file is very sensitive even a simple upper case will create error, XSD file are many times used when you want
to pass some entries to be updated in the database.
use this XSD file:"discountflow.xsd"
<schema attributeFormDefault="qualified"
elementFormDefault="qualified"
targetNamespace="http://www.autoloan.com/ns/autoloan"
xmlns:tns="http://www.autoloan.com/ns/autoloan"
xmlns="http://www.w3.org/2001/XMLSchema">

<element name="Order" type="tns:OrderType"/>
<complexType name="OrderType">
<sequence>
<element name="orderid" type="int"/>
<element name="tenantid" type="int"/>
<element name="orderstatusid" type="int"/>
</sequence>
</complexType>
</schema>
<complexType name="Discount">
<sequence>
<element name="approval" type="boolean"/>
<element name="discount" type="int"/>
<element name="quantity" type="int"/>
</sequence>
</complexType>
</schema>
-Yatan

XML-error: Not well-formed (invalid token)

Hello,
I want a new XML structure in the Script from my InDesign CS6 (MAC 10.7.4) document. Here ist my little testscript:
     var doc = app.documents.item(0);
     var allStories = doc.stories;
    newXML = new XML('<root></root>');
    for(var i = 0; i < allStories.length; i++) {
        var curStory = allStories[i];
         for(var j = 0; j < curStory.textStyleRanges.length; j++) {
            var textStyleRange = curStory.textStyleRanges[j];
            alert(textStyleRange.contents);
            t = new XML('<content>' +textStyleRange.contents + '</content>');
            newXML.appendChild(t);
    alert(newXML);
The document has a text frame with the text, such as "C & A". When the script starts, it shows me the error message "XML-error: Not well-formed (invalid token)" on.
The problem with the "&" is. Probably also other Characters.
I think InDesign can automatically convert this into "&" or other entities, but how?

I solved the Problem.
The line with
t = new XML('<content>' +textStyleRange.contents + '</content>');
is the Problem. textStyleRange.contents is not converted. The right way is here for the line:
t = new XML('<content></content>');
t.appendChild(textStyleRange.contents);

Could not initiate the BPEL process because the input xml is not well forme

Your test request generated the following exception/fault:
Could not initiate the BPEL process because the input xml is not well formed, the reason is :
Error parsing envelope: (2, 152) Invalid char in text. Please correct the input xml.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body xmlns:ns1="http://xmlns.oracle.com/RO_Update2">
<ns1:RO_Update2ProcessRequest>
<ns1:UserName>operations</ns1:UserName>
<ns1:Responsibility>Depot Repair Engineer</ns1:Responsibility>
<ns1:API_VER>1.0</ns1:API_VER>
<ns1:P_commit>T</ns1:P_commit>
<ns1:init_msg>T</ns1:init_msg>
<ns1:Org_ID>207</ns1:Org_ID>
<ns1:R_Number>10782</ns1:R_Number>
<ns1:R_Status>1008</ns1:R_Status>
<ns1:Obj_Ver_No>1</ns1:Obj_Ver_No>
</ns1:RO_Update2ProcessRequest>
</soap:Body>
</soap:Envelope>

Try
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:RO_Update2ProcessRequest xmlns:ns1="http://xmlns.oracle.com/RO_Update2">
<ns1:UserName>operations</ns1:UserName>
<ns1:Responsibility>Depot Repair Engineer</ns1:Responsibility>
<ns1:API_VER>1.0</ns1:API_VER>
<ns1:P_commit>T</ns1:P_commit>
<ns1:init_msg>T</ns1:init_msg>
<ns1:Org_ID>207</ns1:Org_ID>
<ns1:R_Number>10782</ns1:R_Number>
<ns1:R_Status>1008</ns1:R_Status>
<ns1:Obj_Ver_No>1</ns1:Obj_Ver_No>
</ns1:RO_Update2ProcessRequest>
</soap:Body>
</soap:Envelope>

Getting the message: "XML code not well formed"

Hi folks!
I'm a blackberry newbie, and I love it, but I'm having a difficult time understanding why it won't allow me to download a WAP push link to download a ringtone. Every time I try to link I get the message: "The XLM code is not well-formed". I've tried everything from resetting the default browsers to contacting the company who is sending the WAP push message-and they had to download my BlackBerry diagnostics to try and figure out why the phone wasn't accepting the code. I'm going nuts trying to figure this out because it worked on my previous phone: same carrier (T-Mobile), Samsung phone.
Anybody have any insight into this?
Thanks!
Andy

Thank you for your response!
I did contact the site and he downloaded my blackberry diagnostics to diagnose the issue. He was able to download it to HIS Blackberry pearl (so he said) with no problem, and finally, I was able to download the exact same ringtone from the same site to my Samsung phone a week before I purchased the BlackBerry.
It sounds to me as if the issue is with the BlackBerry not accepting the WAP site's code the same way the Samsung did.
I'm a complete newbie, but that's how it seems to me. Frustrating

XML from CF not well-formed?

I have been working through the Training from the Source book
on Flex2 (Trapper, Boles, Talbot, etc.). In Lesson 17, it deals
with accessing server-side objects.
One piece of code accesses a CF template, which brings in an
XML file:
<mx:HTTPService id="prodByCatRPC"
url="
http://localhost/flexGrocer/xml/categorizedProducts.cfm"
result="prodByCategoryHandler(event)"
resultFormat="e4x" />
The CF plate from the book's file has the following:
<cfheader name="Expires" value="#now()#" />
<cfxml variable="xProducts">
<cfinclude template="categorizedProducts.xml">
</cfxml>
<cfset xmlObject=ToString(xProducts)>
<cfcontent type="text/xml" />
<cfoutput>#variables.xmlObject#</cfoutput>
When run the Flex file, I get a run-time message which seems
to indicate that the XML is not well-formed. (Here is a bit of the
message; not sure I'm understanding it!):
[RPC Fault faultString="Error #1088: The markup in the
document following the root element must be well-formed."
faultCode="Client.CouldNotDecode" faultDetail="null"]
I am ASSUMING that the CF page is not returning the xml as
desired, because if I simply change the flex http service call to
the xml file that the CF page is including, the flex app runs as
expected and without errors:
url="
http://localhost/flexGrocer/xml/categorizedProducts.xml"
(something in the posting mech is making the above url
statement messed up, but you can probably tell what I mean)
I am a CF developer and although haven't used the book's
exact method to get the cf generated xml, I have done so
successfully for Spry and other things.
I tried some ot the things I had to do to get the CF
generated xml to work in Spry with this flex, but didn't help.
Tried adding a reset='true" with the cfcontent tag; tried making
the cfcontent wrap the output; added cfprocessing tags to
suppresswhitespace.
Appreciate any thoughts/help on how to solve this. Also,
whether others agree that the problem is with the generated xml
rather than something else.
Thanks
Keith

I don't remember the exact context when I first posted this
question and answered it; but, if one doesn't want to change
overall settings for debugging in cf admin., I *think* you can
ajust for a specific area using cfsetting and/or
cfprocessingdirective. There's a number of attributes and
combinations there that I think can take care of the problem. I
forget for sure, but may want to try that, especially on a
development box where you might generally want debugging to be on.
Also, if using cfcs in any part of what you generate, they
can produce whitespace. To solve (or minimize), make sure that
output attribute in the component is false and that output in
function is false (unless directly outputting within the function.
Seems like CF and whitespace is an ongoing item to try to
manage.
Keith

Not well-formed XML

Hi guys,
I need to parse an XML file which is not well formed.
For example, the value of an element named 'topic' contains html tags which are not ended properly etc..
e.g. <topic>Some text <BR></topic>
Why do I need this? Because some idiots on their web site publish XML data (not well formed) which indeed is very valuable to me, and I want to use it. I tried contacting them on the "not-well-formed-XML" issue but haven't managed to get a reply yet. Hence I have been struggling with this using the SAX API and so on...
I think there should be a way to ignore some elements' content when parsing the XML data but I haven't been able to do it...I am not experienced on SAX or DOM API's...
For example if the problem is caused only by the BR tags then when I encounter it, either startTag or endTag, I should be able to ignore it. When I say "ignore", I mean "not change the state of the parser", or undo the last state change or whatever...Well at least I think I would write an XML parser like this if I were to do that...
Any help is appreciated...

Sorry to be the bearer of bad news.
There is no such thing as an "XML file which is not
well formed." There are files that look like they
might be XML files but are not valid. I think that is
what you have. One of the key differences between XML
and HTML is that HTML has allowed sloppy habits to
become routine. XML prohibits them from getting past
the hurdle of validation.
Dave PattersonI'm not sure about the comments that you have made about the validity and well-formedness about XML documents. As I said I'm not experienced in XML but as far as I understand, a document is called "valid" when it conforms to all the constraints imposed by a DTD. However, there is no DTD in my case and the XML document I have is not "well-formed" as defined below:
A well-formed XML document is syntactically correct. It does not have any angle brackets that are not part of tags. (The entity references < and > are used to embed angle brackets in an XML document.) In addition, all tags have an ending tag or are themselves self-ending (<slide>..</slide> or <slide/>). In addition, in a well-formed document, all tags are fully nested. They never overlap, so this arrangement would produce an error: <slide><image>..</slide></image>. Knowing that a document is well formed makes it possible to process it. A well-formed document may not be valid however. To determine that, you need a validating parser and a DTD.
According to the above definition the XML document I have violates the constraints and not well formed. But you can argue that the XML document I got is not an XML document but it is just some document :) Then anyway, I am not sure about all this terminology...
The technique you suggested seems reasonable but as far as I know the SAX parser stops parsing when a fatal error is encountered. So I don't know how I will trap/ignore the error and continue...
As for the JTidy suggestion:
I have tried using HttpUnit which uses JTidy and couldn't get it right. I think when a DOM is created using JTidy the document must also be well formed (XHTML or whatever)...Am I wrong here?
Thanks a lot...

XML Not well formed

I have an XSLT mapping as described below:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/biztalk_1">
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
<ns0:header>
<ns0:delivery>
<ns0:message>
<ns0:messageID><xsl:value-of select="header/delivery/message/messageID"/></ns0:messageID>
</ns0:message>
</ns0:delivery>
</ns0:header>
<ns0:body>
<ns0:FinancialTransaction.CreateFromData>
<ns0:CompanyCode><xsl:value-of select="body/FinancialTransaction.CreateFromData/CompanyCode"/></ns0:CompanyCode>
</ns0:FinancialTransaction.CreateFromData>
</ns0:body>
</ns0:biztalk_1>
</xsl:template>
</xsl:stylesheet>
however when I execute this mapping I keep getting the error saying that the XML is not well formed...
I have looked at it but really cant see where I am going wrong.. Could someone take a look at the above xslt and let me know where this error could be coming from....

ok this is the xslt again
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/biztalk_1">
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
<ns0:header>
      <ns0:delivery>
         <ns0:message>
            <ns0:messageID><xsl:value-of select="header/delivery/message/messageID"/></ns0:messageID>
         </ns0:message>
      </ns0:delivery>
   </ns0:header>
   <ns0:body>
      <ns0:FinancialTransaction.CreateFromData>
         <ns0:CompanyCode><xsl:value-of select="body/FinancialTransaction.CreateFromData/CompanyCode"/></ns0:CompanyCode>
      </ns0:FinancialTransaction.CreateFromData>
   </ns0:body>
</ns0:biztalk_1>
</xsl:template>
</xsl:stylesheet>
and the source will look something like this
<?xml version="1.0" encoding="UTF-8"?>
<ns0:biztalk_1 xmlns:ns0="urn:biztalk-org:biztalk:biztalk_1">
   <ns0:header>
      <ns0:delivery>
         <ns0:message>
            <ns0:messageID/>
            <ns0:sent/>
         </ns0:message>
      </ns0:delivery>
   </ns0:header>
   <ns0:body>
      <ns0:FinancialTransaction.CreateFromData>
         <ns0:CompanyCode/>
      </ns0:FinancialTransaction.CreateFromData>
   </ns0:body>
</ns0:biztalk_1>
There are actually more fields but this is a toned down version...

Not well-formed error while implementin ajax in firefox---can anyone help

hi techies,
I'm trying to implement ajax in firefox and i'm getting not well-formed error in error console
heres part of code
var xmlHttp;
function create(){
if(window.ActiveXObject){
xmlHttp=window.ActiveXObject("Microsoft.XMLHTTP");
else if(window.XMLHttpRequest){
xmlHttp=window.XMLHttpRequest();
else{
xmlHttp=new ActiveXObject("Msxml2.XMLHTTP");
function getEmployeeDetails(){
frm = document.forms[0];
empid = frm.elements["empid"].value;
url="empdetails.jsp?empid=" + empid;
xmlHttp.open("GET" ,url, true);
xmlHttp.onreadystatechange=doUpdate;
xmlHttp.send(null);
function doUpdate(){
if(xmlHttp.readyState==4 && xmlHttp.status == 200){
var root = xmlHttp.responseXML.documentElement;
----so on
jsp Page is
<%@ page import="java.sql.*" contentType="text/xml" %>
<%
String empid=request.getParameter("empid");
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection con=DriverManager.getConnection("jdbc:odbc:vmouli","hr","hr");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select first_name,salary from employees where employee_id=" + empid);
if(rs.next()){
out.println("<employee><name>");out.println(rs.getString(1));
out.println("</name><salary>");out.println(rs.getString(2));
out.println("</salary></employee>");
else{
out.println("<error>Employee ID not found</error>");
rs.close();
st.close();
con.close();
%>
Firefox error console is saying not well-formed and is pointing to starting of my jsp page
can anyone help plzzz

mouli007 wrote:
Thanx for that Cotton
My XML document is wellformed no doubt about thatNo doubt about that?!?
I would say there is a great deal of doubt about that, especially since the subject of this thread, which you stated was the error message from FireFox is that the document is not well formed at all. I have some more wild guesses about what you've screwed up. Would you like to hear them? My best guess at this point would be that you are outputting some whitespace at the start of the output.
Anyway, this seems pretty pointless. Your code is crap. And I really don't see the point in telling us you have an error, posting code, then having several people identify several major problems in your code and then for you tell us that your code is perfect. Your code is not perfect. It's terrible. Fix it. You've been given several ideas in this and your cross-post as to how to fix it.

Not well-formed error in firefox in implementing ajax--pls help

hi techies,
I'm trying to implement ajax in firefox and i'm getting not well-formed error in error console
heres part of code
var xmlHttp;
function create(){
if(window.ActiveXObject){
xmlHttp=window.ActiveXObject("Microsoft.XMLHTTP");
else if(window.XMLHttpRequest){
xmlHttp=window.XMLHttpRequest();
else{
xmlHttp=new ActiveXObject("Msxml2.XMLHTTP");
function getEmployeeDetails(){
frm = document.forms[0];
empid = frm.elements["empid"].value;
url="empdetails.jsp?empid=" + empid;
xmlHttp.open("GET" ,url, true);
xmlHttp.onreadystatechange=doUpdate;
xmlHttp.send(null);
function doUpdate(){
if(xmlHttp.readyState==4 && xmlHttp.status == 200){
var root = xmlHttp.responseXML.documentElement;
----so on
jsp Page is
<%@ page import="java.sql.*" contentType="text/xml" %>
<%
String empid=request.getParameter("empid");
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection con=DriverManager.getConnection("jdbc:odbc:vmouli","hr","hr");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select first_name,salary from employees where employee_id=" + empid);
if(rs.next()){
out.println("<employee><name>");out.println(rs.getString(1));
out.println("</name><salary>");out.println(rs.getString(2));
out.println("</salary></employee>");
else{
out.println("<error>Employee ID not found</error>");
rs.close();
st.close();
con.close();
%>
Firefox error console is saying not well-formed and is pointing to starting of my jsp page
can anyone help plzzz

As BalusC said - run the JSP producing the xml.
Save that xml to a file - INCLUDING any white space - because thats what you actually get.
Open that xml file in your browser - it should tell you at that point if your xml is well formed.
AS BalusC said this is better done in a servlet - especially since you're just doing out.println.
JSPs add extra whitespace and carriage returns. While that won't necessarily break XML, it can cause problems with the first few characters.

Got "Reponse is not well-formed XML" error when calling FormDataIntegration web service

Hi,
I'm using Windows Server 2008 + LiveCycle Server ES2 (Reader Extensions) + ASP.NET
This problem only happened when I run the ASP.NET program with the licensed version of the server, (which i installed form the CD provided)
However, there is no problem in my development environment with the trial version downloaded from Adobe website, the import data was successful and a correct PDF form can be returned.
My question is that whether there is a problem within the LiveCycle services? or there is missing component that needs to be installed?? Thanks
After call the importData of FormDataIntegration, I got below error
Response is not well-formed XML.
System.InvalidOperationException: Response is not well-formed XML. ---> System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
--- End of inner exception stack trace ---
I checked in LiveCycle's jboss log, I found below errors:
2011-02-17 14:16:37,086 ERROR [org.apache.axis.encoding.ser.BeanSerializer] Exception:
java.lang.NullPointerException
at com.adobe.idp.dsc.provider.impl.soap.axis.ser.ArraySerializer.serialize(ArraySerializer.j ava:76)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1 504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:707)
at com.adobe.idp.dsc.provider.impl.soap.axis.ser.AdobeAxisBeanSerializer.serialize(AdobeAxis BeanSerializer.java:281)
at java.lang.Thread.run(Thread.java:619)
2011-02-17 14:16:37,087 ERROR [org.apache.axis.encoding.ser.BeanSerializer] Exception:
java.io.IOException: java.lang.NullPointerException
at com.adobe.idp.dsc.provider.impl.soap.axis.ser.AdobeAxisBeanSerializer.serialize(AdobeAxis BeanSerializer.java:326)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1 504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
: at java.lang.Thread.run(Thread.java:619)
2011-02-17 14:16:37,088 ERROR [org.apache.axis.SOAPPart] Exception:
java.io.IOException: java.io.IOException: java.lang.NullPointerException
at com.adobe.idp.dsc.provider.impl.soap.axis.ser.AdobeAxisBeanSerializer.serialize(AdobeAxis BeanSerializer.java:326)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1 504)
at java.lang.Thread.run(Thread.java:619)
2011-02-17 14:16:37,088 WARN [org.apache.axis.attachments.AttachmentsImpl] Exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname: XXXX
ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error.
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:333)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
... 33 more
Caused by: java.lang.NoClassDefFoundError: com/adobe/formServer/utils/LogUtils
at com.adobe.formServer.utils.CommonGibsonUtils.PDFDocumentFromDocument(CommonGibsonUtils.ja va:122)
at com.adobe.livecycle.formdataintegration.server.FormData.importData(FormData.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
... 74 more
2011-02-17 14:16:37,090 ERROR [org.apache.axis.encoding.ser.BeanSerializer] Exception:
java.lang.NullPointerException
at com.adobe.idp.dsc.provider.impl.soap.axis.ser.ArraySerializer.serialize(ArraySerializer.j ava:76)
at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1 504)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:707)

it's base64, here's the codes i called, any hints?
            FormDataIntegration.FormDataIntegrationService dataIntClient = new FormDataIntegration.FormDataIntegrationService();
            dataIntClient.Url += "?blob=base64";
            dataIntClient.Credentials = new System.Net.NetworkCredential(account, password);
            FormDataIntegration.BLOB inXMLData = new FormDataIntegration.BLOB();
            inXMLData.binaryData = xmlData;
            FormDataIntegration.BLOB inPDFForm = new FormDataIntegration.BLOB();
            string pathPDF = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "bin\\ReplySlipByEmail.pdf");
            FileStream fsPDF = new FileStream(pathPDF, FileMode.Open);
            int lenPDF = (int)fsPDF.Length;
            byte[] bytePDF = new byte[lenPDF];
            fsPDF.Read(bytePDF, 0, lenPDF);
            inPDFForm.binaryData = bytePDF;
            FormDataIntegration.BLOB result = dataIntClient.importData(inPDFForm, inXMLData);
            return ApplyUsageRightsToPDF(result.binaryData, account, password, LCCertName);

Firefox crashes continually. Now I'm getting this error and cannot open firefox at all: XML Parsing Error: not well-formed Location: chrome://browser/content/browser.xul Line Number 1068, Column 87:

SInce the latest update Firefox has crashed continually for about two weeks now. Continually means at least 10 times a day. Now it does not open at all and I get this message when launching Firefox:
XML Parsing Error: not well-formed Location: chrome://browser/content/browser.xul Line Number 1068, Column 87:

SInce the latest update Firefox has crashed continually for about two weeks now. Continually means at least 10 times a day. Now it does not open at all and I get this message when launching Firefox:
XML Parsing Error: not well-formed Location: chrome://browser/content/browser.xul Line Number 1068, Column 87:

Xml is not well formed and caller ID issues

Similar Messages

Maybe you are looking for