"There was a problem while committing: File is locked." Error Message

"There was a problem while committing: File is locked." Error Message

If the "There was a problem while committing: File is locked." error message occurs in Content Central when attempting to Access or Capture a document into the system to either the Coding Queue or the Folder Browser, this may be due to insufficient permissions for the System Folder on the Content Central Server where the electronic files are stored. 

In order to resolve this item, the user in charge of the Content Central server would need to log into the server with the correct permissions and follow the steps below:

1. Access the Content Central server and Open the Content Central Configuration Manager.


2a. From the Configuration Manager go to the System Folders section and follow the folder path of the "Document Root Folder" using the Server's File Explorer (This is if the error message is occurring when attempting to Access or Capture a document for a specific catalog folder).


2b. From the Configuration Manager go to the System Folders section and follow the folder path of the "Coding Queue Root Folder" using the Server's File Explorer (This is if the error message is occurring when attempting to Access or Capture a document in the Coding Queue).


3. Once you are at the System Folder location in the Windows Server's File Explorer, right click on the folder specified in the previous step and select Properties. From the Document Properties menu, select the Security tab and verify whether the "Network Service" account is enabled with 'Full Control' permissions. If it is not, add the "Network Service" account and grant it 'Full Control' permissions, then click OK. 


Side Note: Additionally one other area you may wish to check to verify whether the "Network Service" account is enabled with 'Full Control' permissions would be in the following file path "C:\inetpub\wwwroot\ContentCentral"

4. After the account has been added or granted the permissions specified in step 3, the error message should no longer occur and the users should be able to Access or Capture the documents in the Content Central system once more.