Critical Platter Management Error - Unable to make file read-only

[Cameron_Gray]

Hi all -

A customer got the error:

Critical Platter Management Error. Call Tech support.

Unable to make file read-only. \\uncshare\imagedstmts\v80\1279\6991770.img

79.

It occurred during a COLD Process that was processing in approximately 500 documents, and this error occurred around 420. After clicking OK on the error, the documents continued to process in normally. Does anyone have an idea of what could have caused this? I have seen several different Critical Platter Management Errors on this site, but none that dealt with being unable to make the file read-only.

Thanks,

Cameron

[ptam]

Hi Cameron,

It is difficult to say the exact cause as the low-level file system error is not present in the error message.  The "79." denotes this error occurred during a commit operation.  Have you continued to see this error?  Some possible causes are:

• Someone else opened the file.  This is unlikely since it is the committed platter and not the primary platter .
• A virus checker had the file open for processing at the same time OnBase attempted to set the file to read-only.
• The committed storage location is a WORM or other retention device.  You would likely see the error for every file if this were the case.

It the error continues to happen you could use the tool Process Monitor (available from Microsoft) to monitor and record the low-level file system error that caused the error to be reported in OnBase.

Thanks,

Paul Tam