Data Replication 2
Results 1 to 1 of 1

Thread: HOW TO: Debug a BizTalk 2004/2006 runtime problem

  1. #1
    Adeeb Mass'ad is offline Support Manager
    Join Date
    Aug 2006
    Location
    Jaffa of Nazareth
    Posts
    169
    Rep Power
    14

    HOW TO: Debug a BizTalk 2004/2006 runtime problem

    DESCRIPTION

    This article describes the steps to be taken when facing a run-time problem using the Attunity BizTalk Adapters.

    STEP 1

    Before starting the debugging procedures which follows, you should always start by reviewing the last few Event Viewer entries.

    To start the Event Viewer:
    - Click on the Start menu.
    - Administrative Tools.
    - Click on the Event Viewer.
    - Click on the Application within the Event Viewer.
    BizTalk and Attunity events are listed in the Application view of the Event Viewer.

    If you find a generic BizTalk related errors consult your IT for solving the problems.

    Common problems

    PROBLEM 1 - Host is not started.
    SOLUTION - Start the host using the BizTalk Administration.

    PROBLEM 2 - One of the Ports is not started/enabled.
    SOLUTION - Check the Ports using the BizTalk Administration.

    PROBLEM 3 - Receive or Send ports point to non valid location
    SOLUTION - Check the location of the port (for example, File Receive Port which is pointing to bad lcoation on the network/drive).

    PROBLEM 4 - Failure to deploy the Adapters
    SOLUTION - Check the Adapter being deployed correctly, deploy the adapter and make sure you get no errors.

    If you suspect Attunity related issue proceed to STEP 2.

    STEP 2

    Enabling the Attunity Adapter tracing is your 2nd step. To enable the tracing decide on which Adapter you are getting the errors, this can be seen from the Event Viewer error messages.

    To enable the trace perform the followings:
    BizTalk 2004

    - Start the BizTalk Server Administration.
    - Expand the Microsoft BizTalk Server 2004 entry.
    - Expand the Adapters category.
    - Expand the Adapter you want to modify.
    - Click on the "Sender Handlers" or "Receive Handlers" depending on the Adapter type.
    - Right-Click the BizTalk Host entry on the right-pane and choose "Properties".
    - Click on the properties tab.
    - Scroll to the "Trace Level" property, and set it to DEBUG.
    NOTE: The DEBUG trace level is the most verbose tracing level. It's recommended to clear the Event Viewer.

    Restart the BizTalk Host to enable the tracing.

    Analyze the resulting Events and if you find a BizTalk related error which you can handle, then fix it and remove the tracing.

    If you find an error related to Attunity Adapter send it to the Attunity Support.

    At many cases when the error is related to the backend (for example an Adabas driver error), Attunity Support will need the logging from the backend, proceed to STEP 3.

    STEP 3

    Enabling the tracnig on the backend can envolve several debugging flags. However, as a starting point we will need the minimal tracing to including generalTrace and acxTrace.

    In cases where the problem may reside in the backend driver we may require driverTrace as well.

    To configure the debugging flags perform the following:

    - Run the Attunity Studio.
    - Expand the machine where the backend resides. If the machine does not exist you should add it to the Studio.
    - Right-Click on the binding which hosts the Adapter or Driver which BizTalk uses.
    - Edit the Binding.
    - Set the debugging flags: generalTrace='true', acxTrace='true'.

    NOTE: You should recycle the server in order for the new flags to be effective.

    FINAL STEP

    If the problem requires creating an Attunity Support issue, please collect the information from the previous steps when filling the issue:

    1. Describe the problem and the adapter being used.
    2. Full description of the environment.
    3. Export the Application section of the Event Viewer in it's native format. Simply Right-Click the Application entry and export it.
    4. ZIP the log files from the backend and attach them to the issue.
    5. Export MACHINE from the Attunity Server. This can be done using the Studio or nav_util on the server (nav_util export machine mac.xml).
    6. Use the ExportAdapters utility of the Attunity BizTalk Gateway and export the adapters to an XML file.
    Last edited by Adeeb Mass'ad; 08-18-2008 at 07:39 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •