Conference abbott::teamlinks_windows

2018.0. "Can't load Custom Control DLL on TX4VBB.VBX" by GIDDAY::LEH () Mon Mar 03 1997 06:28

TL 2.7 on WfW 3.11

A conflict with another Windows application called Systems Engineer SE version 
6.12 caused TL fail to invoke when SE is already an active session

The failure was

        Can't load Custom Control DLL:
        C:\WINDOWS\SYSTEM\TX4VBB.VBX

and no CFCDEBUG file was created.

The reverse scenario caused similar disruption when TL is already an active 
session, invoking SE caused the application to stay in indefinite hour-glass 
and its task was not seen in Task Manager. A shutdown/restart of Windows is 
then required.

This symptom was different from 2.7 EFT3 environment, when it was reported in 
note 1579 as a GPF and no follow up was in QAR#2928.

SE support confirmed they're not using TX4VBB.VBX and suspected :

...this VBX module is trying to exclusively use a .DLL that is already in use 
(possibly by SE) or TL is trying to use a memory location that SE is already 
using...

They went on further nominating potential DLLs: COMMDLG, CTL3D and CTL3DV2; 
which were checked on the affected system as

C:\WINDOWS\SYSTEM	commdlg.dll	97936	6-sep-95
			ctl3d.dll	20272	10-mar-95
			ctl3dv2.dll	27632	14-jul-95

C:\WINDOWS		ctl3dv2.dll     21648	27-oct-94

C:\CORVU\CTL3D		ctl3dv2.dll     27632   14-jul-95
X:\ADMIN		ctl3d.dll	20976	15-sep-93
			ctl3dv2		21648	7-feb-94

(the last 2 sources are not on PATH, so can be ignored)

SE support also supplied a list of DLLs loaded by their own application when 
running under WfW

SHELL				C:\WINDOWS\SYSTEM\SHELL.DLL
MMSYSTEM			C:\WINDOWS\SYSTEM\MMSYSTEM.DLL
CSPMAN				C:\WINDOWS\SYSTEM\CSPMAN.DLL
COMMDLG	  4-SEP-94  97936	C:\WINDOWS\SYSTEM\COMMDLG.DLL
MSMIXMGR			C:\WINDOWS\SYSTEM\MSMIXMGR.DLL
WINMM16				C:\WINDOWS\SYSTEM\WINMM16.DLL
NETAPI				C:\WINDOWS\SYSTEM\NETAPI.DLL
PMSPL				C:\WINDOWS\SYSTEM\PMSPL.DLL
WIN87MEM			C:\WINDOWS\SYSTEM\WIN87MEM.DLL
AD05-100				C:\SE612\SEPPROG\AD05-100.DLL
HSKUTILS				C:\SE612\SEPPROG\HSKUTILS.DLL
IMUTILS					C:\SE612\SEPPROG\IMUTILS.DLL
DM01_001				C:\SE612\SEPPROG\DM01_001.DLL
SQLAPIW					C:\SE612\SEPPROG\SQLAPIW.DLL
IN01_001				C:\SE612\SEPPROG\IN01_001.DLL
METASESS				C:\SE612\SEPPROG\METASESS.DLL
REFINT					C:\SE612\SEPPROG\REFINT.DLL
PCODE					C:\SE612\SEPPROG\PCODE.DLL
DBCDLL					C:\SE612\SEPPROG\DBCDLL.DLL
DUAL					C:\SE612\SEPPROG\DUAL.DLL
ICON					C:\SE612\SEPPROG\ICON.DLL
SQLWSV					C:\SE612\SEPPROG\SQLWSV.DLL
OLESVR				C:\WINDOWS\SYSTEM\OLESVR.DLL
VER				C:\WINDOWS\SYSTEM\VER.DLL
LZEXPAND			C:\WINDOWS\SYSTEM\LZEXPAND.DLL
TOOLHELP			C:\WINDOWS\SYSTEM\TOOLHELP.DLL
CTL3DV2    21-SEP-94 21648	C:\WINDOWS\SYSTEM\CTL3DV2.DLL
HPPCL5G1			C:\WINDOWS\SYSTEM\HPPCL5G1.DLL
HPPCL5G2			C:\WINDOWS\SYSTEM\HPPCL5G2.DLL
HPPCL5G3			C:\WINDOWS\SYSTEM\HPPCL5G3.DLL
HPPCL5UI			C:\WINDOWS\SYSTEM\HPPCL5UI.DLL
HPTABS16			C:\WINDOWS\SYSTEM\HPTABS16.DLL
HPPJLMON			C:\WINDOWS\SYSTEM\HPPJLMON.DLL
HPLJCOMM			C:\WINDOWS\SYSTEM\HPLJCOMM.DLL
HPLJ4QP				C:\WINDOWS\SYSTEM\HPLJ4QP.DLL

Thanks for any help in identifying the conflict


Hong

Just for the record.

This problem is not related to note 1579 or QAR #2928.  That was a 
different customer, different problem.

As I remember it, there was no difference between EFT3 and SSB.

Malcolm