Special Character Error in Message in PI after PI-PRD Upgrade

Dear Experts,
We had a PI PRD upgrade 3 days back  from (PI NW 7.3 ) from SP-07 to SP-11.
After this upgrade we ar facing one peculiar issue which was not there before upgrade.
The messages containing special character like '&', ", etc is not getting parsed and throwing error.
The messages having no such characters are passing smoothly.
Is it upgrade related issue??
Thanks
Sumit

Hi Sumit,
There is not a problem to introduce a java mapping in a response of a ECC system, at least if you are not using a standard PI software component. You can set in the response Operation Mapping, two mappings, the first one the java mapping and the second one your current mapping.
Java Mapping example: Java Mapping: To change the encoding type or replacing special characters.
Regards.

Similar Messages

  • Special character error

    HI,
    we are facing problem during ODS activation, it is a kinda of special
    character error, i maintained almost all characters in RSKC,
    rsallowedchar table is reflecting the same, but still it is throwing
    special character error, that special character system showing is "□".
    Please look into this ASAP

    Hello,
    Please use the standard FM - CONVERT_HASH or Please use the below code :
    ATA:    BEGIN OF trans OCCURS 0,
                 x     TYPE x VALUE '00',
                 c_00  TYPE c VALUE ' ',
                 soh   TYPE x VALUE '01',
                 c_01  TYPE c VALUE ' ',
                 stx   TYPE x VALUE '02',
                 c_02  TYPE c VALUE ' ',
                 etx   TYPE x VALUE '03',
                 c_03  TYPE c VALUE ' ',
                 eot   TYPE x VALUE '04',
                 c_04  TYPE c VALUE ' ',
                 enq   TYPE x VALUE '05',
                 c_05  TYPE c VALUE ' ',
                 ack   TYPE x VALUE '06',
                 c_06  TYPE c VALUE ' ',
                 bel   TYPE x VALUE '07',
                 c_07  TYPE c VALUE ' ',
                 bs    TYPE x VALUE '08',
                 c_08  TYPE c VALUE ' ',
                 ht    TYPE x VALUE '09',
                 c_09  TYPE c VALUE ' ',
                 lf    TYPE x VALUE '0A',
                 c_0a  TYPE c VALUE ' ',
                 vt    TYPE x VALUE '0B',
                 c_0b  TYPE c VALUE ' ',
                 ff    TYPE x VALUE '0C',
                 c_0c  TYPE c VALUE ' ',
                 cr    TYPE x VALUE '0D',
                 c_0d  TYPE c VALUE ' ',
                 so    TYPE x VALUE '0E',
                 c_0e  TYPE c VALUE ' ',
                 si    TYPE x VALUE '0F',
                 c_0f  TYPE c VALUE ' ',
                 dle   TYPE x VALUE '10',
                 c_10  TYPE c VALUE ' ',
                 dc1   TYPE x VALUE '11',
                 c_11  TYPE c VALUE ' ',
                 dc2   TYPE x VALUE '12',
                 c_12  TYPE c VALUE ' ',
                 dc3   TYPE x VALUE '13',
                 c_13  TYPE c VALUE ' ',
                 dc4   TYPE x VALUE '14',
                 c_14  TYPE c VALUE ' ',
                 nak   TYPE x VALUE '15',
                 c_15  TYPE c VALUE ' ',
                 syn   TYPE x VALUE '16',
                 c_16  TYPE c VALUE ' ',
                 etb   TYPE x VALUE '17',
                 c_17  TYPE c VALUE ' ',
                 can   TYPE x VALUE '18',
                 c_18  TYPE c VALUE ' ',
                 em    TYPE x VALUE '19',
                 c_19  TYPE c VALUE ' ',
                 sub   TYPE x VALUE '1A',
                 c_1a  TYPE c VALUE ' ',
                 esc   TYPE x VALUE '1B',
                 c_1b  TYPE c VALUE ' ',
                 fs    TYPE x VALUE '1C',
                 c_1c  TYPE c VALUE ' ',
                 gs    TYPE x VALUE '1D',
                 c_1d  TYPE c VALUE ' ',
                 rs    TYPE x VALUE '1E',
                 c_1e  TYPE c VALUE ' ',
                 us    TYPE x VALUE '1F',
                 c_1f  TYPE c VALUE ' ',
                 diez    TYPE x VALUE '23',
                 c_23  TYPE c VALUE ' ',
    Start of insertion by CGT DR77618
                 exma  TYPE x VALUE '21',    "'!'
                 c_21  TYPE c VALUE ' ',
                 auml  TYPE x VALUE 'C4',   "'Ä'
                 c_8e  TYPE c VALUE 'A',
                 unds  TYPE x VALUE '5F',   "'_'
                 c_2d  TYPE c VALUE '-',
    End of insertion by CGT DR77618
    Start of insertion(+) DR85766
                 sque  TYPE x VALUE '7F',  " 
                 c_squ TYPE c VALUE ' ' ,
                 deg   TYPE x VALUE 'B0',  " °
                 c_deg TYPE c VALUE ' ' ,
    End of insertion(+)   DR85766
    Start of insertion(+) DR88519
                 sla   TYPE x VALUE '2F',  " /
                 c_sla TYPE c VALUE ' ' ,
    End of insertion(+)   DR85766
               END OF trans.
      output = input.
      TRANSLATE output USING trans.
    ENDFUNCTION.

  • Orchestration exception:Exception occurred when persisting state to the database because of special character ' ' in HL7 message.

    In some scenarios HL7 message is coming with special character ‘’ and HL7 dis-assembler escaping this character with “”. But while sending out (pass thru pipeline but orchestration trying to persist here at last sendshape.) from orchestration
    this message failing with the error “Exception occurred when persisting state to the database.”
    As per the analysis , Orchestration is unable to convert to xml document from a
    XLANGMessage because of this special character. We have tried to call custom .net class with following code and its failing here as well (I think orchestration also trying to do same way and failing with the message and failing with same error.).
    public void ProcessRequest(XLANGMessage reqMessage)
    XmlDocument xmlDocument = (XmlDocument)reqMessage[0].RetrieveAs(typeof(XmlDocument)); It is failing here with the error
    “ ', hexadecimal value 0x10, is an invalid character. Line 1, position 1865. “
    Note : Please find the special character in the attachment circled in red color. 

    Hi ,
    Please find the xml and the screenshot.
    <OBX_ObservationResult>
      <OBX_1_SetIdObx>3</OBX_1_SetIdObx>
      <OBX_2_ValueType>TX</OBX_2_ValueType>
      <OBX_3_ObservationIdentifier>
        <CE_0_Identifier>P.112</CE_0_Identifier>
        <CE_1_Text>Where pt. will be transported to \T\ where &#x10;&#x1;famly can wait:</CE_1_Text>
      </OBX_3_ObservationIdentifier>
      <OBX_4_ObservationSubId />
      <OBX_5_ObservationValue>Y</OBX_5_ObservationValue>
      <OBX_6_Units>
        <CE_0_Identifier />
      </OBX_6_Units>
      <OBX_7_ReferencesRange />
      <OBX_8_AbnormalFlags />
      <OBX_9_Probability />
      <OBX_10_NatureOfAbnormalTest />
      <OBX_11_ObservationResultStatus>N</OBX_11_ObservationResultStatus>
    </OBX_ObservationResult>

  • Unsported character error in message mapping

    I use a sender mail adapter to read an xml and then map it to another message type. Most of the time, it's ok. But when there are some special German character such as ö ä ß, then I get the "unsuported character" error.
    Anyone could help?
    thanks!
    com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: Unsupported character: 32(:main:, row:11, col:14) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207) at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:205) at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143) at com.sap.engine.lib.xml.parser.XMLParser.scanCharData(XMLParser.java:2000) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2445) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1841) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2843) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more

    As the mail server provides the correct encoding, the MessageTransformBean does the conversion to UTF-8.
    If the encoding was not set by the mail server, then the MessageTransformBean would only set the content type, but not do any conversion.
    When you are not sure, if the content type is by the mail server, you can apply the MessageTransformBean twice: First with iso-8859-1, second with UTF-8
    I am not sure, why the mapping tool cannot do the conversion, but I think this is because the content type is not application/xml. But this is only a guess.
    What happens, when you only apply the MessageTransformBean, but do not change the XML encoding?

  • Oracle error  "No message file for" after Upgrade to 10.2.0.5

    After upgrade from 9.2.0.8 to 10.2.0.5 i get the following error "No message file for"
    (with both Users sidadm and orasid)
    Platform AIX 64 bit
    The installation und Upgrade with dbua works fine.
    DB and SAP runs after the Upgrade.
    then I tried
    SQL> select xx from v$log;
    select xx from v$log
    ERROR at line 1:
    ORA-00904: Message 904 not found; No message file for produstyle='font-
    family:courier' ct=RDBMS,
    facility=ORA; arguments: ["XX"]
    The Environment is correct,
    ORACLE_HOME,ORACLE_SID,PATH,LIBPATH have right Values.
    I cant find any failure in Configuration or Install Logs.
    So i tried the following:
    Copy the complete Directorie /oracle/SID/102_64/rdbms/msg from a
    10.2.0.4 Oracle Installation to the 10.2.0.5 home.
    the result ist that the Messagefile could be read by Oracle an i get
    the ORA-00904
    Here the same Query:
    SQL> select xx from v$log;
    select xx from v$log
    ERROR at line 1:
    ORA-00904: "XX": invalid identifier
    So I do the same procedure with an other System.
    I detect:
    the Patch 9952230 (SAP_102051_201011/9952230) delivers
    both Message Files oraus.msg and oraus.msb which caused the problem.
    Has anyone the same Problem?
    Are there any other Impacts with wrong Message Files .
    I raised a OSS Call, but no answer till today.
    best regards
    Uwe

    I could not find anything is sap notes, but oracle recommends to update binary file oraus.msb in $ORACLE_HOME/rdbms/mesg
    Download link:
    https://updates.oracle.com/ARULink/PatchDetails/process_form?patch_num=10235783
    You can find more details also in:
    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=10235783.8
    https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=10235783
    The problem with this solution. It is not officially released by SAP.

  • Unquoted special character error

    Am reading data from a file and parsing through it using StringTokenizer. I am putting the data into DB2 tables and therefore need to set the integer and fraction count for decimal numbers so they won't abend the program if they are over the DB2 setting. I am calling an internal method with the following line:
    pstmt_master.setDouble(23, formatDecimal(token, decForm));
    where token is the value to interpret and decForm is the pattern to apply, in this case it is:
    "###########0.####;-###########0.####"
    The method that is called is:
    public double formatDecimal(String numStr, String format) {
    NumberFormat nf = NumberFormat.getInstance(Locale.US);
         double intdbl = 0;
         if (nf instanceof DecimalFormat) {
              ParsePosition pos = new ParsePosition(0);
              nf.setMaximumIntegerDigits(12);
              nf.setMinimumIntegerDigits(0);
              nf.setMaximumFractionDigits(4);
              nf.setMinimumFractionDigits(0);
              DecimalFormat df = (DecimalFormat)nf;
              df.applyPattern(numStr);
              Double db = new Double(numStr);
              double dbl = db.doubleValue();
              BigDecimal bd = new BigDecimal(dbl);
              db = new Double(df.format(bd.doubleValue()));
              intdbl = db.doubleValue();               
         return intdbl;
    I am trimming the value (token), and for the purposes of debugging this problem have done a println on the value which is the number just before the error below. Can anyone offer any help as to why I am getting this error?
    By the way, this is not the first value passed through the method, it successfully handles about 10 values before abending on this value.
    51050
    java.lang.IllegalArgumentException: Unquoted special character '0' in pattern "51050"
         at java.text.DecimalFormat.applyPattern(DecimalFormat.java:1334)
         at java.text.DecimalFormat.applyPattern(DecimalFormat.java:1208)
         at JavaAgent.formatDecimal(JavaAgent.java:758)
         at JavaAgent.NotesMain(JavaAgent.java:225)
         at lotus.domino.AgentBase.runNotes(AgentBase.java:161)
         at lotus.domino.NotesThread.run(NotesThread.java:203)

    I'm thinking that this line:
    df.applyPattern(numStr);should read
    df.applyPattern(format);You appear to be passing the number as the pattern.
    Tim

  • Special Character error in IDOC

    All,
    I am trying to upload PO data using IDOC type "PORDCR1" from LSMW. All is well till I convert data. We have some speical characters in short text field at item level and even when I convert the data and display it from LSMW it looks fine, but when I processing idoc it's erroring out meaning if I have special character "Á" in IDOC during processing it's getting converted to "Á#" and it's screwing up the positions.
    What I am not able to understand is when I am displaying the converted data in segment mode in LSMW it's getting displayed perfectly without extra "#", but when I am checking errored idoc from WE05 it has this new #. Did anyone come across this issue?
    Your help will be greatly appreciated. Thanks for your time.

    Ok, the issue was with LSMW port (which was not marked as UNICODE) and because of which it's not translating special characters....

  • Error In Message Time Stamp After Deleting Single Messages

    I currently have an iPhone 5 running the latest version of iOS 8.  After updating to iOS 8 ive noticed that when I delete a message from a conversation (without deleting the entire thread), the timestamp that shows up on the conversation thread still shows the time of the last message as the one that I deleted.  It always used to revert the time/date to the last message that was left in the conversation after removing messages, but doesn't anymore?
    Just wondering if anyone else was having this issue or if there was a fix for it yet!!
    Thanks!

    i am having the same issue, its not fixed i hope apple fixes it

  • Error locking object in SPAU after 3.5 upgrade

    Hi,
    When I try to change the status of the object either "Reset to Original" or "Adopt Modifications" I get the message saying that "Error Locking the Objects".  What does that mean?  Does it mean that I dont have auth to modify the objects?
    Also I would like to know what does the STOP sign mean when I complete adjusting the object mean?
    Thanks

    Hi,
    This looks like the object referred is still locked in the transport system, which means it's contained in a change request, for which you don't have a task opened, and thus, you're not allowed to acquire the lock for yourself.
    My suggestion is that you find the change request, create a task for yourself, and then try to adjust the object.
    BTW, this is a general Netweaver question, unrelated to BW, so you'd get many more responses on those forums.
    Best regards,
    Daniel

  • Error Code 2300 on Restore after failed Os4 upgrade.

    Pretty simple. Attempted to upgrade to the new Os4 with a 2nd gen iPod touch. For whatever reason, iTunes recognizes it, but the update failed which sent it into recovery mode. After 6 attempts at a restore, error code 2300 doesn't fail to pop up while preparing the iPod for restore. I've also tried 3 different USB ports- aiming for different computers later in the day. I don't want to have to invest money into a newer iPod - even though this one is 1 1/2-2 years old just about. Thankfully music is on the computer happily waiting to be loaded back in - so the only issue is getting the iPod itself to restore or SOMETHING. Paper weight - no thanks.
    Any help is appreciated.
    -Mare.

    I have the same issue. from what i've gathered the issue is with the data transfer via usb
    try a different computer

  • "Object reference not set to an instance of an object" error while accessing document libraries after in place upgrade to SP 2010

    I performed an inplace upgrade on my sharepoint 2007 installation and post the upgrade while trying to browse the document libraries on the site i get the following Error. HAs anyone encountered a similair error?? What could be the cause and resolution
    for this
    Any pointers/solution appreciated.
    Description: An
    unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
    Exception
    Details: System.NullReferenceException: Object reference not set to an instance of an object.
    Source
    Error: 
    An unhandled exception was generated during the execution of the
    current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    Stack
    Trace: 
    [NullReferenceException: Object reference not set to an instance of an object.]
    Microsoft.SharePoint.WebPartPages.ListViewWebPart.PrepareContentTypeFilter(SPList list, Hashtable[] excludedTransformers) +682
    Microsoft.SharePoint.WebPartPages.ListViewWebPart.GenerateDocConvScriptBlock(SPWeb web, SPList list) +482
    Microsoft.SharePoint.WebPartPages.XsltListViewWebPart.OnPreRender(EventArgs e) +571
    Microsoft.SharePoint.WebPartPages.WebPartMobileAdapter.OnPreRender(EventArgs e) +78
    System.Web.UI.Control.PreRenderRecursiveInternal() +11032094
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3393
    Version
    Information: Microsoft .NET Framework Version:2.0.50727.4952; ASP.NET Version:2.0.50727.4955
    My SharePoint Blog
    http://dhireny.blogspot.com

    How to be in my case??
    [NullReferenceException: Object reference not set to an instance of an object.]
    Microsoft.SharePoint.WebPartPages.ListViewWebPart.PrepareContentTypeFilter(SPList list, Hashtable[] excludedTransformers) +694
    Microsoft.SharePoint.WebPartPages.ListViewWebPart.GenerateDocConvScriptBlock(SPWeb web, SPList list) +482
    Microsoft.SharePoint.WebPartPages.XsltListViewWebPart.OnPreRender(EventArgs e) +571
    Microsoft.SharePoint.WebPartPages.WebPartMobileAdapter.OnPreRender(EventArgs e) +78
    System.Web.UI.Control.PreRenderRecursiveInternal() +11141054
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Control.PreRenderRecursiveInternal() +223
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3393

  • Error deploying to iPod touch after 2.0 upgrade

    Been in the developer program a while and haven't had any problems with putting apps to my iPod touch until now. Downloaded the release version of the SDK, then I started having problems. Also have purchased release 2.0 software for the Touch and have it installed. When I try to Build | Go from Xcode, I get the following error:
    Your mobile device has encountered an unexpected error (0xE8000001) during the install phase: Verifying application.
    Anyone know what this might mean? First suspected the 2.0 software, now I'm starting to think more about certificates/profiles. XCode lists the device just fine as 5A347. Also has my provisioning profile checked.
    One other thing that is strange is in the Apple docs on Multiple Applications they just released, it mentions checking in Key Chain under the Keys category. I don't see anything related to this in that category. But I do still have certificates listed in the System keychain.
    I guess it is time to wipe out all the profiles again and start over. Any other ideas? Really what I'd like to see is a log file or something that gives me the real error, or at least the thing its trying to verify when it errors out.

    I had forgotten about that in my new App. Changing it didn't help though. Also, the app that I have successfully deployed to the device before (and is on the AppStore now) has the same error. And it's identifier was already set.
    Just for reference though, I'm setting my Identifier to the same thing that is listed in XCode under Organizer | Provisioning. And that is the same as listed under Name in the AppIDs section of the Program Portal. I also had used a * for the Bundle ID when I setup that AppID.
    Thanks for the thought. Don't think that is the problem though. At least changing it to the above didn't seem to have any affect.

  • Error installing or removing Itunes after trying to upgrade to 7.6

    Hi There,
    I recently tried to upgrade to 7.6 from 7.5 and this has caused me some issues.
    Firstly when upgrading a dialog box opens stating that itunes.msi cannot be found in local settings - however it was there. I manually moved to the path still to no avail.
    I followed all steps to remove itunes and do a clean install - as stated in the support site "how to uninstall section". This failed at the add remove stage. Stating "The older version of itunes cannot be removed. Please contact your technical support group".
    As there was no add remove option I removed all references to itunes in my local settings folder, program files and registry and went to reinstall, however I am still getting the same message above when tryin to install.
    Now I am stuck with no version of itunes at all on my PC. If anyone could help I would greatly appreciate it.
    Do Apple have a default "scrubber" that will remove all reference/instances of itunes?
    Many Thanks,
    Martin

    I'm having the same exact problem! The only diffrerence is that I haven't unistalled my current version and it still works. But I REALLY want those new iPod Touch Apps! But they require 7.6! Why is it when ever Apple does something great for us they some how find a way to screw us at the same time.
    I don't want a scrubber however cause that migth wipe my settings and or library. Instead I want a magic file that fixes what ever apple screwed up and intalls 7.6!
    ....Or I suppose a copy of iTunes.msi for my version would do to....
    My iTunes version is 7.4.3.1

  • Error trying to sync iPhone after IOS 7 upgrade

    Since upgrading to IOS 7 I can no longer sync my iPhone I get this message:
    I've tried rebooting both my MacBook Pro and my iPhone and still get the same message.
    Has anyone else run into this?  Is there a workaround?

    An iPhone can be synced with a single iTunes library only.
    When syncing an iPhone with a different iTunes library on the same computer, or with an iTunes library on a different computer, all iTunes content on the iPhone will be erased and replaced with the chosen content from the new or different iTunes library.
    http://support.apple.com/kb/HT1296
    This is why maintaining a backup of all your important data - including your iTunes library stored on a external drive used for backup purposes only, or stored on some other media is so important.
    iTunes includes an option to transfer content purchased from the iTunes Store from an iPod or iPhone, but this is for content that was purchased from the iTunes Store only.
    Without syncing, at the iTunes menu bar go to File and select Transfer Purchases From - the name of your iPhone.

  • Error 1604 - Can't restore after 2.0 upgrade

    I have already reported this problem to Itunes and made a visit to the "Genius Bar". It was bricked during the firmware upgrade to 2.0 and all the Genius bar could do is restore it to the previous firmware even though I have a receipt showing I purchased 2.0. Ugh!!
    Anyway, in searching my hard drive, I cannot find the 2.0 firmware and it looks like it never downloaded in the first place. I have searched for files with ipsw extension and there's nothing, anywhere. Are you allowed to download again for free? Maybe this is why it bricked trying to load a file that wasn't even there? Any insight and/or help greatly appreciated!

    People who have still not solved error 1604 and had a bricked iPhone no matter what they tried, might manage to revive it by following these instructions (on how to downgrade from 2.0 to 1.1.4).
    You will need the following:
    - iTunes 7.5 (NOT 7.7)
    - iPhone firmware iPhone1,11.1.4_4A102Restore.ipsw
    Step 1:
    Uninstall iTunes 7.7 completely if you have it and restart your computer.
    Step 2:
    Install iTunes 7.5
    Step 3:
    Your iPhone should be in 2 states, either stuck on the "Slide to make emergency calls" screen, or you tried to restore before and it's stuck on the new look "connect to iTunes" screen. Either way you're ok.
    Enter the phone in DFU mode (You must have the iPhone connected to the computer and iTunes running). To do this, hold the power & the home button down for about 9 seconds.
    Why 9s? Well people say 10s, but it depends how slow you are at counting. Too short and it doesn't work, too long and the apple logo appears.
    When you hit about 6-7s the screen should turn off, leave it for 2 more seconds and release the power button, STILL holding the home button. If all went well, you should NOT see an apple logo, the screen should be dead.
    Keep holding home until windows/Mac informs you that it's found new hardware, OR iTunes tells you that your iPhone is in recovery mode. Remember, screen should be blank.
    If you see an apple logo, repeat the process for less time until you get it right. Took me a little time.
    Step 4:
    Shift/Option click the restore button in iTunes and select the iPhone1,1_1.1.4 firmware you downloaded.
    Fingers crossed it should restore back to 1.1.4.

Maybe you are looking for