Corolar Release 7.0.1 (Hotfix #1 for 7.0.0)

Description

Corolar Hotfixes are a collection of hotfixes for issues that have been identified within the Dapasoft Corolar product. Corolar Hotfixes are cumulative, however each hotfix describes only the fixes added since the previous Corolar Hotfix. Thus, prior Hotfix release notes should be reviewed for information regarding earlier published fixes.

Note: This Hotfix requires Corolar 7.0.0 installed

New Features

A new component is shipped in Corolar Release 7.0.1 as part of an SDK package.The package can be found in the <CorolarInstallation folder >\SDK folder.

It is a sample piece of code for a Pipeline Component allowing the user to:

  • specify a custom namespace for an HL7 v3 schema
  • Automatically generate an HL7v3 ACK/NAK by setting a flag in the pipeline component property

Affected Components

The affected components section describes the Corolar components for which this particular release applies.

Corolar Monitor – Code Set Table Mapping

This hotfix addresses a number of issues identified in the Corolar Monitor Tool When a user tries to import a file for Code Set Table Mapping, user may encounter an error

Symptoms:

User may encounter an error “Server Error in /CorolarMonitor Tool Application” after choosing a file to be imported into Code Set Table Mapping.

Cause:

Sometimes the internet browser uses the full file name with the full path as the filename, and Corolar Monitor was only expecting the filename, therefore causing an error.

Solution:

Apply Corolar Release v7.0.1.

Corolar Monitor – Security Settings

Weird characters in the Role Configuration Description of Code Set Table Mapping

Symptoms:

When the user goes to Security Settings, into Role Configuration, the description for Code Set Table Mapping contains some weird characters.

Cause:

This is caused by an error in the description text

Solution:

Apply Corolar Release v7.0.1.

Corolar Monitor – General

The IIS log file diag.svclog and traces.svclog is taking up a lot of diskspace

Symptoms:

The log file for IIS “diag.svclog” and “traces.svclog” sometimes take up a lot of diskspace (upwards of Gigabytes) under C:\log.

Cause:

Corolar Monitor writes all the log to those 2 log files, if there are lots of activities then the log files will grow substantially.

Solution:

  • Apply Corolar Release v7.0.1.
  • Delete existing log files.
  • Restart IIS and run Corolar Monitor.

Corolar Monitor – Message Resubmission

Resubmit All does not work under Message Resubmission in Corolar Monitor when the resubmission is done via 2-way MLLP receive port.

Symptoms:

When the user tries to resubmit multiple messages using the “Resubmit All” button resubmitting via a 2-way MLLP resubmitting receive port, the user gets an error in the Windows Event Log:
Error in resubmission process, failed to send message to BizTalk using MLLP. Please check the BizTalk resubmission interface.

Cause:

There is an issue with the Corolar Reusbmission pipeline component causing the resubmission to fail.

Solution:

Apply Corolar Release v7.0.1.

Corolar BizTalk Artifacts

This hotfix addresses an issue identified in the Corolar BizTalk Artifacts When applying a BizTalk Map that maps to an HL7 message with only MSH segment (and nothing else), it causes the message to be suspended.

Symptoms:

When an outbound BizTalk Map that has a destination HL7 message that only has MSH segment, it causes an error in BizTalk and the message is suspended. The error message looks like this: 
A message sent to adapter “XXXX” on send port “XXXXXXXXX” with URI “XXXXXXXXXXXXXXXXXX” is suspended.
Error details: The Messaging Engine failed while executing the outbound map for the message going to the destination URL “XXXXXXXXXXXXXXXXXX” with the Message Type “http://microsoft.com/HealthCare/HL7/2X#XXXXXXX”.
Details:”There are multiple root elements. Line 1, position 79.”

Cause:

A bug in the Corolar Receive Post Processor causes this issue.

Solution:

Apply Corolar Release v7.0.1.