• "CRITICAL ERROR: One or more binders in your Local File Room require your attention. The finalization process for the following binder(s) did not complete successfully. The binder(s) listed below cannot be deleted from the Local File Room until this problem is corrected. Please contact Technical Support for assistance before continuing work on these binders."
• Pressing Retry will continue to generate the error.
• Clicking ok results in the binder generating a "Partially Failed" message when attempting to sync the binder
• May receive error "Error Number -2146233088 Error Description: Cannot create temporary file" instead of Critical Error message
• Binder appears in CFR with finalized icon and red exclamation point. Finalization process will not complete from local file room.

• Version 2020.1.3 and 2020.2.1

N/A

• Note: The CCH® ProSystem fx® Engagement version 2020.2.2 release will have this updated/patched dll already. Do not apply this patch or dll to any prior or later version of Engagement or Workpaper Manager than versions 2020.1.3 and 2020.2.1. The patched file is not intended for any other versions than those specifically listed in this article title. Once 2020.2.2 is applied, all repairs, new installs, and reinstalls will also have the fix.
• Additional Note:  If running CCH® ProSystem fx® Workpaper Manager, there is currently not a version 2020.2.2 available.  To resolve please follow the steps listed below to apply the CommonLibrary_Update.exe patch.

• CommonLibrary_Update.exe
• NOTE: If the link above does not start the download please try the link in the attachments section to the right.
• NOTE: If the patch is deployed then a subsequent repair OR uninstall/reinstall install of CCH® ProSystem fx® Engagement or Workpaper Manager occurs the patch will need to be run again.
• Once the patch is run, restart the pfx services on the machine.  For instructions, review our article How do I start, stop, or restart the CCH® ProSystem fx® Engagement or Workpaper Manager services?
• If you would like to deploy the dll manually or script pushing it to multiple machines you can do so with the following dll download:
  • Download dll file from the following link or copy URL below: Pfx.CommonLibrary.dll
    • http://d2iceilwdglxpz.cloudfront.net/download/Commonlib/Pfx.CommonLibrary.dll
    • The same file can be used in 2020.1.3 of 2020.2.1 to correct the patched trigger to this issue.
  • Unblock the file if it has been blocked on download.
    • Right click the file in File Explorer.
    • In the context menu, select the last item named "Properties".
    • In the Properties dialog, on the General tab, tick the checkbox named "Unblock"
  • Browse to this location on the user's machine:
    • C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Pfx.CommonLibrary\v4.0_2020.1.1.1__21b98a3ae763e7ad
  • Rename existing pfx.commonlibrary.dll by appending OLD to the beginning
  • Copy new pfx.commonlibrary.dll to
    • C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Pfx.CommonLibrary\v4.0_2020.1.1.1__21b98a3ae763e7ad
  • Close and reopen Engagement.
  • Also put this dll onto the server install and restart the pfx services or reboot.

1. Click Tools > Restore Binder.
2. Navigate to ?:\Pfx Engagement\WM\Failed Finalization Backups folder
3. Select the backup file for the binder in question.
4. Restore the binder.
   • The restore process is restricted and the user may need assistance getting the right to restore a binder, if only temporarily, from their Engagement or Workpaper Manager Administrator:
     • How do I edit the staff rights for CCH® ProSystem fx® Engagement or Workpaper Manager or Workpaper Manager users?
5. Verify the contents of the restored backup.
6. Delete the Central File Room copy of the binder.
   • For instructions to delete a Central File Room binder,  Review the article How to delete a binder from the Central File Room (CFR) in CCH® ProSystem fx® Engagement or Workpaper Manager?
7. Synchronize the binder.

• How do I create a support case on support.cch.com?
• What are the phone tree options for 1-800-739-9998?

N/A