Tuesday, February 07, 2006

Event ID #5743 - Send Port Error Message

I recently received this error message after deploying an assembly with a binding file and was stumped by it.

--------------------------
Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5743
Date: 2/6/2006
Time: 7:06:18 PM
User: N/A
Computer: XXX-XX-BZT1
Description:
The adapter failed to transmit message going to send port "E:\xxxxxxx\xxxxx\xxxxx\xxx\Final.837EDI\%SourceFileName%". It will be retransmitted after the retry interval specified for this Send Port. Details:"The FILE send adapter cannot open file E:\xxxxxxx\xxxxx\xxxxx\xxx\Final.837EDI\837_EDI.txt for writing. ".

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

All the posts I saw about it dealt with Web Services which is something I wasn't working with. It turned out to be a "D'oh" moment. The binding file I used had assigned an address of 'Final.837EDI' for the last directory in the path, when in fact the directory was 'Out.837EDI'. Of course the send port couldn't write to it, it didn't exist! Anyway, if you are running into this issue, make sure all the assumptions you are making are correct (ie paths are right).

Monday, February 06, 2006

XPATH expressions with XPATH Visualizer

With regards to my last post, I went looking for a good XPATH expression tool after the Advanced features of my Home version of XML Spy ran out. I found a great free tool at TopXML.com from Dimitre Novachev called "XPATH Visualizer" the link is http://www.topxml.com/xpathvisualizer/. This is a great browser based tool that allows you to open an XML doc and create XPATH expressions which it then highlights the results of in the doc. Nice for getting the syntax just right before adding to your BizTalk map or orchestration. It also handles XPATH functions like count and sum.

My only lament isthe small field for entering the XPATH expressions, but that's done with HTML so alittle modification takes care of that.

Definitely worth a look if you have the need for such a tool.

Accessing Message XML in Orchestration

I had a situation where I needed to access the Message XML in an orchestration recently and was stumped as to how to do this. I posted the question on the BizTalk -General Newsgroup and got a good answer back from Greg Forsythe. He suggested:

----- From Greg Forsythe -----
Declare an orchestration variable of type System.Xml.XmlDocument
variable = message;

or

You can directly access any part of the message using the xpath function.
with a variable of the appropriate type.

variable = xpath(message, "");
-------------------------------

I had done with the first option by the time I read this, but after testing the 'xpath' function worked out to be a great option for plucking data from the Message. Thanks Greg.

Friday, October 07, 2005

HIPAA Error: No authorization exists

This is a fairly common error, but perplexing when encountered.
---------------------------
Error encountered: ERROR (13), docnr 10029 :No authorization exists for this document type. Check the port properties.sender: [8][DEFAULT], recipient: [7][DEFAULT], source format: [101 0 ], source document: [837 004010DEFAULT X X096A1
---------------------------
To fix this set the HIPAA_EDI Send Port properties and select the document in the "Supported Document Types in HIPAA" section.

Monday, October 03, 2005

Introduction

I'm starting this blog to try and record some of the troublesome errors I've gotten with BizTalk 2004 and the HIPAA Accelerator 3.0 and their subsequent fixes. I've found many solutions in other intrepid Biztalkers' blogs and wanted to contribute my experinces with BizTalk and specifically the HIPAA Accelerator. The HIPAA Accelerator in particular seems to suffer from a relatively small knowledge base on the web it's my hope that over time this will add something.

That said I'm terrible about keeping journals so we'll see how this goes. I expect I'll start off by combing through the MS BizTalk newsgroups for my past postings to give them a more permanent home here.