AnsweredAssumed Answered

Operator.LOCK File Generation

Question asked by dbailey on Jan 4, 2011
Latest reply on Dec 28, 2011 by dbailey
We have three i3070 machines, one is an IPC and the other are HP PCs.  When logging in as 'operator' the IPC will occasionally not load the rmiserver and then a file is created in c:\agilent_ict\log named operator.LOCK.  Re-logging in as 'operator', the operator.LOCK file prohibits the operator GUI to load. 

The file .LOCK file contains one line, "i5000 already running".  Deleting the file allows normal operator log in to occur and testing can resume.

This phenomenom has only been witnessed after power up of the i3070, not when logging out and logging in again alone.

Anybody have a clue to what's going on?  I have a service request logged, so if support answers this first, I'll report back.