Microsoft Knowledge Base Email Alertz

(887481) - Describes a problem that occurs when you use the BizTalk Deployment Wizard to deploy an assembly that contains one or more EDI schemas, and the EDI database on the destination computer is not updated to include the deployed EDI schemas.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 887481 - Last Review: April 18, 2005 - Revision: 2.2

The BizTalk Deployment Wizard does not update the destination BizTalk EDI database when you deploy EDI schemas

SYMPTOMS

If you use the BizTalk Deployment Wizard to deploy an assembly that contains one or more Electronic Data Interchange (EDI) schemas to a computer that is running Microsoft BizTalk Server 2004, the EDI database on the target computer is not updated to include the deployed EDI schemas.

CAUSE

This problem occurs because the BizTalk Deployment Wizard does not implement functionality to update the destination BizTalk EDI database with the information in the deployed EDI schemas.

RESOLUTION

To resolve this problem, manually update the destination BizTalk EDI database by using the information in the deployed schemas. To do this, follow these steps:
  1. Run the Xsd2edi.exe command at a command prompt:

    XSD2EDI -c[Location of EDICodelists.mdb] -i[Base EDI schema] -t -f

    For example, run the Xsd2edi command at a command prompt if the EDICodeLists.mdb file is in the default directory and you are updating the BizTalk EDI database with the 850Schema.xsd schema file:

    XSD2EDI -c"C:\Program Files\Microsoft BizTalk Server 2004\EDI\Adapter\CodeLists\EDICodeLists.mdb" -i"C:\Program Files\Microsoft BizTalk Server 2004\EDI\Adapter\EDI Schemas\X12\4010\850Schema.xsd" -t -f
    
    

    Note If you receive a "The input file is not present!" error message or a "The codelist database is not valid!" error message when you run the Xsd2edi command, make sure that there are no spaces between the Xsd2edi switches and their arguments.
  2. Generate the EIF file that is used by the BizTalk Base EDI Service at run time by running the COMPEIF command at a command prompt:

    COMPEIF

    Note You must start the BizTalk Base EDI Service before you run the COMPEIF command.
  3. After the COMPEIF command has completed, restart the BizTalk Base EDI Service on the destination computer.

MORE INFORMATION

The Xsd2edi.exe command converts an XSD file into the required EDI schema format and then stores it in the BizTalk EDI database. To see a list of all the switches that are available for the Xsd2edi command, run the Xsd2edi command at a command prompt:

XSD2EDI ?

By default, the Xsd2edi.exe file is installed in the Program Files\Microsoft BizTalk Server 2004\EDI\Subsystem folder.

Important The arguments to the Xsd2edi.exe command may be different for different versions of the Xsd2edi.exe command. To determine what parameters are required, run the following command at a command prompt:

XSD2EDI ?

Also note that if you do not have Microsoft SQL Server 2000 installed on the BizTalk Server 2004 server, you must install the SQL Client tools for the Xsd2edi command to work.

The Compeif.exe command uses the information in the BizTalk EDI database to generate an Engine Input File (EIF) to be used by the BizTalk Base EDI Service to parse and serialize EDI documents. The default location for the EDI EIF is C:\Documents and Settings\All Users\Application Data\Microsoft\BizTalk Server 2004\EDI\Subsystem\EIF\live.eif. By default, the Compeif.exe file is installed in the Program Files\Microsoft BizTalk Server 2004\EDI\Subsystem\ directory.

STATUS

This behavior is by design.

APPLIES TO
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
Keywords: 
kbprb KB887481
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate