Hi Eric and welcome to Sage City!

13.1 Revision 5 and 6 have the Pervasive Monitor Utility patch wrapped into them.

However, we do have a separate patch that can be run for your version of 13.1 Rev 4.

The pervasive patch for your version (13.1 Rev 4) can be found in the Knowledgebase searching for ID:16867

In the KB, there are 2 different files to choose from for the server depending on what bit your OS runs on and there is only one choice for the workstation.

Thanks Brian! I actually found that this morning after digging some more and i can now clear sessions. I have another issue with permissions I would like to ask you and the rest of the community about. I've checked the req document and have given EVERYONE group full permissions to all the folders & registry keys it talks about requiring. But when I open Sage as a domain user it creates 4 sessions in the monitor, and when I close it it leaves 3 behind.

Have you seen that before? If I open the software as a local admin (or add the user to local admins) I can see it properly opening & closing the sessions in the monitor utility. It's clearly a permissions issue, but where?

Eric -

What you are seeing in the Pervasive Monitor Utility with one or multiple user IDs is called a communication thread.

Depending on what that particular user has rights to and what tasks they may be using when logged in the software will dictate how many communication threads get created and reported by the PMU (Pervasive Monitor Utility).

So in essence you are correct in that depending what "permissions" they have in the software will dictate how many threads are created. However this shouldn't be a cause for concern. That is the system working normally.

If you have left-over communication threads in the PMU after a user logs out, that can indicate a few different things.

If there isn't a file associated with the communication thread and people can access the data normally then there shouldn't be an issue. It can be as benign as a random packet of data floating in the system and the PMU notices it.

Bottom line is if there are no problems with accessing the data and you have some communication threads left in the PMU after users log out, it isn't a cause for concern.

Hope that helps!