A bug in Pentana Audit means that it is possible to Accept a Document Request even if that Document Request has attached to it a file that is reserved.   This is not allowed for other record types (e.g. Action Updates), and leads to the following problem behaviours:

• The file remains in your "My Reserved Files" home screen tile for ever
• You cannot delete the parent Step or Test

At this time the only solution is to remove the reservation directly in the database, using the attached script template.

To use the script:

• Edit the attached script.  You will need to know the GUID of the reserved attachment.  To find this:
  • Open Pentana Audit, and navigate to the Document Request
  • Click the Attachments icon to expand the list
  • Right click on the Attachment
  • Select Copy Shortcut
  • Open notepad
  • Paste
  • From the pasted text, select the text that looks like:  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  • Copy this text
  • Paste it into the script, overwriting the example on the first line of the script
  • Demonstration of this procedure is here:  Obtaining the GUID from a copied document
• Stop the Retain Server service (where present)
• Stop the Pentana Audit robot service
• Stop the Pentana application pools
• Back up the Pentana database and verify
• Back up the Retain database and verify (where present)
• Run the edited script it should run without error
• Restart the Retain service (where present)
• Restart the Pentana app pools
• Restart the Pentana Audit robot service
• Verify effect of change:
  • you should now see that the attachment is not reserved

The script should first be run in a test environment to verify the change is as required.

Note that:

• this issue affects Audit Tests and Steps but not Entity Tests
• it will not be possible for the user to has reserved the file to check it back in after this script is run

Thanks to Alain Rousseau at Sepia Solutions for his suggestion for improving this process.