It turns out that the way I was doing my querying of tables for information, the MapInfo .TAB files for certain members were so large that it was overwhelming the memory and hanging MapInfo Professional. I had to rework from the beginning how I needed to accomplish this task. Ultimately, I worked with Claude to modernize this process I had built easily 15 years ago. Everything works now after a few days of having time to modernize.
In the end, it was the fact that old code could not support the growing dataset size in MapInfo .TAB files.
Thanks again for your suggestions.
Original Message:
Sent: 03-05-2026 04:49
From: Peter Møller
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
If your running MapBasic application want to shut down the current session of MapInfo Pro, I would recomend using the End MapInfo statement.
I had a look through the release notes for v2021.1 to see if any caught my eye. I don't see anything that obviously would prevent MapInfo Pro from being shut down.
Do you have any tables open or connections to databaes open, when you try to shut it down?
Your experience clearly state that something has changed but I can't detect what.
Would you be able to try to use the End MapInfo statement instead to see if that makes any difference?
------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
Original Message:
Sent: 03-04-2026 08:18
From: Nicholas Evanish
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
Peter,
Good morning. The job runs to completion; however, when the program attempts to kill the MapInfoPro.exe (using a MapBasic program referenced in my first post) that MapInfoPro.exe is no longer closing.
It looks like what is happening is the MapInfoPro.exe instance is left orphaned with a very small amount of memory usage recorded.
For example, this morning a process ran at 0015, and it completed around 0135. However, the MapInfoPro.exe process stayed running on the server (see image):

I hope this helps give more clarification as to what is now happening. This solution had worked up until (2/25/2026).
------------------------------
Nicholas Evanish
Senior Program Analyst
Original Message:
Sent: 03-03-2026 03:19
From: Peter Møller
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
Hey Nicholas
Are you saying that your jobs don't shut down MapInfo Pro anymore when they are finished?
If that's so, do you know where they halt/stop in the execution?
------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
Original Message:
Sent: 03-02-2026 19:56
From: Nicholas Evanish
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
All,
I have had several automated instances of MapInfo Professional that run to analyze .TAB files throughout the day. These have been running for almost 15 years. I upgraded them to the latest version we are using which is MapInfo Pro v 2021.1 Build 33.
Starting on February 25th for some reason, at the end of the processing, the code runs a MapBasic command to kill the process ID that the MapInfo Professional instance is running on the server. (See mapbasic code below)
====================================================
Declare Sub Main()
Declare Function TerminateProcess Lib "kernel32" (ByVal hProcess As integer, ByVal uExitCode As integer) As integer
Declare Function GetCurrentProcessId Lib "kernel32" () As integer
Declare Function GetExitCodeProcess Lib "kernel32" Alias "GetExitCodeProcess" (ByVal hProcess As integer, lpExitCode As integer) As integer
Declare Sub ExitProcess Lib "kernel32" Alias "ExitProcess" (ByVal uExitCode As integer)
Sub Main
Dim pid As integer, excode as integer, retval as integer
pid = GetCurrentProcessId()
IF pid > 0 THEN
retval = GetExitCodeProcess(pid,excode)
call ExitProcess(excode)
END IF
End Sub
====================================================
My question is what could all of sudden cause this to happen?
- MapInfo Pro was not updated in any way
- The server did not have any Windows Updates installed
The only lead I have is the server's Event Viewer log is showing the following:
================================================
Faulting application name: MapInfoPro.exe, version: 21.0.1.33, time stamp: 0x639b24f8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000000000c
Faulting process id: 0x7e4
Faulting application start time: 0x01dca699ba728fea
Faulting application path: C:\Program Files\MapInfo\Professional\MapInfoPro.exe
Faulting module path: unknown
Report Id: 09f4ab29-1292-11f1-80fc-005056986225
Faulting package full name:
Faulting package-relative application ID:
EventRecordID 1449822
EventID 1000
================================================
Anyone that may of experience this same thing? I would appreciate any insight if anyone has had a similar experience.
Thank you.
------------------------------
Nicholas Evanish
Senior Program Analyst
------------------------------