9.1.2.1: conflict with previous acurcl or acuserver installations

0 Likes

Problem:

acurcl 7.2 or 8.1 might not start anymore after extend® suite 9.1.2.1 has been installed on the same Windows server.

The acurcl (or acuserver) service is created but it does not start.
The Windows Event  Viewer reports the following error:

Faulting application name: acurcl.exe, version: 7.2.2.0, time stamp: 0x462fed5b
Faulting module name: MSVCR71.dll, version: 7.10.3052.4, time stamp: 0x3e561eac
Exception code: 0xc0000005
Fault offset: 0x00011da1
Faulting process id: 0x14c8
Faulting application start time: 0x01cdb77f8a7acc30
Faulting application path: C:\Acucorp\Acucbl722\AcuGT\bin\acurcl.exe
Faulting module path: C:\Acucorp\Acucbl722\AcuGT\bin\MSVCR71.dll
Report Id: c90bdb71-2372-11e2-8f5d-005056c00008

Resolution:

Starting acurcl 9.1 adds this registry entry:

HKLM\System\CurrentControlSet\Services\Eventlog\Application\acurcl\EventMessageFile

which points to the 9.1 acme.dll file. Then acurcl of any previous version does not start because it tries to load this 9.1 acme.dll.

The workaround is to manually edit that registry entry to point to the version you want to start.

Please note that AcuServer creates a similar registry key and may be affected by the same problem.

This behavior is now fixed and starting with release 9.2.0 the key will contain a reference to the version of the service:
i.e.: HKLM\System\CurrentControlSet\Services\Eventlog\Application\acurcl 9.2\EventMessageFile

Claudio Contardi
Product Support Engineer, Senior
Micro Focus

Comment List
Anonymous
Related Discussions
Recommended