Sage doesn't support the use of Sage 50 through RemoteApp, so we have no experience in attempting to get it to work effectively. Hopefully a network ninja or a certified consultant can chime in if they know of a workaround. However, that being said, I can tell you that the PawEncrypt error is almost always caused by one of two things: 1. Corrupt Windows profile 2. Insufficient local rights when using a profile for remote access. Here's a procedure we consider a "use at your own risk" workaround. It may work, it may not. If done wrong, it could mess up the registry, so be sure to do a full registry backup before attempting it. Press Windows+R keys. Enter regedit, and then click OK. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Inside this key you will see a number of subkeys, these correspond to different windows users. Locate the user you are logged in as by looking at the string value "ProfileImagePath" of each of these sub keys. One of these values will correspond to the users home directory which in most cases will have the user name in it. Once you have located the profile that is getting the error check the value of the "State" DWORD Value. If it is not set to 0100 (hex value) this could be the cause of the PAWEncrypt AcquireOurContainer Error. A hex value of 0100 indicates Administrator level use of the local profile. Other values may cause windows to have insufficient access than what is needed to the local profile to run Sage Peachtree. Editing this value may have unknown consequences, before editing make a note of the existing value. Verify you can now open Sage 50.
↧