This month we are happy to announce new versions of a few of our products adding additional features and capabilities.
First, we have updated our T-Connect EDI Database to support the full ANSI X12 EDI 837 transaction set. This includes full support for Institutional, Professional, and Dental transaction sets. The EDI Database Toolkit is our proprietary set of databases constructed to store and archive EDI messages and is included in our EDI Accelerator package, or can be purchased as a standalone product.
We have a new version of our T-Connect HIPAA EDI Accelerator available. The EDI Accelerator is our flagship product allowing for rapid deployment of a complete end to end EDI intake and storage solution based on the Microsoft BizTalk Server platform.
The T-Connect EDI Viewer has been updated with backwards compatibility for the EDI ANSI Version 4 (004010). The EDI…
BizTalk is great in its ability to store messages within the MessageBox even after processing failure, however its not always so easy to get those messages back out! I recently had a need to retrieve all messages that were currently suspended due to validation failures while attempting to generate X12 EDI messages using the Microsoft.Practices.ESB.
In September of last year, we released the T-Connect EDI Splitter For BizTalk. We are proud to announce the release and immediate availability of the newest version of the T-Connect EDI Splitter. For the uninitiated, the EDI File Splitter is a Microsoft BizTalk Server pipeline component that enables the rapid splitting of large EDI files within BizTalk Server. These split files are delivered to an user configurable folder location. Along with additional features added to the EDI Splitter for BizTalk, we are also releasing a standalone application for Microsoft Windows available today: The T-Connect EDI Splitter for Windows
We are happy to announce the availability of our enhanced product, the T-Connect EDI Accelerator for BizTalk. We have seen a trend in the difficulties encountered while processing EDI messages. That trend includes all types – both HIPAA and Manufacturing/supply chain transactions. Originally, we developed the T-Connect HIPAA Accelerator to address these pain points, allowing companies in the Healthcare space to successfully process claims, authorizations, benefit enrollments, eligibility inquiries, and acknowledgements. The T-Connect EDI Accelerator was purpose built to address pain points that many companies experience in working with EDI files. This includes, but is not limited to:
The process of on-boarding of new trading partners is time consuming and expensive
There is a significant risk of implementing unproven platforms, especially complex point to point architectures.
Their current EDI platform is a “home grown” point-to-point or manual/paper-based system
This is very hard to maintain
Recently, while troubleshooting performance issues at a client, I came across a peculiar issue. The environment in question was a multi- server environment with multiple BizTalk Servers (2010) connected to a SQL Server cluster. The issue was extremely slow performance when trying to view, refresh, start or stop the host instances through the Administration Console. Now usually it takes a few seconds for host instances to start, stop, or restart, however, in this case just refreshing the status of the host instances was taking over a minute.
The problem was that one of the BizTalk Servers in the group was offline for some time, causing the host instances tied to that BizTalk Server, within the same group, to become unresponsive. This caused slowdown in viewing the host instances for any of the other servers in the BizTalk Group.
There are two ways to resolve this:
1. Turn on…
While building BizTalk projects within Visual Studio, it is possible to receiving the following error when trying to compile a project with multiple orchestrations:
“The namespace ‘[namespace]’ already contains a definition for ‘_MODULE_PROXY_’”
While the error seems obvious, in my case, the namespaces were indeed unique, such that the above error did not make much sense. The underlying issue was in fact that the type names of two of the orchestrations within the project were identical. It turns out that an orchestration was at one point duplicated, and only the namespace was changed. After making the type names unique, the project successfully compiled and deployed.
A common trend that we have been seeing recently is the similarities in the pain points that companies are often faced with. One of those such pain points is the difficulty in quickly receiving and processing large EDI files having a file size over 10 MB. In one instance, there was a need to receive a HIPAA EDI 834 Enrollment file totaling 1.3 GB, containing roughly 800,000 enrollments. The already powerful BizTalk Server in a 1-1 architecture – 1 BizTalk Server, 1 SQL Server, was having difficulty processing the file. The file would take several hours to process, often taking up several gigabytes of drive space to attempt to disassemble the file using the EdiDisassembler pipeline.
There are a few common deployment errors in Microsoft Visual Studio when redeploying a previously deployed BizTalk project.
“Failed to add resource(s). Change requests failed for some resource. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Cannot update receive port “”. Transform “” not found”
A quick tip today – I came across an error while trying to enlist one of my send ports while deploying a BizTalk application using the amazing BizTalk Deployment Framework.
“Could not enlist Send Port ‘X’. Exception from HRESULT: 0xC00CE557 (Microsoft.BizTalk.SnapIn.Framework)
I have recently encountered an error while trying to reinstall BAM Tool and the BAM Portal on a Microsoft BizTalk Server 2013 installation. I encountered the following error while attempting to configure the BAM Portal in the Microsoft BizTalk Server Configuration window.