I think there are two other system tables to delete but as I am on Standard I can't look them up and I can't remember their names off the top of my head. Maybe someone on here can remember or you can call Sage Support.

Kick everyone out. Shut down the sage 100 host. Go to task manager and kill any remaining pvxwin32 processes.

If you still have the problem try renaming sy_session.m4t in addition to sy_workstation.m4t. Don't delete them, just rename. I remember in the past dealing with sy_session but couldn't confirm from the knowledgebase. So please rename so you can restore it if necessary.

The file to rename you were looking for may be SY_Console.M4T (...\MAS90\MAS_SYSTEM) as this is commonly renamed with SY_Workstation.M4T (with all users out of Sage 100).

The following information might be helpful:

If the phantom task and the workstation are identifiable in Master Console:
1) At the workstation, close Sage 100, 2) Open Windows Task Manager, 3) End any PVXWIN32 processes

If all the users are out of Sage 100, then on the Sage 100 server, Clear Open Files
1) In Windows Server 2012 R2, Select Administrative Tools, Computer Management, Shared Folders, Open Files
2) All files currently used by the server appear in the right pane
3) Right click any files that have the Sage 100 directory in the path and select Close Open File
(from KB 41722 in Sage Knowledgebase).

To kill "ghost" tasks from the Server:
Kill all PVXWIN32 processes on the server using Task Manager.
Have all users exit Sage 100, for Sage 100 ERP Advanced or Premium, stop the Application Sever Desktop App or Service
Open Task Manager.
Click the Processes tab, and then click the Image Name column heading to sort.
Select the Show Processes from all users check box (if not checked).
Select PVXWIN32, and click the End Process button until all tasks are ended.
To Kill tasks via Master Console: Use the Kill Tasks button in Master Console. Note: Sometimes this option is not possible.
Restart the Application server service
(from KB 20125 in Sage Knowledgebase).

If this is a commonly occurring issue and there may be corruption in the Application Server configuration (such as repeated connection issues or locked/"Phantom" tasks stuck) then it is sometimes recommended to:
1) Stop the Application Server and close the Application Server Configuration application.
2) On the Sage 100 server, rename:
..\MAS90\MAS_System\SY_Console.m4t file
..\MAS90\home\lib\_appserv\LOCATE.PVK
..\MAS90\home\lib\_appserv\SESSIONS.PVK
3) Restart the Application Server.
4) From the Windows desktop on the Sage 100 server, click the Start button. On the Programs menu, select Sage or Sage Software - depending on Sage 100 version, and then click Application Server Configuration. (new LOCATE.PVK and SESSION.PVK files are created).
5) Click the Server Tab. Clear the KeepAlives check box.
6) Click the Clients Tab. On the Re-Connect list, select None.
7) Select Apply
8) Close the Application Server Configuration window.
(from KB 19887 in Sage Knowledgebase)

Thanks DGR! You found it. Don't know why I couldn't.

Thanks DGR, and the rest.
This solved the problem. No more stuck session.
Sorry for the late reply.
Regards,
Bret