Re: DLL problem from Vsamex.dll causes the crash Logger32 go down when telnet to the cluster is ON

Bob <k4cy@...>

VSAMEX.DLL is the database engine. I have connected to IK5PWJ-6 Telnet cluster all day. No problems. 73.

On 01/23/2021 1:31 PM Alex Del Chicca <ik5pwj@...> wrote:

Hi all,

the error that causes the Logger32 program to close as explained in the msg. that I report below,

is shown in the Windows 10 PRO 64 Bit Event Viewer that I am using.


Below I insert the msg. Error found in Windows Logs / Application Level / Error / General:









    C: \ Logger32 \ Logger32.exe

    C: \ Logger32 \ Vsamex.dll



And in Windows / Application Level / Error / Details:


Name of the application that generated the logger32.exe error vers, timestamp: 0x60033d98

Module name etc .....

Exception code: 0x c0000005

Error offset 0x0004c 1f8


Path to the module that generated the error: C: \ Logger32 \ Vsamex.dll


So ….i’s    Vsamex.dll    that causes the Logger32.exe program crash to close

Anyone know why and how to solve this problem?


73 Alex ik5pwj.


Da: <> Per conto di Alex Del Chicca via
Inviato: sabato 23 gennaio 2021 17:24
Oggetto: [hamlogger] Logger32 go down when telnet to the cluster is ON


Hi to ALL,

I upgraded from the latest version 3.5 to version 4.0 without any errors.

After doing database maintenance and updating statistics, I updated to ver. 4.0.235 without problems.


The open windows are: Operator :, Dx Spots, Worked / Confirmed Logbook page, Previous QSOs and Telnet for IK5PWJ-6 cluster connection,

I also opened the CW Machine window.

Unfortunately after some time, sometimes 30 min. others after an hour the Logger32 program closes, leaving only the window outside

the Logger32 Window of the CW Machine open.


In practice the window of Logger32 disappears.


I then made several tests, reinstalling the logger32 vers. 4 from vers. 3.5 where I had previously deleted all the log

and then reinstalled the ik5pwj log from the previously saved adif file.


Unfortunately, the problem reoccurred by going the Logger32 program down and always remaining the CW Machine -Software window.


At this point I did a test and I disabled the connection via telnet to the cluster no longer receiving the spots both

in the Telnet window and in the DX Spot window.


Well .... the Logger32 program ran for hours without closing.

I am sure that the block depends on the right spots that the telnet receives and sends to the DX Spots window,

because if I reactivate the telnet connection and the spots start to arrive again, the program goes down again.


What's up ? and how can this problem be eliminated?


When I use the same configurations on the latest version of the program vers. 3.5 .... everything works,

including telnet and spot-free spots or whatever.


Thanks for any Help

73 Alex ik5pwj.


Join to automatically receive all group messages.