I have a client using SAGE 100 STD v2017 (5.40) PU#5 on a Windows 2012 R2 server.  They are getting random lockups and "unlock region failure" messages. I viewed the System Activity Log and found that many of these types of errors are preceded by "Error: 261 SY_Session.pvc Line=xxx" (see attached SAGE KB image). 
They have between 5-8 SO Invoice Data entry users and several Customer Inquiry users in the system almost all day.  If I follow the SAGE KB instructions, perform a system backup, and rename the SY_Console.M4T and the SY_Workstation.M4T files, will I end up with any Unintended Consequences?

------------------------------
Michael McDonald
Consultant
Michael T McDonald CPA
Sparta MI
616-813-8887
mike@mcdcpa.com
------------------------------

Keep a copy of the files, just to be safe.  These files are system generated, so when you rename them, they are recreated when needed (as soon as a user logs in).  Standard procedure ;)

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

Is this perhaps needed? 

My experience is that wiping/recreating those files can be somewhat helpful but more often are bandaids

Cannot create a new session with a large number of users

Products

Sage 100

Description

<content>

• Cannot create a new session with a large number of users in Sage 100 (Formerly known as article SS3003-ABC)
• "WindX client connection: Connection Timed Out waiting for your application to start"
• Blank white screen displays when opening Sage 100 Advanced tasks
• Unable to start a new window or task in Sage 100 until a previous one is closed.

</content>

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

The "unlock region failure" error is hardware related... see Sage KB article 30437.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------