Known bugs of 3rd party software - Revision history

Admin at 13:20, 13 January 2017

2017-01-13T13:20:54Z

2016-11-14T12:43:38Z

German

2016-11-14T12:36:32Z

ENGDAT routing problems

2016-11-14T12:28:00Z

2012-11-30T10:47:06Z

OFTP error: no valid package received, but this binary content (8 bytes): '0x2 0x30 0x46 0x30 0x34 0xFE 0x27 0xD'

2012-11-30T10:46:55Z

OFTP error: no valid package received, but this binary content (8 bytes): '0x2 0x30 0x46 0x30 0x34 0xFE 0x27 0xD'

2012-11-30T10:46:37Z

OFTP error: no valid package received, but this binary content (8 bytes): '0x2 0x30 0x46 0x30 0x33 0xFE 0x27 0xD'

2012-02-03T14:11:24Z

Invalid transmission header

2012-02-03T14:10:22Z

2010-03-29T13:36:49Z

OFTP error: no valid package received, but this binary content (8 bytes): '0x2 0x30 0x46 0x30 0x34 0xFE 0x27 0xD'

← Older revision		Revision as of 13:20, 13 January 2017
Line 82:		Line 82:

	Speichern Sie diese Konfiguration. Alle neue durchlaufenden Aufträge werden die ENGDATv2 Abstract-Datei so codieren, dass der erwartete Wert enthalten ist.		Speichern Sie diese Konfiguration. Alle neue durchlaufenden Aufträge werden die ENGDATv2 Abstract-Datei so codieren, dass der erwartete Wert enthalten ist.
		+
		+
		+	== TLS error during connect try to <hostname>:6619: wrong version number ==
		+	If the remote party has a Hüngsberg OFTP2 system, please let the remote party check if the option "useSSL" is active for the TLS listener (default port: 6619) is active. When changing the configuration value, the listener has to be restarted.

@@ Line 67: / Line 67: @@
 Dieses Verhalten hat Einfluß auf die Interpretation folgender Eigenschaften von Absender und Adressat von Transferaufträgen:
-*Addresscode / Routing-Code
+*Adresscode / Routing-Code
-*Email-Adresse
+*E-Mail-Adresse
 ==== Lösung ====

@@ Line 38: / Line 38: @@
 === English ===
 ==== Scenario ====
-If your partner complains that ENGDAT routing doesn't work, it may be because OS4X uses a very strict implementation of the ENGDAT specification (VDA 4951 P1). It states in the document, that the UNH segment 0052 ("<code>Versionsnummer</code>" / version number) the value "<code>001</code>" must be used.
+If your communication partner complains that ENGDAT routing doesn't work, it may be because OS4X uses a very strict implementation of the ENGDAT specification (VDA 4951 P1). It states in the document, that the UNH segment 0052 ("<code>Versionsnummer</code>" / version number) the value "<code>001</code>" must be used.
 [[Image:ENGDATv2-UNH.png]]
@@ Line 50: / Line 50: @@
 In OS4X, you can configure the behaviour of the ENGDATv2 encoding plugin to encode the UNH segment to the required value. Configure the used send plugin group at the given partner (or location/department/recipient, depending on your used send plugin group configuration).
-In the desired hierarchy level (mostly used at top partner level), click on "Configure" beside the "Send plugin group":
+In the desired hierarchy level (mostly used at top partner level), click on "Configure" beside the "Plugin group for send jobs":
 [[Image:ConfigureSendPluginGroup.png]]
@@ Line 59: / Line 59: @@
 Save this configuration. All new jobs will encode the ENGDATv2 abstract file as required by the remote party.

← Older revision		Revision as of 12:28, 14 November 2016
Line 33:		Line 33:
	=== Solution ===		=== Solution ===
	None.		None.
		+
		+	== ENGDAT routing problems ==
		+
		+	=== English ===
		+	==== Scenario ====
		+	If your partner complains that ENGDAT routing doesn't work, it may be because OS4X uses a very strict implementation of the ENGDAT specification (VDA 4951 P1). It states in the document, that the UNH segment 0052 ("<code>Versionsnummer</code>" / version number) the value "<code>001</code>" must be used.
		+
		+	[[Image:ENGDATv2-UNH.png]]
		+
		+	This behaviour can influence the interpretation of:
		+	*address code / routing code
		+	*email address
		+	of sender and/or recipient of a transmission job.
		+
		+	==== Solution ====
		+	In OS4X, you can configure the behaviour of the ENGDATv2 encoding plugin to encode the UNH segment to the required value. Configure the used send plugin group at the given partner (or location/department/recipient, depending on your used send plugin group configuration).
		+
		+	In the desired hierarchy level (mostly used at top partner level), click on "Configure" beside the "Send plugin group":
		+
		+	[[Image:ConfigureSendPluginGroup.png]]
		+
		+	In the upcoming window, activate the checkbox "Encode segment UNH0052 as value '002' ('''violates specification''')?":
		+
		+	[[Image:Engdatv2-Plugin-Config-UHN0052.png]]
		+
		+	Save this configuration. All new jobs will encode the ENGDATv2 abstract file as required by the remote party.

@@ Line 25: / Line 25: @@
   A Start Session (SSID) command contained an invalid password.
 which means that the remote partner hasn't configured your OFTP password correctly.
 === Solution ===

@@ Line 9: / Line 9: @@
 which means that the remote side indicated an OFTP session error 3:
   A Start Session (SSID) command contains an unknown or invalid Identification Code.
-which means that the remote partner doesn't has correctly configured your SSID.
+which means that the remote partner hasn't configured your SSID correctly.
 === Solution ===

@@ Line 30: / Line 30: @@
 == Invalid transmission header ==
-The software of the company "Greve Ingenieurleistungen" is lacking of correct support of the stream transmission header. It's impossible to communicate with their software.
+The software "giodette" of the company "Greve Ingenieurleistungen" is lacking of correct support of the stream transmission header. It's impossible to communicate with their software.
 === Solution ===
 None.

← Older revision		Revision as of 14:10, 3 February 2012
Line 28:		Line 28:
	=== Solution ===		=== Solution ===
	Ask the remote party to update their OFTP settings for your partner entry. And, if you want, insist on an update of the remote software.		Ask the remote party to update their OFTP settings for your partner entry. And, if you want, insist on an update of the remote software.
		+
		+	== Invalid transmission header ==
		+	The software of the company "Greve Ingenieurleistungen" is lacking of correct support of the stream transmission header. It's impossible to communicate with their software.
		+	=== Solution ===
		+	None.

@@ Line 22: / Line 22: @@
 which has an ASCII interpretation of
   F    0     4
-which means that the remote side indicated an OFTP session error 3:
+which means that the remote side indicated an OFTP session error 4:
   A Start Session (SSID) command contained an invalid password.
 which means that the remote partner doesn't has correctly configured your OFTP password.