In order to check a project or article in, the file repository needs to have both read and write privileges. In this case the administrator opened his Administrator Client and noticed that the status of the file repository had switched to Read Only. It turned out that the Helios server that was acting as the file repository did not give the Helios process the CPU time it requires when the server machine became busy. As a result, the status of the file repository status was read by the QPS Server as Read Only.

Solution:

  1. Deactivate users currently logged into QPS.
  2. Reset the path to the file repository.
  3. Reactivate all users.