BizTalk Server 2004 : B2B, EAI and .NET

Thursday, November 18, 2004

Getting the BizTalk SQL Server DB Name

A quick one. How to get the name of the SQL Server that BizTalk is running? A relatively easy way is to get it from the registry. Heres a code sippet that does just that.

string strBtsSvrSubKey =
"Software\\Microsoft\\BizTalk Server\\3.0\\Administration";
string strBtsSqlSvrKey = "MgmtDBServer";
Microsoft.Win32.RegistryKey key = Microsoft.Win32.Registry.LocalMachine.OpenSubKey(strBtsSvrSubKey);
string strBtsSqlSvrName = key.GetValue(strBtsSqlSvrKey).ToString();

Any queries, post a comment.

View complete post...

Tuesday, November 16, 2004

HIPAA Accelerator 3.0 Error deciphering

The BizTalk Accelerator for HIPAA 3.0 throws up a mighty detailed error in the event log when it fails during Xml to EDI translation and/or validation. These errors tend to look a little scary (they scared me at the very least). An example would be :

Status report details: SRH DevBT03 200411122204111 DEFAULT 2 DEFAULT
SRM 00000000 00010168 101 0 837 004010HC09translate failed 0000010000010000000000010 10168
SRE 001030ProcessSegment 00053 000TS837Q1_2420A_NM103__RenderingProviderLastOrOrganizationName source format: [101 0 ,XML 1.0]\r\nsource document: [837 004010DEFAULT X X098A1,Health Care Claim: Professional]\r\nsource segment: [data#53,def#232,name=TS837Q1_2420A_NM1_RenderingProviderName]\r\nsource element: [def#4,elm#0,comp#0,name=TS837Q1_2420A_NM103__

RenderingProviderLastOrOrganizationName], (msgnr:1 segnr:53)(line:2 pos:11671 filepos:11953)

Look for the last numeric code following the SRE element. In this case its 001030. Ignore the 0010 part and you are left with 30. Open [document's home]\HIPAA_EDI\Subsystem\EIF\live.eif with notepad. Please be careful not to edit this file!! Preferrably create and open a copy. The first section of the file contains code to message mapping entries like :
ET1000001The path does not exist. Check the folder location.

Look for the entry matching our code i.e. 30. We have :
ET1000030The document does not contain a required element. Contact the sender.

So, the actual interpretation of the event log message is :
"The required element/attribute TS837Q1_2420A_NM103__RenderingProviderLastOrOrganizationName in the segment TS837Q1_2420A_NM1_RenderingProviderName is missing."

Now that's a LOT less frightening I think. :)

View complete post...

Thursday, November 11, 2004

HIPAA Accelerator 3.0 Gotchas

I stumbled across a couple of things w.r.t the BTS 2K4 and the HIPAA Accelerator 3.0, which I feel are worthy of a mention.

  1. SQL Server 2000 client components are needed on the BizTalk boxes when SQL Server 2000 is installed on a separate box.
  2. DTC (Distributed Transaction Coordinator) must be enabled for Network Access (via Windows Component Setup) on all computers participating in the configuration, administration and message processing.
  3. The user under which the HIPAA EDI windows service is configured to run, must be a member of the BizTalk Application Users group.
  4. All HIPAA 3.0 schemas should be validated using the XSD2EDI utility located at ......Program Files\Microsoft BizTalk Accelerator for HIPAA 3.0\HIPAA_EDI\Subsystem at least once (on all BizTalk boxes where HIPAA is installed) before the HIPAA Accelerator can start processing messages.
  5. For multi-box BizTalk Installations you might want to consider making the HIPAA Documents Home directory a network share.
  6. For ANSI 835p there exists a context property named CountOfTranslatedDocs, which can be used for correlating 835's from a single file into a sequential convoy.
  7. Ensure that the login credentials for the HIPAA EDI Windows service and the BizTalk Host under which the HIPAA Adapter runs, match.

More additions later. Any queries, post a comment.

View complete post...