Corolar Release 6.12.0302.1 January 2013 Hotfix2

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.

Affected Components

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

Dapasoft Corolar Pipeline Components
Corolar Solution Templates

The hotfix addresses several issues identified within the Dapasoft Corolar Pipeline Components and the Corolar Solution Templates.

Fixes

Corolar NonHL7InputSendPipeline generating errors

Symptoms:

The following error may occur on the NonHL7InputSendPipeline’s Send-PreProcessor component:

There was a failure executing the send pipeline: “Corolar.HL72XPipelines.CorolarHL72XNonHL7InputSendPipeline, Corolar.HL72XPipelines, Version=0.0.0.0, Culture=neutral, PublicKeyToken=611b6ec93f28c00a” Source: “BTAHL7 2.X Assembler” Send Port: “TestSend” URI: “” Reason: Header part stream is null

A message sent to adapter “XXXX” on send port “YYYYY” with URI “ZZZZZ” is suspended. Error details: There was a failure executing the send pipeline: “Corolar.HL72XPipelines.CorolarHL72XNonHL7InputSendPipeline, Corolar.HL72XPipelines, Version=0.0.0.0, Culture=neutral, PublicKeyToken=611b6ec93f28c00a” Source: “BTAHL7 2.X Assembler” Send Port: “TestSend” URI: “ZZZZZ” Reason: Header part stream is null

Cause:

This is due to a defect within the Send PreProcessor of the Corolar NonHL7InputSendPipeline which is unable to create a Header part stream for downstream pipeline components.

Solution:

Install Corolar Release 6.12.0302.1 January 2013 Hotfix.

Corolar NonHL7InputSendPipeline having unrelated pipeline component properties

Symptoms:

The NonHL7InputSendPipeline has “LogPath” and “LogPrefix” properties in the Send PreProcessor component. These two properties should not be there, please refer to the Corolar Configuration Guide for further information.

Cause:

The Corolar Solution Templates where not updated appropriately to represent the unused “LogPath” and “LogPrefix” pipeline component properties correctly. This resulted in the properties appearing within the pipeline component.

Solution:

Install Corolar Release 6.12.0302.1 January 2013 Hotfix