We have only seen this error occur in clients where Ivo is being accessed remotely, and in those cases, it has been related to staff not ending their remote sessions - they 'disconnect', instead of 'logging off', and they leave Ivo still running in the disconnected session.


To resolve the issue -

  1. have everyone close Ivo
  2. once everyone has closed Ivo, have one person only try to logon -
    1. If they can, then it is all good and everyone can get back on to Ivo
    2. If they can't, then keep everyone out of Ivo and have your IT support
      1. connect to their terminal server and close any Ivo processes that are running (they will know what this means). After that, it should be fine again. If not, then go to next step.
      2. If there is no terminal server, then it means someone has an Ivo process still running. Try connecting to the file server upon which the Ivo data file resides and removing any file locks to the data file (Ivo_Data.ivo).
      3. If that still doesn't work, then have every use restart their computer (this would be a last resort; we've never had to have a client do it).