Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > BizTalk Server Forums > BizTalk Server EDI and AS2 > Upgrade BizTalk 2004 to BizTalk 2006 Mapping Issues
Ask a questionAsk a question
Search Forums:
 

AnswerUpgrade BizTalk 2004 to BizTalk 2006 Mapping Issues

  • Wednesday, October 21, 2009 9:29 PMRaj Venkat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    We are facing a huge mapping issues in BizTalk 2006 after upgrade the same BTS applications are just working fine in BTS2004.

    We followed below steps.

    1. We created development environment with BizTalk Server 2006
          --  VS 2005
          -- SQL Server 2005
          -- .NET Framework 2.0
    2. Convert BTS applications in to .Net 2.0 by using VS2005
    3. Compile BTS applications and Deploy by using VS2005
    4. Configure all the ports (send/receive) just like BTS2004 server have.
    5. All the setting we made it similar to old BTS2004 server.

    However, we are facing issues. I am placing few event log errors below. Please help us how to resolve.


    Event Type: Error
    Event Source: HIPAA EDI Subsystem
    Event Category: BizTalk Server 2006
    Event ID: 24
    Date:  10/21/2009
    Time:  11:56:16 AM
    User:  N/A
    Computer: xxxxxxxx
    Description:
    Error encountered: ERROR (39) :
    The document type is not recognized. Contact the sender.RootLabel: [Nsf], PublicId: [], SystemId: [http://NsfData],  (msgnr:0 segnr:0)(line:0 pos:292 filepos:292)

    Function:
    DetermineFormat

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

    Event Type: Error
    Event Source: HIPAA EDI Subsystem
    Event Category: BizTalk Server 2006
    Event ID: 24
    Date:  10/21/2009
    Time:  11:56:19 AM
    User:  N/A
    Computer: xxxxxxxx
    Description:
    Error encountered: ERROR (36), docnr 10139 :
    A required segment is not included in the document. Contact the sender.source format: [101  0  ,XML 1.0]
    source document: [837   004010DEFAULT          X X098A1,Health Care Claim: Professional]
    source segment: [data#49,def#130,name=TS837Q1_2320]
    source element: [def#1,elm#0,comp#0,name=TS837Q1_2320_SBR_OtherSubscriberInformation],  (msgnr:1 segnr:49)(line:1 pos:12233 filepos:12513)

    Function:
    defseg_find

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

    Event Type: Error
    Event Source: HIPAA EDI Subsystem
    Event Category: BizTalk Server 2006
    Event ID: 24
    Date:  10/21/2009
    Time:  11:56:19 AM
    User:  N/A
    Computer: xxxxxxxx
    Description:
    Error encountered: ERROR (36), docnr 10139 :
    A required segment is not included in the document. Contact the sender.source format: [101  0  ,XML 1.0]
    source document: [837   004010DEFAULT          X X098A1,Health Care Claim: Professional]
    source segment: [data#50,def#130,name=TS837Q1_2320]
    source element: [def#1,elm#0,comp#0,name=TS837Q1_2330A],  (msgnr:1 segnr:50)(line:1 pos:12506 filepos:12786)

    Function:
    defseg_find

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

    Event Type: Error
    Event Source: HIPAA EDI Subsystem
    Event Category: BizTalk Server 2006
    Event ID: 24
    Date:  10/21/2009
    Time:  11:56:19 AM
    User:  N/A
    Computer: xxxxxxxx
    Description:
    Error encountered: ERROR (36), docnr 10139 :
    A required segment is not included in the document. Contact the sender.source format: [101  0  ,XML 1.0]
    source document: [837   004010DEFAULT          X X098A1,Health Care Claim: Professional]
    source segment: [data#53,def#161,name=TS837Q1_2330D]
    source element: [def#1,elm#0,comp#0,name=TS837Q1_2330D_NM1_OtherPayerReferringProvider],  (msgnr:1 segnr:53)(line:1 pos:13055 filepos:13335)

    Function:
    defseg_find

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

     

     

Answers

All Replies