PADES-LTV Document timestamp verification error

Hello,
I have a signed pdf document which includes PADES-LTV signture with a Document timestamp signature.
When I try to open the signed document with Adobe reader version 10.1.0.534, signature is validated however Document timestamp signature can not be verified. It says: At least one signature requires validating on the top bar. When I look at the Signatures section on the left, It says: Signer's identity is invalid because it has expired or is not yet valid. If I try to open the signature details of the document timestamp, Adobe reader crashes. (I submitted a bug report for this issue but I have not received any response yet)
When I open the signed document with Adobe Acrobat X pro and view the details of the document timestamp signature, this value "1970/01/01 03:00:00 +03'00'" is displayed in the signature date field. Actually, Date field should be Not available since ETSI 102 778-4 V1.1.2 says: In the document timestamp dictionary Name, M, Location, Reason and contact info should not be present.
Why does the adobe reader shows this value 1970/01/01 03:00:00 +03'00' instead of Not Available?
What can be wrong?
Thanks

Thanks for answer,
but I don't have a problem with timestamp included inside the signature.
I have a issue with creating Document Time-stamp dictionary.
Document Time-stamp dictionary is a standard Signature dictionary but with some changes.
More details in PADES LTV see specification ETSI TS 102 778-4 V1.1.1 (2009-07) page 15.

Similar Messages

Signing a document, generates a "Timestamp signature property generation error: Verification error."

I am getting this error message when I sign my documents. Especially when I try and create a second or third signature on a document.
I have just upgraded to Reader11.0.09 and then when I got the error, I went back to Reader 11.0.08 and then back to Reader 11.0.07 but all are giving the error. The document gets signed but a pop up box shows the "Timestamp signature property generation error: verification error"
I have the settings pointing to our timestamp server under Preferences > Document Timestamping > Server Settings.
Under signature verification preferences > Verification > Verification time, I have the "Secure time (timestamp) embedded in the signature" selected.
It seems to work but is generating the error. If I open a new document and sign it sometimes it works without the error. Occasionally it produces the error on first signing. Mostly on second and third signatures on the page..
Any ideas?

you can mail me directly to [email protected], and I'll try to help.
no guarenty :-)
Tal
[email protected]

Code signing and Timestamp Server Error

Warning: I’ve got exactly 2 days experience with AIR
but a client wants to add file IO capabilites to a
touchscreen/Flash application we developed and AIR seems to be our
only choice.
From CS4 I can publish an AIR 1.5 application with a self
signed code certificate but I get the error “Could not
connect to timestamp server”, I can then disable the
timestamp and get the warning: “If the AIR application is not
timestamped, it will fail to install when the digital certificate
expires. Are you sure you want to disable timestamping?” I
can proceed without the timestamp and everything seems to work.
So I’m wondering, when does my certificate expire? I
think I might have read 5 years. What do my clients do if they have
to reinstall the application after 5 years? Make them pay for
another copy ;-) Lastly, how do I avoid the timestamp error? Sign
up with a CA like VeriSign at $500/yr, not gonna happen for just
one client.
Sorry to sound a little testy but I could have written
exactly the same application in Director and not had to worry about
this code signing business.

You need to have a network connection for timestamping to
work. If that network connection uses a proxy server, you may also
need to set up the JRE to use that proxy (See
http://www.java.com/en/download/help/5000020600.xml).
When the certificate expires, the AIR file can't be used
anymore if there is no timestamp.
A timestamp verifies that the certificate was valid when the
AIR file was signed, so the AIR app can be installed even after the
cert expires when a timestamp is present.
Timestamps do not require a Verisign, or any other commercial
certificate. The service is free.

Document protocol identification error

Hi While receving Shipment from our trading partner, it showing below error in b2b, Please help me in resolving this? We are suing Custom document over internet.
Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Enter
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage compInfoList[k].getValue().toLowerCase()==>text/plain
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Components List= [Loracle.tip.adapter.b2b.packaging.ComponentInfo;@4fa23a
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage File Name=>null
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: AS2 Identifier Value: EMRSNS
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage:Payload ï»¿<?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment>
2009.09.15 at 10:31:07:506: Thread-30: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.09.15 at 10:31:07:511: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP EMRSNS
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@23ce9f
2009.09.15 at 10:31:07:597: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
2009.09.15 at 10:31:07:598: Thread-30: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
     at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
     at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:370)
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:598: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:657: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:661: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {CONTENT-TRANSFER-ENCODING=binary, CONNECTION=Keep-Alive, AS2-FROM=BENCHQA, CONTENT-TYPE=application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m", MIME-VERSION=1.0, RECEIPT-DELIVERY-OPTION=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll, AS2-VERSION=1.1, EXPECT=100-continue, USER-AGENT=Microsoft(R) BizTalk(R) Server 2006 R2 3.0.1.0, AS2-TO=EMRSNS, CONTENT-LENGTH=5137, ORACLE-ECID=1253032264:10.236.2.145:16396:0:3376,0, MESSAGE-ID=<ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>, HOST=emersonb2b-s.emrsn.com, B2B_SERVLET_URI_PATTERN=/b2b/transportServlet, DISPOSITION-NOTIFICATION-TO=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll}
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.09.15 at 10:31:07:671: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.09.15 at 10:31:07:684: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 IdentifierEMRSNS
2009.09.15 at 10:31:07:769: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2009.09.15 at 10:31:07:815: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.09.15 at 10:31:07:827: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) Engine:notifyApp Enter
2009.09.15 at 10:31:07:848: Thread-30: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AEC0291123BE8B0DB800000B91B0200</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) Engine:notifyApp Exit
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.09.15 at 10:31:07:861: Thread-30: B2B - (DEBUG) DBContext commit: Enter
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Leave
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Edited by: user8653471 on Sep 15, 2009 10:55 PM

Hi Anuj,
Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
Do above statement is related to EDI? I am using Custom document over internet
I did not find any unreadable/non-xml characters in the xml file, here i am attaching the xml fille.
<?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment>

Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions?

Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions? SecSigner is not responding.

Well, I contacted SecCommerce about the issue, the response was, that I should sign the file later (afterwards). This is a solution, but not the best in my opinion.
When I sign the document the SecSigner window/Java window appears and freezes. Adobe is not responding. I have to terminate Adobe because the program is not responding.
I only found this support website, so I have realized that this is a User 2 User site, but it was a try to get some help.

Error loading BASIC document. General Error. General input/output error".

Error loading BASIC document. General Error. General input/output error".

I guess your problem is related to StarOffice8, right?
I had the same issue after upgrading StarOffice7 to StarOffice8:
http://forum.java.sun.com/thread.jspa?threadID=5287604&tstart=0
Apparently the .StarOffice8 directory in your export/home directory was created based on .StarOffice7
directory. Probably here something went wrong. Maybe a bug.
So the solution is very simple:
rm -r .StarOffice8 in your export/home directory and restart StarOffice8.
Or you can also rename the directory.

Document protocol identification error for custom protocol

Hi,
Working for B2B inbound transaction. By using B2B need to transfer file from remote TP location to Host TP location. The file type is non EDI file (FLAT file of type fixed length) .
I am doing given below steps but B2B giving document identification protocol error after file picked for processing.
Document Defination at administration level:
Protocol : Custom
Version : 1.0
DocType : CustomerDoc
DocDef : CustomerDocDef( In these mentioned values as
Identification Type = "Flat"
Identification Start Position = 1,
Identification End Position = 1 ,
Identification Value = 1)
Host Tp set up:
TP Name : Client
EDI INTERCHANGE ID : ClientID
EDI GroupID : ClientID
EDI Interchange ID Qualifier : 01
Listening channel : Client_Deliverychannel
Remote TP setup :
TP Name : Customer
EDI INTERCHANGE ID : CustomerID
EDI GroupID : CustomerID
EDI Interchange ID Qualifier : 02
Document IMPORTED : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
Listening channel : Customer_Listeningchannel
Agrement for the Remote TP 'customer:'
Document using : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
TP names using : Customer , Client
Listening channels using : Customer_Listeningchannel, Client_Deliverychannel
Sample Flat File Using:
1 00123451107200600123456780021000021001500049870USD 0000000000
Thanks&Regards,
Sridhar.Rachumallu.
Edited by: user1133742 on Jun 29, 2010 11:54 PM
Edited by: user1133742 on Jun 30, 2010 12:00 AM

Configuration is looking fine. however error says B2B is not able to identify incoming document.
Please paste/send the log in trace:32 mode for further analysis.
Rgds,
Nitesh Jain
[email protected]

TS1424 All of my books in iBooks have the following message: "this page has the following errors: error on line 1 at column 1 document is empty error on line 1 : encoding error..,...". Any advice?

All of my books in iBooks have the following message: "this page has the following errors: error on line 1 at column 1 document is empty error on line 1 : encoding error..,...". Any advice?

I have the same problem. I've tried to restart my Ipad and downloaded the book again several times but nothing has changed. There aren't any reviews on the book with that problem and I've got the latest version of iBook so I don't know what else I can do to get the book which I've paid for. Does anyone have another idea what I could do? (maybe one of the above might help you, Paul)
Thanks

Ibooks Error This page contains the following errors: error on line 1 at column 1: Document is empty error on line 1 at column 1: Encoding error Below is a rendering of the page up to the first error

I am getting this error with my latest Ibook,
This page contains the following errors:
error on line 1 at column 1: Document is empty error on line 1 at column 1: Encoding error
Below is a rendering of the page up to the first error
Can anyone offer a fix?
Thanks
Paul

I have the same problem. I've tried to restart my Ipad and downloaded the book again several times but nothing has changed. There aren't any reviews on the book with that problem and I've got the latest version of iBook so I don't know what else I can do to get the book which I've paid for. Does anyone have another idea what I could do? (maybe one of the above might help you, Paul)
Thanks

Email verification error

Ever since the latest update, I'm receiving this error when trying to setup an additional email account:
"Verification error Failed to verify email accounts from this device. All accounts will be deleted."
The options are "Yes" or "No"
Obviously, I'm not going to say "yes" to delete all accounts. Any fix for this problem???

Thanks for your reply.
The phone is used for business so the problem had to be resolved quickly. I called Verizon Support and was told to back up contacts and do a master reset and then reset all email accounts.
Best regards,
Carolyn
Logo
Brackett Imports, Inc.
T. 508-428-8887 · F. 508-428-8855
[email protected]

Rosettanet--document protocol identification error

Hi guys,
i am trying inbound operation using oracle Rosettanet standard(3a4) i have taken PO request XSD and Input XML from Oracle sample Rosettanet-004 i am getting document protocol identification error i have changed the GlobalBusinessIdentifier value for buyer and seller according to my duns values. Still any values i have to change?
can any one help on this?
thanks in advance...

Hi,
Here is my wire message payload..
*<?xml version="1.0" encoding="UTF-8"?>*
*<Pip3A4PurchaseOrderRequest xmlns="http://www.edifecs.com/RosettaNet/100PO">*
*<fromRole>*
*<PartnerRoleDescription>*
*<ContactInformation>*
*<contactName>*
*<FreeFormText>Kerri Makela</FreeFormText>*
*</contactName>*
*<EmailAddress>Not Available</EmailAddress>*
*<telephoneNumber>*
*<CommunicationsNumber>4805521413</CommunicationsNumber>*
*</telephoneNumber>*
*</ContactInformation>*
*<GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>927775478</GlobalBusinessIdentifier>*
*<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</fromRole>*
*<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>*
*<PurchaseOrder>*
*<AccountDescription>*
*<accountName>*
*<FreeFormText>INTEL CORP</FreeFormText>*
*</accountName>*
*<AccountNumber>035219007</AccountNumber>*
*<billTo>*
*<PartnerRoleDescription>*
*<ContactInformation>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>ACCOUNTS PAYABLE</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>P.O. Box 1000</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>Hillsboro</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550001</GlobalLocationIdentifier>*
*<NationalPostalCode>97123-100</NationalPostalCode>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</ContactInformation>*
*<GlobalPartnerRoleClassificationCode>Payer</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>INTEL CORP</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</billTo>*
*</AccountDescription>*
*<comments>*
*<FreeFormText>THIS PURCHASE ORDER CONFORMS TO THE TERMS AND__CONDITIONS SET FORTH IN CONTRACT. THE PARTIES HEREBY AGREE__TO AMEND SAID CONTRACT, FOR THIS ORDER ONLY, BY INCORPORATING THE NON__CONFLICTING TERM BELOW:__PARTIAL SHIPMENTS WILL NOT BE ACCEPTED. SHIP COMPLETE__PLEASE CONFIRM THIS ORDER BY SIGNING ON THE SIGNATURE__LINE BELOW AND RETURNING A COPY TO BUYER.__SIGNATURE DATE__THE TOOL ID, PURCHASE ORDER NUMBER, LINE ITEM AND__RELEASE, CRATE/BOX OF WILL BE ON THE PACKING SLIP__ATTACHED TO THE BILL OF LADING AND WRITTEN OR STAMPED__ON EACH CRATE/BOX OR CRATES/BOXES. THE TOOL ID,__PURCHASE ORDER, LINE ITEM AND RELEASE, WILL BE ON EACH__INVOICE TO ENSURE PROMPT AND CORRECT PAYMENT__SHIP VIA:__UVL REPRESENTATIVE AT 800-716-6625 OR__FAX: 602-470-0345__Danzas-AEI REPRESENTATIVE: GREGG TEUNISSEN:(31)(20)316-9754 OR FAX:__(31)(20)316-9898__KWE REPRESENTATIVE ICHIRO FURUSAWA:(81)(3)5443-4510 OR__FAX: (81)(3)5443-4515__SELLER WILL PROVIDE THE CARRIER WITH THE FOLLOWING INFORMATION:__PURCHASE ORDER NUMBER, LINE ITEM NUMBER AND RELEASE__NUMBER, TOOL IDENTIFIER FOR EACH PART NUMBER, TOOL__IDENTIFIER FOR EACH SYSTEM TO BE SHIPPED, DATE AND TIME__THE SYSTEM(S) WILL BE AVAILABLE FOR PICKUP; AND__CONFIRMATION OF THE PIECES, DIMENSIONS AND WEIGHTS TO__BE INCLUDED.__.</FreeFormText>*
*</comments>*
*<FinancingTerms>*
*<GlobalFinanceTermsCode>Bank transfer</GlobalFinanceTermsCode>*
*<PaymentTerms>*
*<GlobalPaymentConditionCode>Acceptance</GlobalPaymentConditionCode>*
*<netTermsDays>*
*<CountableAmount>0</CountableAmount>*
*</netTermsDays>*
*<percentDue>*
*<PercentAmount>20</PercentAmount>*
*</percentDue>*
*</PaymentTerms>*
*</FinancingTerms>*
*<GlobalPurchaseOrderTypeCode>Standard</GlobalPurchaseOrderTypeCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<ProductLineItem>*
*<comments>*
*<FreeFormText>.</FreeFormText>*
*</comments>*
*<GlobalProductUnitOfMeasureCode>Each</GlobalProductUnitOfMeasureCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<LineNumber>0010</LineNumber>*
*<OrderQuantity>*
*<requestedQuantity>*
*<ProductQuantity>1</ProductQuantity>*
*</requestedQuantity>*
*</OrderQuantity>*
*<OrderShippingInformation>*
*<CarrierInformation>*
*<GlobalCarrierCode>UVLN</GlobalCarrierCode>*
*</CarrierInformation>*
*<GlobalFreeOnBoardCode>Origin</GlobalFreeOnBoardCode>*
*<GlobalShipmentTermsCode>Collect</GlobalShipmentTermsCode>*
*<GlobalShippingServiceLevelCode>Premium Surface</GlobalShippingServiceLevelCode>*
*<SpecialHandlingInstruction>*
*<specialHandlingText>*
*<FreeFormText>Carrier Name : UVL Capital - Fob Text: EXW Amatpos;s Dock</FreeFormText>*
*</specialHandlingText>*
*</SpecialHandlingInstruction>*
*</OrderShippingInformation>*
*<ProductIdentification>*
*<PartnerProductIdentification>*
*<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>*
*<ProprietaryProductIdentifier>DESCRIPTION:PreFac Kit</ProprietaryProductIdentifier>*
*</PartnerProductIdentification>*
*</ProductIdentification>*
*<ProductSubLineItem>*
*<GlobalProductUnitOfMeasureCode>Each</GlobalProductUnitOfMeasureCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<OrderQuantity>*
*<requestedQuantity>*
*<ProductQuantity>1</ProductQuantity>*
*</requestedQuantity>*
*</OrderQuantity>*
*<OrderShippingInformation>*
*<CarrierInformation>*
*<GlobalCarrierCode>UVLN</GlobalCarrierCode>*
*</CarrierInformation>*
*<GlobalFreeOnBoardCode>Origin</GlobalFreeOnBoardCode>*
*<GlobalShipmentTermsCode>Collect</GlobalShipmentTermsCode>*
*<GlobalShippingServiceLevelCode>Premium Surface</GlobalShippingServiceLevelCode>*
*<SpecialHandlingInstruction>*
*<specialHandlingText>*
*<FreeFormText>Carrier Name : UVL Capital - Fob Text: EXW Amaapos;s Dock</FreeFormText>*
*</specialHandlingText>*
*</SpecialHandlingInstruction>*
*</OrderShippingInformation>*
*<requestedEvent>*
*<TransportationEvent>*
*<DateStamp>20020311Z</DateStamp>*
*<GlobalTransportEventCode>Dock</GlobalTransportEventCode>*
*</TransportationEvent>*
*</requestedEvent>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>2501 N.W. 229th</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>Attn: D1C</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>HILLSBORO</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550D1C</GlobalLocationIdentifier>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</PartnerDescription>*
*</shipTo>*
*<subLineItem>*
*<LineNumber>1</LineNumber>*
*</subLineItem>*
*</ProductSubLineItem>*
*<requestedEvent>*
*<TransportationEvent>*
*<DateStamp>20020311Z</DateStamp>*
*<GlobalTransportEventCode>Dock</GlobalTransportEventCode>*
*</TransportationEvent>*
*</requestedEvent>*
*<requestedUnitPrice>*
*<FinancialAmount>*
*<GlobalCurrencyCode>USD</GlobalCurrencyCode>*
*<MonetaryAmount>0</MonetaryAmount>*
*</FinancialAmount>*
*</requestedUnitPrice>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>2501 N.W. 229th</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>Attn: D1C</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>HILLSBORO</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550D1C</GlobalLocationIdentifier>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</PartnerDescription>*
*</shipTo>*
*<TaxExemptStatus>*
*<isTaxExempt>*
*<AffirmationIndicator>Yes</AffirmationIndicator>*
*</isTaxExempt>*
*<TaxExemption>*
*<GlobalTaxExemptionCode>Exempt - per State law</GlobalTaxExemptionCode>*
*<taxExemptionCertificationIdentifier>*
*<ProprietaryReferenceIdentifier>Not Available</ProprietaryReferenceIdentifier>*
*</taxExemptionCertificationIdentifier>*
*</TaxExemption>*
*</TaxExemptStatus>*
*</ProductLineItem>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</shipTo>*
*</PurchaseOrder>*
*<thisDocumentGenerationDateTime>*
*<DateTimeStamp>20020307T002254.760Z</DateTimeStamp>*
*</thisDocumentGenerationDateTime>*
*<thisDocumentIdentifier>*
*<ProprietaryDocumentIdentifier>pip3a4_po_id1</ProprietaryDocumentIdentifier>*
*</thisDocumentIdentifier>*
*<toRole>*
*<PartnerRoleDescription>*
*<GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>*
*<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</toRole>*
*</Pip3A4PurchaseOrderRequest>*
I cant see any junk characters or BOM in my Payload..

An error occurred: Save document failed / An error occurred while saving the document: PATH (HDB 00055)

Hello Colleagues, I am creating an analysis in build 576, everything goes well, the algorithm calculates the needed values, but when I try to save the analysis, I receive the following error message: "An error occurred: Save document failed / An error occurred while saving the document: <PATH> (HDB 00055)".
Does anyone know what could cause this error message?
Thanks a lot for any hint.
Sergey

Hi Henry,
I am using PA 1.0.11 and received this error; any update on this fix for SAP PA. Does this happen for a particular data source.
I am currently using Excel as source and whenever I try to use this data; I get this even if I move the data to a new file or rename a file. I tried to check the same issue with a different file and it works fine. This file worked fine a day back.
Please let me know if this is unusual for this version.
Regards,
Arvind E

Ime I try to open a document I get : Error getting License. License Server Communication Problem: E_STREAM_ERROR:

Every time I Try to open a document I get: Error getting License. License Server Communication Problem: E_STREAM_ERROR:

do you have a compatible os for the ade version you're trying to use?
ie, what os/what ade version?

Error Message - Reference number of a document from Back Error

Hi,
I created proforma invoice but it is not transferred to GTS. I tried to transfer manually, status shows it is released but there is an error at the top saying 'Reference number of a document from Back Error'. When I checked it in GTS, there is no custom document for proforma invoice. I checked configuration in ECC as well as GTS regarding activation of BADis, document types etc. everything looks fine. Can you please help me where to look at it and get it solved?
Thanks in advance.

Hi Manohar,
Are you trying to create an Export Declaration? If so, is this the first time, or has it worked ok previously but failed this time?
In case it's the first time, have you made sure that:
The Billing Type is set for transfer to GTS?
The Billing Type is mapped in GTS?
The Item Category is mapped in GTS?
The proforma is actually an export (Shipping Point and Ship-to address not both in the EU)?
Do you see any related entries in Transaction SM58?
Do you see any related log entries in the GTS transfer log?
Regards,
Dave

Document 5100082865 saved (error in account determination).

When I am creating credit memo System through error message Document 5100082865 saved (error in account determination).
What could be the reason..

To resolve the error, you can analyze account determination in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account Determination (first option)
This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
Possible SD errors:
1. VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.
2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
Solution:
Option 1 (Standard solution):
step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
step 2: Maintain Customer master / Material Master correctly.
step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
Option 2:
Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
3. Account Key not maintained in Pricing Procedure:
Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client ot uploaded through LSMW / SCATT / BDC.
In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:
1. G/L account not found
2. Cost Element not maintained for G/L account.
In both the above cases, FI consultant requires to take corrective action.
Regards,
Rajesh Banka
Reward points for suitable responses to Promote Food Distribution Program.

PADES-LTV Document timestamp verification error

Similar Messages

Maybe you are looking for