That's the new current user tracking log file, one file is created per user per company (it seems). Files are deleted when the user closes the company. Maybe the user's don't have permissions to delete files in the Company folder?

I was getting the same errors on my development system. I was able to track down the cause of the event log errors. When you load OE1100.OCX from a VB or a VBA project it generates that error in the event log.  Is there a fix out there for this?  It doesn't appear to be causing any problems but we don't want these errors filling up our windows event logs.

Development system:

Sage 300 ERP 2014 PU3

Windows 7 Pro

SQL Server 2008 R2

Contact Sage support.

Sage development is investigating into this error. I will reply when we have more information.

I am seeing similar event logs as ERRORs in Event Viewer. I know they are an issue because I have users telling me the system has crashed i.e. things keep timing out while trying to close work orders, issue material etc. The event logs correlate with the exact time the system 'times out.' Please advise of any fix.

Error: userMgtLockCapture: File already exists. File ="C:\Sage\Sage300\COMPANY\userMgtLogs\userMgt-E9498196-03BE-4DD4-9CCC-7678DCE1F29F.lock.log"

We've seen performance slowed due to this feature, or some knock-on effect of it, at some sites. Our solution was to disable by customising .\runtime\a4w.ini by adding the folliwng lines to the end of the file:

[UserMgt]

CaptureTask=0

Stephen Smith commented on this a while back.

Did Sage come up with a clear solution for this issue. I don't seem to see it in the below thread. 

Just ignore them, they're a harmless error.