"Partial Failure" and "Cannot create temporary file" error when attempting to sync after a failed finalization in CCH® ProSystem fx® Engagement or CCH ProSystem fx Workpaper Manager Version 2020.1.3 and 2020.2.1.

  • Article Type:
  • Problem Resolution
  • Last Modified:
  • 11/05/2022


  • Full Error Text:
    • "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.
  • "Error Number -2146233088
Error Description Failed to zip file. Files: C:\Pfx Engagement\WM\WorkPapers\{GUID}\{GUID}\{GUID}.xlsx ZipFile: C:\Pfx Engagement\WM\WorkPapers\{GUID}\{GUID}\SyncBAK\ZipTemp\{GUID}.xlsx.szp Error(xerCreateTempFile): Cannot create temporary file"


  • CCH ProSystem fx Engagement
  • CCH ProSystem fx Workpaper Manager
  • Version 2020.1.3 and 2020.2.1




This is an issue specific to the 2020.1.3 and the 2020.2.1 release. 
  • The latest Engagement and Workpaper Manager versions have resolved this issue and updating to the latest version is the preferred method to resolve this issue.
If unable to update at this time and still running Engagement or Workpaper Manager v2020.1.3 or v2020.2.1, please follow below:
  • Do not apply the below patch or .dll to any prior or later versions 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. Most current releases for Engagement and Workpaper Manager already have this fix applied.
We have created a patch installer to place a new .dll file on the workstations and servers for both versions 2020.1.3 and the 2020.2.1 version of  Engagement or Workpaper Manager. This new .dll will help avoid the issue in new finalization attempts. Please download and run this patch installer on all Engagement or Workpaper Manager workstations and servers in any order. 
  • 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 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. 
  • 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
    • 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.
To fix any binders that encountered this issue prior to the above patch or updates see below (we recommend that the patch is applied first on the machine before doing the fix below):
  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.
  5. Verify the contents of the restored backup.
  6. Delete the Central File Room copy of the binder.
  7. Synchronize the binder.
If the above process does not get the binder Finalized and synchronized to the Central File Room as expected, please call into support or start a new case online for further assistance.

Additional Information


  Solution Tools
 Solution Id 000241648/Partial-Failure-and-Cannot-create-temporary-file-error-when-attempting-to-sync-after-a-failed-finalization-in-CCH-ProSystem-fx-Engagement-or-CCH-ProSystem-fx-Workpaper-Manager-Version-2020-1-3-and-2020-2-1
 Direct Link
To provide feedback on this solution, please login.

Your feedback about this article will help us make it better. Thank you!