-
Title
Error: "Desktop Authority was unable to create and/or write the necessary registry keys for proper operation" -
Description
When roaming profiles are in use, Desktop Authority may fail with the following errors:
"Desktop Authority was unable to create and/or write the necessary registry keys for proper operation."Or
Error: "ScriptLogic was unable to create and/or write to the necessary registry keys for proper operation."
-
Cause
Among the many pitfalls often associated with roaming profiles, a simple mistake made during the creation of a user’s roaming profile can lead to errors and other problems. A typical mistake is neglecting to assign the appropriate permissions to the roaming profile when it is created. This mistake becomes most apparent when dealing with Windows XP since portions of the user’s registry (the NTUSER.DAT) are secured using these permissions. If the user is not granted the appropriate permissions then software applications that normally make changes to the registry may fail. Another cause for this type of error is the improper relocation of locally stored profiles on a Terminal Server. If existing profiles are relocated improperly, then again the ability to make changes to the registry may fail due to incorrect registry permissions. This change will only adversely affect existing users and will not affect any new users. -
Resolution
To diagnose and confirm this issue, simply un-assign the roaming profile from the user and delete the locally cached copy of the profile. Once a user logs back on, they should find that ScriptLogic executes without the above error. To correct this problem follow the steps outlined in the Microsoft Knowledge base article listed below that correspond to your situation.
1. Recreate the roaming profile and ensure that you assign to the user the appropriate permissions to access the profile. For additional help, refer to Microsoft Knowledge Base article Q302082 How to Create a Roaming User Profile.
2. Correct any registry changes made to the Terminal Server when moving the location of locally cached profiles. For additional help, refer to Microsoft Knowledge Base article Q214470 How to Move the Location of a Locally Cached Profile