Windows Server - EDI Pipeline throws Validation error 71 "Transaction Set or Group Control Number Mismatch"

Hi Everyone,

the EDI Receive Pipeline throws error 71 while validating an EDIFACT
message and throws a negative CONTRL message. The following error log
is written to the event viewer:

Error encountered during parsing. The Edifact transaction set with id
'1401-1' contained in interchange (without group) with id '1414', with
sender id '9900294904714', receiver id '9903228000003' is being
suspended with following errors:

Error: 1 (Miscellaneous error)
71: Transaction Set or Group Control Number Mismatch
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does anyone have a clue what that means?
In the EDIFACT file, there are no groups used; furthermore, the
interchange numbers in UNH and UNT are the same. Further EDIFACT
errors (like 26: Duplicate interchange detected) do not occur.

Thanks,
Christoph

  Leonid Ganeline replied...

Hi,
In your file the data should be like here the 00000000000775 (in UNB and
UNZ), 00000000000831 (in UNH and UNT)

UNB+UNOA:1+changed:ZZ+changed:12+060710:1450+00000000000775++changed
UNH+00000000000831+changed:D:95B:UN'
....
UNT+334+00000000000831'
UNZ+1+00000000000775'


--
Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/

  christoph replied...

Thank you, Leonid,

the file looks like this:
UNA:+.? '
UNB+UNOC:3+changed:14+changed:500+070705:2310+U0000000000545+++A+++1'
UNH+U0000000000545+UTILMD:D:04B:UN:4.0a'
...
UNT+24+U0000000000545'
UNZ+1+U0000000000545'

Actually, I can't see a mistake as the number in UNB is the same as in
UNZ and the same is valid for UNH and UNT...

Do you have any other idea? Do you know what is meant with transaction
set?

Thanks,
Christoph

AD replication Windows Server I have and exiting 2000 mixed mode domain just added a 2003 server into the mix and promoted it to DC The AD transfer happened but I am AD on the new DC. . . . . but havent observed the new user over in my 2000 server AD not sure if I am under the correct assumptions that I should see these existing w2k DC I should see the AD correclty replicating between the 2 ? thanks Windows Server Active Directory Discussions DC (1) Administration (1) Eriecountygov (1) DNS (1) TCP (1) CN (1) LH (1) Server (1) Run diagnostics against your Active Directory domain. If you don't have the support tools installed, install them from your server install disk. d: \ support \ tools \ setup.exe Run dcdiag, netdiag and repadmin in verbose mode the 1st thing I run into running the DCDIAG ( on DC1) is 1722 error RPC server is unavialable 510 failures sincet he last success but later it says this server passed test replications . . . . . I do not see this 1722 stuff later on when it tests

Error " The Target principal name is incorrect" Windows Server Hi All, I have big problem , becuase i miss take change the DC system day Thanks, DC and DC2 : Windows 2003 Std R2 SP2 Windows 2000 Active Directory Discussions Windows Server 2003 R2 (1) Active Directory (1) MSSQLSvc (1) SupportedSASLMechanisms (1) SupportedLDAPPolicies (1) DHCPServer (1) IMAC www.blakjak.demon.co.uk / mul_crss.htm Hi All, Yes , because the Site A DC Server change the time to year 2002 (is my mistake ), now the site A server and site B DC cannot replication , on Site A open AD site and Services replcate context is in the process of being removed or is not replicated from the specified server. This operation will not continue " For The Event Log Site B Event Type: Error Event User: N / A Computer: DC_B Description: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host / smlad.sml.com. The target name used was LDAP / 6ad1947f-b693-4166-85fc-d2097457fec6 password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (ABC.COM help , Thanks Hi All, More Detail for my case , On siteA (HK) DC have 2 server dc1 and dc2 On SiteB (CN) DC habe 1 server dc_b1 before i have mistake

WARNING] Failed to query SPN registration on DC Windows Server Hi all, Newly promoted DC (after an OS failure requiring a rebuild - metadata cleanup performed to query SPN registration on DC (every DC is listed) DCDIAG is clean. On the server which the newly promtoed one has a site link too are many Event ID 1265 on it's replication partner. Any ideas guys? I'm a bit stumped here Windows Server Active Directory Discussions AndrewDOTstoryATjameswalkerDOTbiz (1) Active Directory (1) Windows Server (1) KnowsOfRoleHolders (1) NCSecDesc (1) ExistingADS01 (1) NewADS01 (1) Report (1) After a reboot on x.0.1 DNS Servers . . . . . . . . . . . : x.x.1.1 x.x.33.99 Primary WINS Server . . . . . . . : x.x.1.1 Secondary WINS Server . . . . . . : x.x.99 IPConfig from existing DC (not in same site, in site linked via x.32.1 DNS Servers . . . . . . . . . . . : x.x.33.1 x.x.33.99 Primary WINS Server . . . . . . . : x.x.33.1 Secondary WINS Server . . . . . . : x.x.33.99 Ran the command also on both DC's, not sure what

AD state and dns windows2003r2x64 Windows Server My Company recently upgraded to server2003R2x64 with the help of a Microsoft Partner from Nt4 I have two main catogoty of issues I would like to resolve. thank you Windows Server DNS Discussions DomainDnsZones.ELLJHB.ELLIESHQ.LOCAL (1) DomainDnsZones.ELLIESHQ.LOCAL (1) ForestDnsZones.ELLIESHQ.LOCAL (1 D / E / s:HQDC1" Domain Controller Diagnosis Performing initial setup: * Connecting to directory service on server HQDC1. HQDC1.currentTime = 20080621173737.0Z HQDC1.highestCommittedUSN = 1417525 HQDC1.isSynchronized = 1 HQDC1.isGlobalCatalogReady = 1 * Collecting CN = Configuration, DC = ELLIESHQ, DC = LOCAL iSiteOptions = 0 dwTombstoneLifeTimeDays = 60 dwForestBehaviorVersion = 0 HomeServer = 0, HQDC1 SERVER: pServer[0].pszName = HQDC1 pServer[0].pszGuidDNSName = 6541722b-9298-4783-8f73-ac0eef5d620d._msdcs.ELLIESHQ.LOCAL DC = ELLIESHQ, DC = LOCAL pServer[0].ppszPartialNCs: ppszPartialNCs[0] = DC = ELLJHB, DC = ELLIESHQ, DC = LOCAL SERVER: pServer[1].pszName = HQDC2 pServer[1].pszGuidDNSName = b2aeeeca-c018-4ff1-af82-55a11417f52a._msdcs.ELLIESHQ.LOCAL DC = ELLIESHQ, DC = LOCAL pServer[1].ppszPartialNCs: ppszPartialNCs[0] = DC = ELLJHB, DC = ELLIESHQ, DC = LOCAL SERVER: pServer[2].pszName = JHBDC1 pServer[2].pszGuidDNSName = 5ae6c190-0a13-4a98-ade5-b99391085bf7._msdcs.ELLIESHQ.LOCAL CN = Configuration, DC = ELLIESHQ, DC = LOCAL pServer[2].ppszPartialNCs: ppszPartialNCs[0] = DC = ELLIESHQ, DC = LOCAL SERVER: pServer[3].pszName = JHBDC2 pServer[3].pszGuidDNSName = 45585b9f-c26b-403c-8b18-8c80cb0aba5a._msdcs.ELLIESHQ.LOCAL ELLJHB, 4 TARGETS: HQDC1, HQDC2, JHBDC1, JHBDC2, = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Done Printing pDsInfo Doing initial required tests Testing server: Default-First-Site-Name \ HQDC1 Starting test: Connectivity * Active Directory LDAP Services Check Failure Analysis

Any idea why this does not work anymore? Windows Server Hi all, Today, I just tried several computers and servers to do gpupdate / force and XP and Windows 2003 and windows 2000 DCs envir.). Can anyone help? Thank you. Windows Server Active Directory Discussions Windows Server 2003 R2 (1) Windows XP (1) CRSOPComponentData (1) Active Directory (1) Windows Server (1) RIDNextRID (1) RIDPreviousAllocationPool (1) SupportedSASLMechanisms (1) Hello John, If policies do not apply correct can be an issue. Please post an ipconfig / all from a client and your DNS server / s Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties 200.99 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.200.1 DHCP Server . . . . . . . . . . . : 192.168.200.43 DNS Servers . . . . . . . . . . . : 192.168.200.10 192.168.200.49 Primary WINS Server . . . . . . . : 192.168.200.43 Lease Obtained. . . . . . . . . . : Tuesday, April 15, 2008 9:31:33 AM Lease 168.200.1 DNS Servers . . . . . . . . . . . : 192.168.200.10 192.168.200.49 Primary WINS Server . . . . . . . : 192.168.200.43 BDC - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - Windows IP Configuration Host Name . . . . . . . . . . . . : conad Primary Dns Suffix . . . . . . . : boxley