Installing PR2.21.0 FAILS

SUGGESTED

Has anyone seen this error.

PR2.21.0 install ends with Finalize Failed with the following error

      OK    

***Then -  An error occurred converting pii data. administrator must log in to convert data

That fails with Error 12 SY_PII.dvc Line 326 indicating the PR_EmployeePDFEDeliverylog file is missing or duplicate.

This is a brand new 2020.1 install with only ABC data.  No client data migration has occurred yet.

KB  68822 addresses the error but resolution 3 does not work because you are no unable to access SAGE.

If you try and access Sage it starts again with *** above

A file must be locked as you can not rename MAS90 folder or delete it so the backup can be restored.No pvx or sage processes are running in task mgr.

Having IT look at it and the KB but noluck so far.   AV was disabled. Permissions are full control.

  • 0
    SUGGESTED

    Microsoft fonts are the reason you cannot rename. Instead of fully instaling the fonts are being shared .  The location of these shares are pretty deep:

    ..Mas90\Home\TINYMCE\JS\TINYMCE\LIGHTGRAY\FONTS\TINYMCE.TTF  and TINYMCE-SMALL.TTF

    As for your instial error I have nto experienced. it.

  • 0

    Had something similar happen. New installation of Sage 100 2020, applied PU 1 and then installed PR 2.21.

    As PR 2.21 installation was being finalized, we received an InstallShield Wizard Error: "Finalize failed with the following error:", with just an OK button. Clicked OK and received: "Error Encountered | File 'PR_EmployeePDFEDeliveryLog' not found."

    Info: "Error 12 SY_PII.pvc Line 326". I reinstalled PR 2.21 and it went through without errors. We could then access 2020 and migrate data. After migration, however, when we tried to login to Sage we received the following:
    "An error occurred converting personally identifiable information. An administrator must login to restart the conversion process."

    That reminded me of the old message about an administer maintaining the system so I looked, and sure enough there was an "InstLock.txt" in the Home folder. Of course first I logged in as the Administrator and attempted to convert company data, no luck there.

    Then we received the pop-up box which seemed to require us to change the PII Encryption Key.

    Eventually we were able to bypass all the errors and get back to converting data.