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]
Similar Messages
-
Error for customer specific Authorization check (User Exit)
Dear Experts,
I am facing a problem in PM.
I have created a maintenace plan for calibration via t code IP42 and mentioned the order type PM05. Scheduling is done for the order. I got the order number.
I have released the order and got the inspection lot number.
While entering the results recording through t code QE17, the reluts are out of the specified range, i have given the valuation Rejected, immediately system is giving an error message as below:
"Error for customer specific Authorization check (User Exit)"
Though there is no user exit activated in the system, this message is coming and not allowing the result recoring for rejection.
If I'm entering the result recording within the specified range, then valuation is Accepted and its allowing to save.
I have checked the following user exits:
QQMA0002: QM: Authorization Check for Entry into Notif. Transaction
QQMA0026: PM/SM: Auth. check when accessing notification transaction.
The above 2 User Exits are not active.
I have also checked a note 429066. But it says incase of any dump for that user exit only its applicable and more over the current version of the system is ECC 6.0 packae 15, where as that note is applicable upto 4.6C.
Please some one help me on this issue.
Thanks and Regards,
Praveen.Dear Pete,
I have cheked with my technical team, There is no hotpacks updated recently. This is the implementaion project I'm in, so performing the cycle for the first time.
Any how I got it solved, in T code QE17, after entering the Inspection lot in next screen goto menu path Settings - User settings - Defects recording mention the reprt type and tick on Reprt type Changable.
At the time of result recording if the valuation is Rejected then it ask for defects recording close that window if not rwequired then save, the error message no longer apperaing now.
Regards,
Praveen -
'BuilHeader not bound' error for custom field added by AET
Hi,
We created a Custom field through AET in IC Web UI Screen
The field is in the Accont Identification screen
But the field is showing 'Buiheader nto bound error' on loading of the screen.
We generated the GETTER and the SETTER Methods for the corresponding field in the context node CONTACT PERSONS of the ICCMP_BP_SEARCH Component.
While Debugging its seen that the
DATA: current TYPE REF TO if_bol_bo_property_access.
if iterator is bound.
current = iterator->get_current( ).
else.
current = collection_wrapper->get_current( ).
endif.
current is not getting populated and thats reason why its giving the 'Buiheader not bound error'
Any suggestions on this will be highly appreciated.
Regards,
Sijo
Edited by: sijokjohn85 on Oct 21, 2009 3:01 PMHi Masood,
I checked the method create_contactpersons but I couldnt find anything unusual there.
The code below is present in the CREATE_CONTACTPERSONS Mehtod of the context class
model = owner->create_model(
class_name = 'ZL_CRMCMP_B_BUPASEARCHB2B_CN01'
model_id = 'ContactPersons' ). "#EC NOTEXT
ContactPersons ?= model.
CLEAR model.
* bind to custom controller
owner->do_context_node_binding(
iv_controller_type = CL_BSP_WD_CONTROLLER=>CO_TYPE_CUSTOM
iv_name =
'ICCMP_BP_SEARCH/CuCoSearch' "#EC NOTEXT
iv_target_node_name = 'CONTACTPERSONS'
iv_node_2_bind = CONTACTPERSONS ).
Any suggestions like how to fix this issue.
Regards,
Sijo -
Services procurement - Pricing Access sequence error for Custom fields
Hi Experts,
We have created 3 custom fields in KOMP structure. Which is required to create condition tables, access sequence. We have successfully created condition tables with the 3 fields along with the standard fields.
While creating access sequence we are getting the error as 'Select a document field'. Even after providing the document field, getting some other errors. Please find the attached document for steps we followed.
We are awaiting for your reply to rectify the error. Thanks.
Regards,
Ganesh R K.Hi Vijay,
Thanks you very much for your valuable reply.
We have added the custom field in KOMK, KOMG & KOMP structures. I have added the ZZITEMGROUP before KFRST and its working fine.
Need to understand what is the implication of KFRST.
As per our requirement the ZZPRODUCT should come first, followed by ZZITEMGROUP. Please advice how to achieve this.
Thanks.
Regards,
Ganesh R K. -
Error for custom infotype in PPOME
Hello Experts,
I have created one custom OM infotype for object position.Now when i am trying to acccess that Infotype in PO13 it is working fine but when i am trying to acccess the custom infotype in PPOME it is giving a dump.
EERROR:
Error in the ABAP program "SAPLRHOMDETAIL_PP01" had to be terminated because it has come accross a statement which cannot be exceuted.
An exception occurred.
The exception, which is assigned to class 'CX_SY_ASSIGn_CAST_UNKNOWN_TYPE', was not caught in procedure "INIT_SUBSCREEN" "(FORM)" nor was it propagagted by raising clause exception.
The reason for the exception is :
The type "" dynamically specified with ASSIGN....CASTING TYPE is unknown.
Please guide me where i am doing mistake.
Thanks in advance.
ShwetaHi Sudha,
PM01 is the tcode.
Similar questions were already answered in the following threads
ABAP HR : Infotype Enhancement
So please search and then post specific queries.
rgds
gayathri -
Document already exist error for our user screen
Hi All,
In SAP 2007 PL 13,after Removing record by right click remove ,I am not able to add the document. It gives error "Document no already exist". After diagnosis Of ONNM and NNM1 table ,I got that next no does not increases in NNM1and ONNM Table.
but this problem came after upgrading from 2005 to 2007.
it happens for some times.
I could not find any reason because I had generated Document no by sap object.
Is it any patch required,I had already run PL 09,10,13
please help me
thanks in advance.Hi Atun,
This issue comes if the connectivity is poor.
Standard procedure.
Step 1
open SAP Business one
check the last added record.
Note down the number.
Step 2
Open SQL server
open the table ONNM
Check for the specific number of the object(your user documents)
Note down the number.
The number in this table should be (last addded record in SAP business one + 1)
Generally this error comes when the ONNM table number and SAP business one last added record number is equal. -
Document splitting not working for customer & vendor Payment
Hi,
We have actived Document splitting on profit center for segment level reporting.
In below scanario Document spliting working fine.
Vendor Invoice (Docuement type - KR)
General Ledger view
Expense Dr 1000 PC1
Vendor Cr 1000 PC1
At the time of Payment (General ledger view) (Document Type - KZ)
Vendor Dr 1000 PC1
Bank Cr 1000 PC1
In the above scanario we dont have any issue, Based on invoice profit center spliting automaticlly in bank in General Ledgerview.
How ever in the below scanario Document spliting is not working in payment
No issues in Invoice
General ledger view
Exp Dr 1000 PC1
Exp Dr 1500 PC2
Vendor Cr 1000 PC1
Vendor Cr 1500 PC2
When we make payment to vendor Document splitting is not working, it get splitting in zero balance clearing account
vendor Dr 1000 PC1
Vendor Dr 1500 PC2
Bank Cr 2500 (No profit Center)
Doc splitt A/C 1000
Doc Split A/C 1000 PC1
Doc Split A/C 1500
Doc Split A/C 1500 PC2
My Finance Team requires automatic split up in bank based on vendor profit center.
We are using Business Transation 1000 (Payment) for document Type - KZ & DZ.
Regards,
LokeshCan you please confirm if the following settings exist in your system in various IMG nodes.
1. Bank G/L account is assigned to item category 04000 (IMG node: Classify G/L Accounts for Document Splitting).
2. Document type KZ is assigned to business transaction 1000 and transaction variant 0001 (IMG node: Classify Document Types for Document Splitting).
3. In IMG Node "Define Document Splitting Rule", under the method that is assigned to your company code, transaction 1000 and variant 0001, you see 04000 as one of the item categories to be edited.
4. If the answer for (3) above is yes, if you double-click on 04000 item category line, the processing category is set to 1 (Splitting based on base item categories).
5. Now when you double-click on 'Base item categories', you see 03000 - Vendor as one of the base item categories in the list there.
Please respond with Y / N to the above questions and we can go from there. -
Change document log not created for customer in Batch input/BDC
Hi Guys,
Change document log is created when you manually change the customer using XD02 but when run the Batch/BDC the values are Changed but the change document is not created.
Please someone can give me some hints?
Luca.Any update guys????
Regards,
guru singh -
Create New Document - Suddenly Lost Ability for Customer Option
Hi -
All of the sudden I can't create a customer profile when creating a new document. Earlier I selecting the print profile. I tried opening a new document and creating a custome profile but that option is grayed out.
Not sure if this is related but I created custome brushes yesterday but they don't appear today. Is that because of the profile that the brushes were created with and without that profile I won't see the brushes?I guess I still don't get it. I create a new brush in print profile but when I open a new doucment with that profile that brush isn't there.
Print Profile with New Brush Created
New Doucment with Print Profile -
No Change Document in outbound queue for customer status in table VBUP
Hello all,
we face the following issue. A customer status (UVP04), changed by a customer program, is not written in the outbound queue (lbwq) to transfer it in the business warehouse.
I checked several Function modules (VERKBELG_WRITE_DOCUMENT, MCEX_UPDATE_CALL_11.....) without success.
Any help would be appreciated.
jgSolution found: Dummy change with VA02, that generates a new record in the outbound queue.
-
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> -
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.. -
How to define document protocol for Custom/Generic message of ASCII types
We need define for B2B document protocol for Custom over Generic message type to receive/process ASCII message (either fixed or indefinite length) from Trading Partner, can anybody tell us if you have done it with detailed example and instruction:
1) In creating protocol revision/document definitions, do I need an Edifecs .ecs file? if yes, how to create the format for indefinite string? if not what I should put in document
definition for 'IDoc ecs File' ? (we actually we may have two different types
of ASCII message, not sure how to differentiate them)
2) Does Identifying expression need message/document translated into XML first ? since it's for
'Identifying XPath Expression' which implied existence of XSD
3) Please provide detailed example you accomplished this in B2B
Thanks in advance for any help!Yes its something on the similar lines but looks like this comparator needs to be at some specific place.
I tried to implement comparator interface in the custom domain data type class but it still throws the same exception.
Looks like RowComparator needs to be defined somewhere. any idea where?
The complete exception is below:
Caused by: oracle.jbo.JboException: Cannot find compare routines for test.MyString
at oracle.jbo.RowComparator.compareValues(RowComparator.java:108)
at oracle.jbo.RowComparator.compareRows(RowComparator.java:146)
at oracle.jbo.RowComparator.compare(RowComparator.java:158)
at java.util.Arrays.mergeSort(Arrays.java:1270)
at java.util.Arrays.mergeSort(Arrays.java:1281)
at java.util.Arrays.mergeSort(Arrays.java:1281)
at java.util.Arrays.sort(Arrays.java:1210)
at oracle.jbo.server.ViewObjectImpl.sortRows(ViewObjectImpl.java:6752)
at oracle.jbo.server.QueryCollection.sortRows(QueryCollection.java:995)
at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:1177)
at oracle.jbo.server.ViewRowSetImpl.executeQueryForMasters(ViewRowSetImpl.java:1331)
at oracle.jbo.server.ViewRowSetImpl.executeQueryForMode(ViewRowSetImpl.java:1249)
at oracle.jbo.server.ViewRowSetImpl.executeQuery(ViewRowSetImpl.java:1243)
at oracle.jbo.server.ViewObjectImpl.executeQuery(ViewObjectImpl.java:6715)
at org.calwin.view.bean.Table.tableSorting(Table.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597) -
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 -
%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 ??
Maybe you are looking for
-
Recover my voice memos after accidentally format my iPhone 4s
I accidently format my Iphone 4s and forget to back up my voice memos... i never back up the file in itunes can someone please tell me what to do to get them back?? thank you
-
[SOLVED]nm-applet fails to launch after update
Hi, I've just updated NetworkManager and network-manager-applet: [2012-10-31 20:16] upgraded networkmanager (0.9.6.0-2 -> 0.9.6.4-1) [2012-10-31 20:16] upgraded network-manager-applet (0.9.6.2-1 -> 0.9.6.4-1) After reboot nm-applet fails to launch wi
-
Operation confirmation display in REM
Hi, In my REM scenario, I am doing backflushing in MFBF, this leads to auto goods issue and auto GR of finished product( No reporting point backflushing). I am doing 'Post with correction' and then entering qty for goods issue and then actual timing
-
Help. I have an iMAC - not even one year old - just got this message - The installed graphics card does not meet the minimum requirements for Aperture. I have not made any changes to my machine. Help - I can't get to my images
-
I would be grateful if somebody could tell me why these funky fonts are showing up in my Dreamweaver CC dialogue boxes. I've never seen this before CC and I've been using DW for lots of years It's driving me crazy and I can't imagine that Adobe did