Fixes are available
APAR status
Closed as program error.
Error description
We are getting the C:\Program Files (x86)\IBM\Personal Communications\autsess.dll error with version 12.0.0 on Windows 10 Long Term Servicing Branch LTSB 64-bit with Office 2016 32-Bit.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Using HACL Automation objects of IBM Personal Communications * * on Windows 10 Environment * **************************************************************** * PROBLEM DESCRIPTION: * * Invoking PCOMM HACL Automation object calls from a VBA * * application could crash the calling application. * **************************************************************** * RECOMMENDATION: * **************************************************************** Environment: IBM Personal Communications v12.0 on Windows 10 Invoking PCOMM HACL Automation object calls from a VBA application could crash the calling application. For instance, when a VBA macro is run from a Microsoft Excel application to connect to an existing PCOMM emulator session, the Excel application may crash reporting access violation inside the AutSess.dll module. A possible exception information would be as below: Faulting application name: EXCEL.EXE, version: 16.0.4366.1000, time stamp: 0x56e81993 Faulting module name: autsess.dll, version: 12000.0.16050.170, time stamp: 0x56c6e94d Exception code: 0xc0000005 Fault offset: 0x000050cb Faulting process id: 0x184c Faulting application start time: 0x01d1ac27693cf939 Faulting application path: C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE Faulting module path: C:\Program Files (x86)\IBM\Personal Communications\autsess.dll Report Id: dc4e42a7-181a-11e6-9bdf-64006a517d8c The problem is intermittent and may occur only on a few Windows 10 environments.
Problem conclusion
Investigation showed that the exception was reported while unloading AutSess.dll. However, there was no concrete evidence to show that AutSess.dll was at fault. However, using .NET Framework 4.6.1 to build the PCOMM's HACL Automation libraries resolved the reported abnormal termination. In addition, investigation showed a couple of first chance exceptions inside PCSCLIB.DLL and PCSWKBD.DLL. Code changes have been made to address these exceptions. The fix for this reported crash includes addressing the exceptions and building HACL Automation libraries using .NET Framework 4.6.1. Fix scheduled for PCOM 12.0.2.0 and 6.0.19 Refresh Packs.
Temporary fix
Comments
APAR Information
APAR number
IT17832
Reported component name
PCOMM COMBO-ENC
Reported component ID
5639I7000
Reported release
C00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-07
Closed date
2017-04-19
Last modified date
2017-04-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
AUTSESS
Fix information
Fixed component name
PCOMM COMBO-ENC
Fixed component ID
5639I7000
Applicable component levels
R60G PSY
UP
RC00 PSY
UP
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSEQ5Y","label":"Personal Communications"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C00"}]
Document Information
Modified date:
26 September 2021