When writing to the PM user session log, the set login attempt needs to use the database timestamp instead of the calendar.getInstance().getTime(). This will prevent queries from generating an error when trying to write to the log at the same time.

Part of the problem is the PM user session log has a primary key in which two entries cannot have the same user and date-time. When a query runs it is the service account that is logged as the user. So if two or more people are running a query (ontology, setfinder, pdo, etc) and the crc is trying to write to the log at the exact same time, then only one entry will file and the other entries will error because the system thinks it is a duplicate.

Temporary work around is to delete the constraint on the log.