Duplicated exchange protocol message error on Remote TP implement Sync Res
I am (MyCompany) send the business message and receive the corresponding business response from remote TP, but got error as the following,
Error Code B2B-50081
Error Description Machine Info: ( Acme) Description: Duplicated exchange protocol message error - Original B2BMessageId = C0A802111322965DEA30000050D092D0-1
I need your help!
Regards,
San
Anuj,
this is message id send to remote TP
Id C0A80211132296566E80000050D091E0
Message Id C0A80211132296564FA0000050D09120
Business Message C0A80211132296566D80000050D09170
Packed Message Packed Message
Payload Payload
Protocol Message Id @C0A80211132296566E10000050D091A0
Refer To Protocol Message Id
Protocol Collaboration Id @C0A80211132296566E10000050D091A0
Protocol Transport Binding SOAPAction="ebXML" http.sync=true timeout=300000 Content-Type=multipart/related;type="text/xml";boundary="----=_Part_65_1555520695.1314954503907";start="<ebxheader-C0A80211132296566E00000050D09190>" Content-Length=2483
Message Digest Message Digest
Digest Algorithm
Transport Protocol HTTP
Transport Protocol Version 1.1
And message id received from remote TP
Id C0A802111322965DE260000050D09280
Message Id C0A802111322965DE260000050D09280
Business Message C0A802111322965DEA40000050D092E0
Packed Message Packed Message
Payload Payload
Protocol Message Id M1314954587133.5826024@tcgws02_te4502442803846285853
Refer To Protocol Message Id @C0A80211132296566E10000050D091A0
Protocol Collaboration Id @C0A80211132296566E10000050D091A0
Protocol Transport Binding SOAPAction="ebXML" User-Agent=haboob/5.5.1.0.1 build-2636 Host=xx.xx.xx.xx:xxxx Content-Type=multipart/related; type="text/xml"; boundary="----=_Part_30558_29196552.1314954587139" Connection=close Content-Length=3237 MSG_RECEIVED_TIME=Fri Sep 02 16:08:54 ICT 2011
Message Digest Message Digest
Digest Algorithm
Transport Protocol HTTP
Transport Protocol Version 1.1
Thanks for your help.
San
Edited by: user7914871 on ๓ ก.ย. ๒๕๕๔, ๑๑:๔๙ น.
Edited by: 7914871 on ๕ ก.ย. ๒๕๕๔, ๑๔:๑๓ น.
Similar Messages
-
B2B-50081 Duplicated exchange protocol message error
Hi,
I tested a scenario for ebXML inbound type. for the first time it worked correctly with no errors. i got instance created in my soa composite. but from the next time, even though i changed the input xml file name with unique message id, i'm getting the following error after acknowledgement or between the acknowledgement.
Please help me to solve the issue.
I'm naming the input xml as follows : <fromTradingPartner>_<DocumentType>_<Revision>_<msgType>_<msgId>.xml
Eg:OracleServices_ebXMLType_204_1_210820128.xml
Error
Id 7F00000113948EE1E4B000002F2BA9C9
Message Id 7F00000113948EE1E26000002F2BA9C5
Refer To Message Refer To Message
Sender Type
Sender Value
Receiver Type Name
Receiver Value MarketInc
Sender
Receiver MarketInc
Agreement Id
Agreement
Document Type
Document Protocol
Document Version
Message Type REQ
Direction INBOUND
State MSG_ERROR
Acknowledgement Mode NONE
Response Mode ASYNC
Send Time Stamp 08/21/2012 04:55:28 PM
Receive Time Stamp 08/21/2012 04:55:28 PM
Document Retry Interval(Channel) 0
Document Remaining Retry(Channel) 0
Document Retry Interval(Agreement)
Document Remaining Retry(Agreement)
Native Message Size 0
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
Correlation To XPath Value
Correlation To XPath Expression
Wire Message Wire Message
Application Message Application Message
Payload Storage Payload Storage
Attachment Attachment
Label
Collaboration Id
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name Generic HTTP
Exchange Protocol Version 1.1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code B2B-50081
Error Description Machine Info: (localhost.localdomain) Description: Duplicated exchange protocol message error - Original B2BMessageId = 7F00000113948EE1D1B000002F2BA9BF
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Duplicated exchange protocol message errorI tried simple ebXML inbound use case only.
1.I created custom ebXML 2.0 document definition
2.created eBMS Channel for remote TP.
3.created Generic File Channel for host TP
3.created an agreement in the remote TP with these two channels and the document definition
4.Created a soa project in the jdeveloper with B2B adapter as sender(inbound), mediator to transform the xml to opaque(for .dat format) and then a JMS adapter as producer to put the the .dat file.
I tried this in 2 different ways:
If i configured the agreement without using the host channel (no channel for host and ebms channel for remote), instance for soa is been created with error since it is unable to convert to opaque format.
If i configured the agreement using the host channel (file channel for host and ebms channel for remote), no instance is been created in the soa but i can able to see the .dat file in the file channel's folder.In the reports page, msg and ack are generated correctly with one more error "duplicated protocol error".
Please help. -
Warning -: AIP-50082: Duplicated Exchange protocol message error
Hi,
I am facing this warning while sending Outbound Rosettanet messages to Oracle b2B.
Warning -: AIP-50082: Duplicated Exchange protocol message error
Even after this warning, the messages are getting exchanged with the trading partner. The B2B report shows message state as "Complete".
The issue is very similar to the following thread.
[t-701140]
I tried entering values to "b2b_event" table manually. It first says that "The row is created". However, It is not actually getting created in the table.
Can you please help me with this issue?
Regards,
Ravi ShahHi Ramesh,
Thanks a lot for your response.
The Duplicate Exchange protocol message error issue is now resolved for RNIF. You suspected the duplicate MSG_ID to be the cause and it was. Though the back-end Java stub was updating the MSG_ID, that wasn't picked up by the B2B. This resulted in the same MSG_ID from the properties file being picked up for every message.
After rectifying the back-end Java stub code, this issue was resolved and no errors were found for the nearly 500 messages that were enqueued onto the JMS. Further, the throughput was found to be 4-6 MPS on Windows Env.
Thanks again!
Warm Regards,
Suhas. -
AIP-50081 Duplicated exchange protocol message.
I am trying to build the X12 Internet configuration sample.
I could send the 850 document successfully to GlobalChip Trading partner. but in the response the acknowledgement 997 throws an Exception.
GloblaChips Log file:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2008.11.07 at 09:47:20:671: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2008.11.07 at 09:47:20:687: Thread-10: 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>C0A8006411D776BEAF200000190A1210</b2bMessageId>
<errorCode>AIP-50081</errorCode>
<errorText>Duplicated Exchange protocol message error</errorText>
<errorDescription>
<![CDATA[Machine Info: (xpone)
Duplicated exchange protocol message - Original B2BMessageId = C0A8006411D776BE62F00000190A11E0 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Acme Log file :
2008.11.07 at 09:47:13:296: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2008.11.07 at 09:47:13:296: Thread-10: 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>C0A8006411D776BC7AB0000093DF5600</b2bMessageId>
<errorCode>AIP-50079</errorCode>
<errorText>Transport error: [IPT_HttpSendConnectionRefused] HTTP connection is refused.
Connection refused: connect</errorText>
<errorDescription>
<![CDATA[Machine Info: (xpone)
Transport error: [IPT_HttpSendConnectionRefused] HTTP connection is refused.
Connection refused: connect ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Thanks
Edited by: user780436 on Nov 7, 2008 7:02 AMHi,
Please let us know whether b2b handles FA? or FA generated from Backend Application?
If FA generated from Backend Application, Make sure the Message ID is unique.
Regards
Nandagopal.S -
Error Code: AIP: 50080: Exchange protocol identification error
Hi,
I have setup a business action to process EDI X12 850 (PO) document version 4010 over EDI X12 over Internet - HTTP. To simulate the Trading Partner sending the EDI data to us I have developed a test.html page to submit the EDI data. The test.html does a http post to the b2b/transportServlet. When I do this I get the following error:
AIP: 50080 Exchange protocol identification errorMy Business Action
setup look like this:
BUSINESS ACTION:
Create Business Action : Review for 850
Business Protocol : EDI X12 over Internet
Process Protocol : B2B
Process Protocol Revision : B2B Process - 1.0
General
Name :Process_850
Revision :1.0
Document Protocol Revision
Name :X12_4010
Revision :4010
Document Type
Document Type :850
Document Definition :850_Def
Create Business Action : Review
Business Protocol :EDI X12 over Internet
Process Protocol :B2B
Process Protocol Revision :B2B Process - 1.0
General
Name :Process_997
Revision :1.0
Document Protocol Revision
Name :X12_4010
Revision :4010
Document Type
Document Type :997
Document Definition :997_Def
Create Trading Partner : Review
General
Name :ACME
Operational Capability
Business Protocol :EDI X12 over Internet
Business Action :Process_850
Use Default Document Protocol Parameters :false
Use Default Document Definition :true
Communication Capability
Delivery Channel :ACME_X12_DC
Document Exchange :ACME_X12_DocEx
Exchange Protocol Revision :AS2 - 1.1
Transport :ACME_X12_Transport
Transport Protocol :HTTP
Transport Server :ACME_X12_Transport_Server
Trading Partner :ACME
Business Protocol :EDI X12 over Internet
Details
Business Action :Process_997 - Responder
Is Initiator :false
Functional acknowledgement required? :false
Is acknowledgement handled by Integration B2B? :true
Document Information
Document Protocol :EDI_X12
Document Protocol Revision :X12_4010
Document Type :997
Document Definition
Document Protocol Parameters
Name Value
Interchange Time #SystemTime(HHMM)#
Interchange ecs File
Security Information Qualifier 00
Security Information
Authorization Information
[ Application Receiver's Code ] ACME
Interchange Control Standard/Repetition Separator U
Segment Delimiter 0x27
Interchange Date #SystemDate(YYMMDD)#
Authorization Information Qualifier 00
[ Application Sender's Code ] ACME
ImplementationClass oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin
[ Interchange Sender ID Qualifier ] ZZ
Replacement Character 0x7c
Subelement Delimiter 0x2b
Interchange Control Version Number 00200
[ Interchange Sender ID ] ACME
[ Interchange Receiver ID Qualifier ] ZZ
Tag Delimiter 0x3d
Usage Indicator P
[ Interchange Receiver ID ] ACME
Version/Release/Industry Identifier Code
Component Element Separator 0x2b
Decimal Separator 0x2e
Functional Group Time #SystemTime(HHMM)#
Responsible Agency Code X
Functional Group Date #SystemDate(CCYYMMDD)#
Group ecs File
Element Delimiter 0x7e
Create Trading Partner : Review
General
Trading Partner :GLOBALCHIPS
Communication Capability
Delivery Channel :GLOBALCHIPS_X12_DOC
Document Exchange :GLOBALCHIPS_X12_DocEx
Exchange Protocol Revision :AS2 - 1.1
Transport :GLOBALCHIPS_X12_Transport
Transport Protocol :HTTP
Transport Server :GLOBALCHIPS_X12_Transport_Server
Confirmation
Trading partner participant successfully added.
Agreement Details: X12_Agreement
Details
Agreement Id X12_1001
Description
Effective From Date
Effective To Date
Invocation Limit
Concurrent Conversations
Trading Partner Participants
ACME - Process_850 - Initiator
GLOBALCHIPS - Process_850 - Responder
GLOBALCHIPS - Process_997 - Initiator
ACME - Process_997 - Responder
If I tried to use enq_850 I am getting the following error:
AIP-50547 : Trading partner agreement not found for the given input values: From party[NAME] "GLOBALCHIPS", To party[NAME] "GLOBALCHIPS", Business action name "Process_850"; also verify agreement effectiveToDateHi Ramesh,
I have created Internal Deliver Channel as File Inbound for the Host Trading Partner and at the time of creating the agreement between the partners I have selected this channel.
And I am keeping the EDI document in the end point folder. I am giving the file name as XXX_850_4010_1_12345.dat.
Now I am not getting General validation error. This time I am getting the below error.
Please Let me know If my approch is correct?
Error Brief :
5000: Parser error - Missing trailer.
5042: Parser error - No matching parser schema was found.
Error Brief :
5000: Parser error - Missing trailer.
5042: Parser error - No matching parser schema was found.
iAudit Report :
<?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{BACD5C1A-90BE-4D6D-8F48-97E66EE909B6}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Friday, January 12, 2007</ExecutionDate> <ExecutionTime>02:26:40 PM (India Standard Time)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>2</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">2</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath>D:\OraASRel2\ip</FilePath> <FileName/> <LastModified/> <FileSize/> <DataURL>file:\\D:\OraASRel2\ip</DataURL> </DataFile> <Interchange Guid="{A87B69C1-43E3-423B-AA44-9F0C3BE37CF3}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>951</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">ZZ</Link> <Link Name="InterchangeSenderID">BLUECHIPS </Link> <Link Name="InterchangeReceiverQual">12</Link> <Link Name="InterchangeReceiverID">colourchips </Link> <Link Name="InterchangeControlVersion">00300</Link> <Link Name="Standard">X12</Link> </Links> <Properties> <Property Name="InterchangeAuthorizationInfoQual">00</Property> <Property Name="InterchangeAuthorizationInfo"> </Property> <Property Name="InterchangeSecurityInfoQual">00</Property> <Property Name="InterchangeSecurityInfo"> </Property> <Property Name="InterchangeSenderQual">ZZ</Property> <Property Name="InterchangeSenderID">BLUECHIPS </Property> <Property Name="InterchangeReceiverQual">12</Property> <Property Name="InterchangeReceiverID">colourchips </Property> <Property Name="InterchangeDate">061207</Property> <Property Name="InterchangeTime">1601</Property> <Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property> <Property Name="InterchangeControlVersion">00300</Property> <Property Name="InterchangeControlNumber">000050524</Property> <Property Name="InterchangeAckRequested">1</Property> <Property Name="InterchangeUsageIndicator">P</Property> <Property Name="InterchangeComponentElementSep">0x2a</Property> <Property Name="DecimalSeparator"/> <Property Name="ElementDelimiter">0x7e</Property> <Property Name="ReleaseCharacter"/> <Property Name="RepeatingSeparator"/> <Property Name="SegmentDelimiter">0x2b0xd0xa</Property> <Property Name="SubelementDelimiter">0x2a</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{BF922FB1-9661-462C-B5A6-D868869A8C79}" FunctionalGroupAckCode="R" TransactionSetsIncluded="1" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>108</StartPos> <Size>843</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="GroupSenderID">BLUECHIPS</Link> <Link Name="GroupReceiverID">colourchips</Link> <Link Name="GroupVersionNumber">004010</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> <Property Name="GroupSenderID">BLUECHIPS</Property> <Property Name="GroupReceiverID">colourchips</Property> <Property Name="GroupDate">20061207</Property> <Property Name="GroupTime">1601</Property> <Property Name="GroupControlNumber">150524</Property> <Property Name="GroupAgencyCode">X</Property> <Property Name="GroupVersionNumber">004010</Property> <Property Name="GroupChildCount">1</Property> <Property Name="GroupTrailerControlNumber">150524</Property> </Properties> </NodeInfo> <Transaction Guid="{367C24CC-9747-4E49-9F02-AFC4295CF850}" TransactionAckCode="R" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>171</StartPos> <Size>766</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="TransactionID">850</Link> </Links> <Properties> <Property Name="TransactionID">850</Property> <Property Name="TransactionControlNumber">158192</Property> <Property Name="TransactionImplementationReference"/> <Property Name="TransactionChildCount">26</Property> <Property Name="TransactionTrailerControlNumber">158192</Property> </Properties> </NodeInfo> </Transaction> </FunctionalGroup> <InterchangeErrors> <Error ErrorCode="{03942C04-7909-4DFB-8F7D-6E5B3D8BDF48}" Severity="Normal" Category="Rejecting" Index="1" ID="50000200"> <ErrorBrief>5000: Parser error - Missing trailer.</ErrorBrief> <ErrorMsg>The Interchange Trailer is missing. The segment itself may be missing or the Segment Delimiter may be missing.{br}{br}Trailer was expected after:{br}{tab}Character: 952 </ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">1</Parameter> <Parameter Name="Name">Parser</Parameter> <Parameter Name="_ec_CaseID">02</Parameter> <Parameter Name="_ec_dn_guid_">{A87B69C1-43E3-423B-AA44-9F0C3BE37CF3}</Parameter> <Parameter Name="_ec_start_pos_">952</Parameter> <Parameter Name="ec_error_scope">File</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <Part3/> <DataXPointer> <StartPos>952</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </InterchangeErrors> </Interchange> <AnalyzerErrors> <Error ErrorCode="{9EE55FDF-8668-4499-9F2E-D9247519A850}" Severity="Normal" Category="Rejecting" Index="2" ID="50420000"> <ErrorBrief>5042: Parser error - No matching parser schema was found.</ErrorBrief> <ErrorMsg>The data starting at position 951 is not a valid EDI interchange. The remainder of the data file was ignored.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">Parser</Parameter> <Parameter Name="_ec_start_pos_">951</Parameter> <Parameter Name="ec_error_scope">File</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>951</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </AnalyzerErrors></AnalyzerResults>
2007.01.12 at 14:26:40:779: Thread-12: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2403)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1263)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1845)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1777)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1735)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:455)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:327)
at java.lang.Thread.run(Thread.java:534)
Thanks
Raghu -
Unable to identify the exchange protocol of the message (sync AS2 MDN)
Hi,
We got the following error:
Description: Unable to identify the exchange protocol of the message
StackTrace:
Error -: AIP-50080: Exchange protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1367)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2370)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1813)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1152)
at oracle.tip.adapter.b2b.xmlgwIntg.XMLGWIntegration.raiseOutboundMessage(XMLGWIntegration.java:168)
at oracle.tip.adapter.b2b.xmlgwIntg.Outbound.onMessage(Outbound.java:297)
at oracle.jms.AQjmsListenerWorker.dispatchOneMsg(AQjmsListenerWorker.java:316)
at oracle.jms.AQjmsListenerWorker.run(AQjmsListenerWorker.java:129)
at java.lang.Thread.run(Thread.java:534)
Here is the Wire message (sync MDN)
=======================
Message-ID=<23033756.391232032071968.JavaMail.SYSTEM@INUBITTEST>
Subject=Your ORDERS AS2
[email protected]
Content-Length=1347
MIME-Version=1.0
Server=Apache
Date=Thu, 15 Jan 2009 15:07:52 GMT
Content-Type=multipart/mixed; boundary="----=_Part_53998_23619909.1232032071968"
[email protected]
------=_Part_53998_23619909.1232032071968
Content-Type: text/plain; charset=UTF-8; name=test.txt
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=test.txt
Message-ID: <17080722.371232032071906.JavaMail.SYSTEM@INUBITTEST>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=disposition-notification;
boundary="----=_Part_53997_14786767.1232032071906"
AS2-Version: 1.1
AS2-From: test_AS2
AS2-To: as2me
------=_Part_53997_14786767.1232032071906
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MDN for Message ID: <33156:4:0:137@as2me>
From: as2me
To: test_AS2
Received on: Thu, 15 Jan 2009 16:07:51 +0100
Status: processed
Comment: This is not a guarantee that the message has
been completely processed or unterstood.
------=_Part_53997_14786767.1232032071906
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: inubit Integration Server
Original-Recipient: rfc822; test_AS2
Final-Recipient: rfc822; test_AS2
Original-Message-ID: <33156:4:0:137@as2me>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: 5kFOLMXOUurpm6DUTA8IMRj5gcs=, sha1
------=_Part_53997_14786767.1232032071906--
------=_Part_53998_23619909.1232032071968--
============================
The communication with our TP is going well, we are able to send, receive messages over AS2 and send back MDN, but we are not able
to receive their MDN.
Edit:
It seems that after the latest MLR patch, the error changed to [IPT_HttpSendError] HTTP encounters send error :. Premature EOF encounter but the roots seem to lead to the problem with MDN as B2B is sending the message a couple of times now and gives the mentioned EOF error.
Please advise,
Thank you
Edited by: Kamil Zadora on Jan 30, 2009 3:44 AMHi Ramesh,
Yes, agreement uses AS2 IDentifiers. Incoming messages are recognized correctly, and we send back sync MDN that is correctly received by our TP. They also recieve our messages correctly although Oracle B2B does not recognize the MDN from them. I think that this causes that, now after applying the latest MLR patch, B2B tries to send it around 6 times and gives the Unexpected EOF error.
Thank you for your help in advance,
Kind regards, -
Identify the exchange protocol of the message
Hi,
I have created a business action, a Trading partner and deployed a Agreement for a partner. On the other side, i have a jsp which post message through HTTP protocol.
Whenever i try to post a Message to the B2B through the jsp, the Error status reports page shows me the error as,
"Unable to identify the exchange protocol of the message".
Has anyone faced a similar problem?Hi Nandagopal,
I tried to find the b2b.log, but it was not available in the path, oracle_home\ip\logs\b2b. But there were some error in the log.xml, which i have mentioned below,
AIP-50080: Exchange protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:972)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:436)
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4442)
at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3092)
at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:2983)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:973)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
AIP-50031: B2B adapter general error: java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4495)
at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3092)
at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:2983)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:973)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:436)
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4442)
... 9 more
Wat do i need to do for getting the b2b.log. I cud not find the ui.log also. Can u pls explain? -
Error in remote call of destination PROCESS_CHAIN
Dear All,
I am getting following error in transport of prcocess chains from DEV to QA.
Error Message :
Error in remote call of destination PROCESS_CHAIN
Message no. RSPC051
Diagnosis
The following error occurred during the remote function call for destination PROCESS_CHAIN:
Name or password is incorrect (repeat logon)
System Response
A short dump has probably been written in the other system.
Procedure
Look at the short-dump overview in the other system.
Please help!!
Regards
RakeshHi Rakesh,
It's a BASIS problem. After transport during process chain activation, the background user tries to logon with the password and if it fails the chain will not be activated. The contents will be transported though. You can manually activate the chain. You can request the Basis guys to fix this.
- Ram -
AIP-52251: Error identifying remote trading partner at MLLP Exchange with
used HL7 over MLLP, one trading partner is EAI(B2B Localhost), another is EchoServer(a java application, the hostname is is4-nb4.corp.ha.org.hk). used a script to enqueue message. like below:
DECLARE
enqueue_options dbms_aq.enqueue_options_t;
message_properties dbms_aq.message_properties_t;
msg_handle RAW(16);
ipmsg b2b.IP_MESSAGE_TYPE;
xml_clob clob;
msg_id number(10);
subscribers dbms_aq.aq$_recipient_list_t;
BEGIN
select message_seq.nextval into msg_id from dual;
xml_clob := '<?xml version="1.0" ?><ADT_A01 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.3.1" CreatedDate="2005-08-16T16:52:26" CreatedBy="ECXEngine_826" GUID="{1A2726C6-B00E-DA11-8F7A-080020C8D296}"><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>EDI</HD.1></MSH.3><MSH.4><HD.1>PWH</HD.1></MSH.4><MSH.5><HD.1>EchoPac</HD.1></MSH.5><MSH.6><HD.1>PWH</HD.1></MSH.6><MSH.7><TS.1>20050804162010</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>ADT</MSG.1><MSG.2>A01</MSG.2></MSH.9><MSH.10>TEST007</MSH.10><MSH.11><PT.1>#Property(ProcessingID)#</PT.1></MSH.11><MSH.12><VID.1>2.3.1</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13><MSH.14 xsi:nil="true"></MSH.14><MSH.15>AL</MSH.15><MSH.16>ER</MSH.16><MSH.17>#Property(CountryCode)#</MSH.17><MSH.18>ASCII</MSH.18><MSH.19><CE.1>ENG</CE.1></MSH.19></MSH><PID><PID.1>1</PID.1><PID.2 xsi:nil="true"></PID.2><PID.3><CX.1>A0000010</CX.1></PID.3><PID.4 xsi:nil="true"></PID.4><PID.5><XPN.1><FN.1>TEST, Patient 01_10</FN.1></XPN.1></PID.5><PID.6 xsi:nil="true"></PID.6><PID.7><TS.1>20001001</TS.1></PID.7><PID.8>F</PID.8></PID><PV1><PV1.1>1</PV1.1><PV1.2 xsi:nil="true"></PV1.2><PV1.3 xsi:nil="true"></PV1.3><PV1.4 xsi:nil="true"></PV1.4><PV1.5 xsi:nil="true"></PV1.5><PV1.6 xsi:nil="true"></PV1.6><PV1.7 xsi:nil="true"></PV1.7><PV1.8 xsi:nil="true"></PV1.8><PV1.9 xsi:nil="true"></PV1.9><PV1.10 xsi:nil="true"></PV1.10><PV1.11 xsi:nil="true"></PV1.11><PV1.12 xsi:nil="true"></PV1.12><PV1.13 xsi:nil="true"></PV1.13><PV1.14 xsi:nil="true"></PV1.14><PV1.15 xsi:nil="true"></PV1.15><PV1.16 xsi:nil="true"></PV1.16><PV1.17 xsi:nil="true"></PV1.17><PV1.18 xsi:nil="true"></PV1.18><PV1.19><CX.1>10010</CX.1></PV1.19></PV1></ADT_A01>
subscribers(1) := SYS.AQ$_AGENT('b2buser', null, null);
message_properties.RECIPIENT_LIST := subscribers;
ipmsg := b2b.IP_MESSAGE_TYPE (msg_id, null,'EAI','EchoServer','Echo_ADTA01_Process', 'ADT_A01', '2.3.1', 1, xml_clob, null);
dbms_aq.enqueue(queue_name => 'b2b.IP_OUT_QUEUE',
enqueue_options => enqueue_options,
message_properties => message_properties,
payload => ipmsg,
msgid => msg_handle);
commit;
END;
show errors;
then go to the B2B Report tab, can see two message like below
EAI EchoServer MLLP - 1.0 HL7 - 2.3.1 Echo_ADTA01_Process WaitFA 2007年11月12日 星期一 下午05:51:37
Acknowledgement Invalid 2007年11月12日 星期一 下午
and in the log file, like this:
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage Could not find a Trading Partner with MLLP ID = is4-nb4. Please check the Trading Partner Identification section of your Trading Partner
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:247)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage identify trading partner by MLLP Id failed for is4-nb4 with ExceptionError -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:257)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {From=is4-nb4, FromIP=160.19.23.102, FARequired=true, protocolVersion=1.0, ToIP=160.19.55.114, Port=4911, Message-Id=1194861102002-1207274363, protocol=TCP, To=is4wingw02}
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning true
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error Set
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA processed by HL7
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Not creating an ACK for an incoming ACK Message
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA B2BMessage is null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Exit
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA Sent
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 1194861102002-1207274363
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2007.11.12 at 17:51:43:096: Thread-10: 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>A0133772116334587C90000068CD8000</b2bMessageId>
<errorCode>AIP-52251</errorCode>
<errorText>Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4</errorText>
<errorDescription>
<![CDATA[Machine Info: (is4wingw02)
Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Enter
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Transaction.commit()
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Leave
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
here said not find the remote partner, but in B2B server, can ping Echoserver.
what is wrong?Hello again,
I have tried all different combinations with the IP addresses and host names, but to no avail. Then I changed the Trading Partner Identification Type from MLLP Id to Sending Application (one of the customer requirements is to be able to identify the Trading Partner by the combination of Sending App/Sending Facility, since they are running multiple HL7 applications on one host). However, I still see the same error in the log file - for some reason, B2B is still trying to identify the Trading Partner by the MLLP Id. Redeploying the configuration didn't help, the requested identification type is ignored.
Please help! If needed, I can send the B2B log file, but maybe I'm missing something obvious.
BTW, the customer has installed the patch for bug 6439217 on October 10th. The B2B version is 10.1.2.2.0.
Thanks in advance! -
Hi!
We have 5 Exchange 2013 servers and when I’m trying to run a script that includes the cmd-let Get-MessageTrackinglog with StartDate = the first of the month and with EndDate = the end of the month I get the following error message after
a couple of hours. The script is run on the server SERVER01 and goes through the Message Tracking logs of all Exchange servers. I have tried the script on other servers and get the same result.
Processing data for a remote command failed with the following error message: Error occurred during the Kerberos reponse.
[Server=SERVER01, TimeStamp = 918/2014 19:32:34]
For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo
: OperationStopped: (server01.domain.com:String) [], PSRemotingTransportException
+ FullyQualifiedErrorId : JobFailure
+ PSComputerName
: server01.domain.com
I have gone through “about_Remote_Troubleshooting Help topic”, but can’t find anything related to my issue. There is nothing in the Application or the Windows PowerShell log either.
/HenrikHi Henado
Check the time on your Exchange server(s) relative to the DCs and ensure they are in correct sync
Use another account which is assigned the Organization Management permission and log to to the server run the command in shell and see the results
Run
Add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010
Set-Adserversettings -ViewEntireForest $True and then run message tracking command and see the results
If none of the above helps you may need to remove and re-install the WinRM and see the results
Good Luck :)
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com -
Typo in error message from Microsoft Remote Desktop for Mac
Just found a bug in error message from Microsoft Remote Desktop (Version
8.0.9 (Build 25073))Hi Sergey,
Thanks for your feedback, i will update to the product group.
Regards.
Dharmesh Solanki
TechNet Community Support -
Help: Error message "ORA-12560 TNS:Protocol Adapter Error "
I tried to install Oracle 8i EE version 8.1.7 on Windows 2000. Everything is OK until the installation proceeded to installing "Oracle Database Configuration Assistant". At that point, I got an error message "ORA-12560 TNS:Protocol Adapter Error (network not loaded)". I looked up the error message. The cause of the error said: "This error occurs when the SQL*Net driver cannot find the JSB driver because you may have either forgotten to load the JSB driver (for instance MFTP) or used an incorrect TCP_VENDOR key (for example, TCP_VENDOR=NOVLWP).". And the suggested action said: "Load the JSB driver or use the correct TCP_VENDOR key.". I am using a standalone PC with Windows 2000 at home, and the PC does not connect to any network(except that I can dialup to internet via modem). What should I do? I can't understand the error message. Any expert to help me overcome the error?
nulldatabase tnsnames.ora
=========
# TNSNAMES.ORA Network Configuration File: D:\Oracle\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = mohsin-pc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORCL)
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = mohsin-pc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = MODOSE)
(PRESENTATION = http://HRService)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
developer 10g tnsnames.ora
==============
# tnsnames.ora Network Configuration File: D:\Forms\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.132)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = Dedicated)
ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = mohsin-pc)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORCL)
Please tell me what changes I needed
database serivice name is "ORCL'
and my pc name is "mohsin-pc" -
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 PMHi 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> -
%DMVPN-3-DMVPN_NHRP_ERROR: Tunnel0: NHRP Encap Error for Resolution Request , Reason: protocol generic error (7)
I had pre-allocated tunnel ip's to remote spokes , some of them were implemented and put into production. Some of them got the config but the tunnel interfaces were left at shut.
Its because of this reason that the DMVPN HUB keeps getting nhrp request from one of the inactive spokes. Following is the sh ip nhrp extract :-
10.x.x22/32
Tunnel0 created 00:02:58, expire 00:00:06
Type: incomplete, Flags: negative
Cache hits: 7
I just cant seem to find the spoke WAN ip to identify it. I tried debugs but just cant get it.
From HUB:-
Nov 30 10:36:31: %DMVPN-3-DMVPN_NHRP_ERROR: Tunnel0: NHRP Encap Error for Resolution Request , Reason: protocol generic error (7) on (Tunnel: 10.x.x.1 NBMA: 20.x.x.x)
Nov 30 10:36:32: NHRP: Send Resolution Request via Tunnel0 vrf 0, packet size: 86
Nov 30 10:36:32: (F) afn: IPv4(1), type: IP(800), hop: 255, ver: 1
Nov 30 10:36:32: shtl: 4(NSAP), sstl: 0(NSAP)
Nov 30 10:36:32: pktsz: 86 extoff: 52
Nov 30 10:36:32: (M) flags: "router auth src-stable nat ", reqid: 46113
Nov 30 10:36:32: src NBMA: 20.x.x.x.
Nov 30 10:36:32: src protocol: 10.x.x.1, dst protocol: 10.x.x.22
Nov 30 10:36:32: (C-1) code: no error(0)
Nov 30 10:36:32: prefix: 32, mtu: 17912, hd_time: 360
Nov 30 10:36:32: addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0 Nov 30 10:36:31: %DMVPN-3-DMVPN_NHRP_ERROR: Tunnel0: NHRP Encap Error for Resolution Request , Reason: protocol generic error (7) on (Tunnel: 10.x.x.1 NBMA: 20.x.x.x)
So my question is , How do i find out the spoke wan ip , so i can do something about it. For now, its just filling up my logs on HUb router...not good ;-))Hello Marcin,
If tunnel interface is shut no NHRP activity should be going, on top, in debugs you point the hub is sending resolution request, not receiving it.
Agree, I expected the same, but unfortunately this is not the case. Spoke does sent out NHRP requests even with Tunnel status as admin shut.
If your hub does not have NHS, it will not know where to send it's resolution request.
I am still on DMVPN Phase 1, so Spokes dont talk to other spokes yet.
Are you positive that there is nothing that is sending packets towards 10.x.x.22 on hub side (sniffer trace of classyfing ACL on "LAN")?
Other then a spoke, it cant be anthing, as the subnet is dedicted for tunnel interface's.
If you know it's not a misconfig and there is no traffic on hub side initiated to 10.x.x.22, try removing and adding full tunnel configuration. i.e. we want to make sure that crypto socket gets closed and restrated.
I can do this over weekend, but i am sure this is not going to fix the problem, reason being, that the HUB was setup before anything else and then we started migrating spokes from primary legacy gre tunnels to dmvpn tunnel as primary and legacy as a backup.
Guess, I am still looking for the answer...Is there a WAN acl that i can use to filter the successfully migrated spokes and log the deny message as in to know what remote wan ip carries along the tunnel ip of .22 or any other debug ?? -
B2B-51503: General create message error
Currently im doing an exchange using
Exchange Protocol Name ebMS
Exchange Protocol Version 2.0
the current error I'm getting is:
[APP: soa-infra] Error -: B2B-51503: General create message error.[[
Error -: B2B-51503: General create message error.
at oracle.tip.b2b.exchange.ebms.EBMSExchangePlugin.createMessage(EBMSExchangePlugin.java:2171)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1532)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1003)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1533)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:806)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3838)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
looking at the business message detail i can see:
Sender Type ebMS Identifier
Sender Value OracleServices_ebMS
Receiver Type ebMS Identifier
Receiver Value MarketInc_ebMS
Sender OracleServices
Receiver MarketInc
Agreement Id ebMS_O_M_Custom_10_PO
Agreement ebMS_O_M_Custom_10_PO_Agr
Document Type PurchaseOrder
Document Protocol Custom
Document Version 1.0
among other values, so if it recognizes the document, agreement and sender an receiver values, the log doesnt show more than the error as to state why the "create message error".No attachment, I have enabled SSL in weblogic but i'm not using the SSL port yet as i have not been able to solve the issue without security first.
the error log:
####<Sep 27, 2011 3:49:51 PM VET> <Warning> <oracle.soa.mediator.dispatch.db> <GLOBO-ve> <AdminServer> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@ec909c> <<anonymous>> <BEA1-3722DFF1EEA3F59EF9A1> <0000JAgK_qO5yW^5xV_AiW1EWY58000002> <1317154791953> <BEA-000000> <Self Container id expired :ADA0FA81E93D11E0AF5D1DDBA1775284 last renewal time :2011-09-27 15:49:51.953 before expiry interval:300000 ms but not removing it.>
####<Sep 27, 2011 3:50:51 PM VET> <Warning> <oracle.soa.mediator.dispatch.db> <GLOBO-ve> <AdminServer> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@ec909c> <<anonymous>> <BEA1-3838DFF1EEA3F59EF9A1> <0000JAgK_qO5yW^5xV_AiW1EWY58000002> <1317154851984> <BEA-000000> <Self Container id expired :ADA0FA81E93D11E0AF5D1DDBA1775284 last renewal time :2011-09-27 15:50:51.968 before expiry interval:300000 ms but not removing it.>
####<Sep 27, 2011 3:50:52 PM VET> <Error> <oracle.soa.b2b.engine> <GLOBO-ve> <AdminServer> <weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@7c5344> <<anonymous>> <BEA1-383CDFF1EEA3F59EF9A1> <3f3d2d8955322f32:-3abd27e6:132ac5204d9:-8000-0000000000001a6e> <1317154852781> <BEA-000000> <Error -: B2B-51503: General create message error.
at oracle.tip.b2b.exchange.ebms.EBMSExchangePlugin.createMessage(EBMSExchangePlugin.java:2171)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1532)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1003)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1533)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:806)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3838)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51503: General create message error.
at oracle.tip.b2b.exchange.ebms.EBMSExchangePlugin.createMessage(EBMSExchangePlugin.java:2171)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1532)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1003)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1533)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:806)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3838)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
Maybe you are looking for
-
Server boot takes a lot of time due to JMS persistence file store
Hi, We're using WebLogic 9.2 on a windows machine. Recently, we enhanced our application to work with JMS. We're using 2 JMS servers on 2 different servers in a cluster, and working with distributed destinations. We're using file store as our persist
-
I am getting unwanted popup ads about software update for software that I don't have installed. I have an iMac 20", 2009, running 10.10.2 Yosemite. This just started this week. I read that Adobe Flash Player was causing problems with mac's and Window
-
How do I get .csv file of Contacts on iPhone?
I am new to iTunes, but am told I can "easily" load a file of phone contact numbers via iTunes to my new (replacement) iPhone. All I see are music files, video files, but can't find a way to even get my contact file into the iTunes library to be abl
-
RFIDYYWT across company codes produces 1099 with multiple records per TIN
We have multiple company codes that post 1099-MISC relevant payments to a common set of vendors. All payments are processed through our main (paying) company code. All our company codes are one taxable entity to the federal government, with one TIN.
-
I NEED HELP!*weird menu setup thing white screen"read verify scan"*
basically...my dad had to delete everything off the computer and install everything back on again. i installed itunes, and the ipod setup thingy u have to do. when i plugged my ipod in and switched it on it came up with a white screen with a menu on