RE: Document Type Not Recognized Error

One last step I forgot to mention in my state of glee...
I restarted services after that last xsd2edi call.

My conclusion of this exercise. The repository somehow had a corrupt copy
of my xsd. All my 323,000 attempts to clear this error by apparently
successfully (no error message) validating the xsd in VS2005 did nothing to
fix this. It finally took using xsd2edi to rip out the old schema and
replace it to fix the problem.
--
John


"JT" wrote:

Never mind - I fixed it myself. I used xsd2edi with -r flag to remove xsd,
undid the replock in dbo.parame, restarted services, and used xsd2edi to get
the xsd back into the repository. Now all is ok... for now...
--
John


"JT" wrote:

This is my exact error message:

Event Type: Error
Event Source: HIPAA EDI Subsystem
Event Category: BizTalk Server 2006
Event ID: 24
Date: 12/21/2006
Time: 13:36:18
User: N/A
Computer: DVX64
Description:
Error encountered: ERROR (39) :
The document type is not recognized. Contact the sender.RootLabel:
[X12_4010_837], PublicId: [], SystemId:
[http://schemas.wpc-edi.com/X12/ISOMORPH/HIPAA/4010A1/TS837Q1], (msgnr:0
segnr:0)(line:0 pos:309 filepos:309)

Function:
DetermineFormat

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Looking at the log in [Documnents Home]\Logs reveals the schema IS in the
repository....

[Thu Dec 21 03:10:02 2006] xsd2edi started
[Thu Dec 21 03:10:02 2006] Repository has been locked.
[Thu Dec 21 03:10:02 2006] Start parsing schema.
[Thu Dec 21 03:10:02 2006] Processing a HIPAA schema.
[Thu Dec 21 03:10:02 2006] Skipping reference to segment X12_EnvelopeHeader.
[Thu Dec 21 03:10:02 2006] Skipping definition of segment X12_EnvelopeHeader.
[Thu Dec 21 03:10:02 2006] Skipping definition of segment
ST_TransactionSetHeader.
[Thu Dec 21 03:10:02 2006] Skipping definition of segment
GS_FunctionalGroupHeader.
[Thu Dec 21 03:10:02 2006] Skipping definition of segment
ISA_InterchangeControlHeader.
[Thu Dec 21 03:10:02 2006] End of parsing schema.
[Thu Dec 21 03:10:02 2006] Hashtotal for C:\Visual Studio Projects\BizTalk
Projects\MapTo837\837professional_v3_wpc_single.xsd is :
[1QSIRQDdMRMQ290nLGhH6hg==].
[Thu Dec 21 03:10:02 2006] Compare hashtotals
1QSIRQDdMRMQ290nLGhH6hg==1QSIRQDdMRMQ290nLGhH6hg==
[Thu Dec 21 03:10:02 2006] Definition is already in repository C:\Visual
Studio Projects\BizTalk Projects\MapTo837\837professional_v3_wpc_single.xsd
[Thu Dec 21 03:10:02 2006] Repository has been unlocked.
[Thu Dec 21 03:10:02 2006] Processing document succeeded.
[Thu Dec 21 03:10:02 2006] xsd2edi finished


What next??

--
John


"JT" wrote:

Hi all,
I am getting a consistent error in trying to send a document through the
HIPAA Adapter 3.3. Using the 837P XSD with one promoted property, I
validated the schema prior to deployment of my mapping project. I restarted
HIPAA Service and BTS Service. The interchange still fails with the above
error. In the past (BTS 04), re-validating the xsd and restarting services
has fixed this for me.
Things that are perhaps unusual about my environment:

Windows 2003 SP1 x64 ENT
SQL 2005 x64 ENT
BTS 2006 DEV
BTA4H 3.3 ENT

This is all running on one 64 bit laptop (it's a helluva machine!)

The host instance handling all aspects of the application that processes
this message is restricted to 32-bit only, and is the default, trusted
instance.

The EDI Service runs with the same credentials/user account as the HIPAA EDI
Service. I actually have tried this with the EDI Service started and with it
disabled (my working setup in BTS 2004). I have not tried it standing on my
head, but am considering the option!

Any advice here would break yet another BTS obsession loop that I find
myself in.

Thanks.

--
John
.

Loading