Corolar Release 7.0.2 (Hotfix #2 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

Affected Components

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

Installer

This hotfix addresses a number of issues identified in the Installer

The v7.0.1 installer fails to run on a machine without BizTalk installed

Symptoms:

When installing Corolar v7.0.1 on a machine with Corolar Monitor installed, but without BizTalk installed, an error pops up saying “Error” before the Welcome Screen shows up.

Cause:

This is an issue caused by some unrecognized InstallShield Behaviour

Solution:

Apply Corolar Release v7.0.2.

The Corolar Account entered during installation is sometimes unable to be set to “Run as a service”

Symptoms:

Corolar Alert Service and Corolar Resubmission services are unable to start because of permission issue.

Cause:

Sometimes the installer is unable to set the Corolar Account to have permission to “Run as a service”. When that happens the Corolar Alert Service and Corolar Resubmission Service will not be able to start

Solution:

Apply Corolar Release v7.0.2.
During installation, it will prompt for Corolar Account again. Make sure to use the same account/pw as the one used during v7.0.0 installation.

The installer is sometimes unable to save the Corolar Monitor Administrator user properly during installation

Symptoms:

After installing Corolar v7.0.0 and when the user tries to open up Corolar Monitor by logging in as the Administrator specified during Corolar v7.0.0 installation, they get an “Access denied” error.

Cause:

The installer save the account/pw only when Corolar Database is selected as part of the install. Thus, if only the web front-end was chosen, it collects the information but does not write that info to the Corolar Database.

Solution:

Apply Corolar Release v7.0.2.
The installation process will prompt for the Corolar Monitor UI Administrator account. It will save the info properly in the Corolar Database.

The installer generates an error that the web.config file cannot be found

Symptoms:

If the v7.0.1 installer is run on a machine that does not have Corolar Monitor web frontend installed, it throws an error saying web.config is not found

Cause:

The way the installer detects the existence of Corolar Monitor Tool causes it to think it was installed but in fact it was not, and hence, the web.config does not exist.

Solution:

Apply Corolar Release v7.0.2.

Corolar BizTalk Artifacts

This hotfix addresses an issue identified in the Corolar BizTalk Artifacts

Corolar send pipeline causes an out of memory error when outbound map uses mass-copy of the whole message.

Symptoms:

User may get an out of memory error when using Corolar HL7 2X Send Pipeline with an outbound map that does a mass copy of the whole message from input to output.

Cause:

The problem is caused by a Corolar Pipeline Component in identifying the MSH tag in the XML form of the HL7 message.

Solution:

Apply Corolar Release v7.0.2.