Recapping a bit, when running MLS as a different Windows user, MLS would pop-up the error message shown in the first post of this thread. If that same User right-clicked on MLS and ran MLS as an admin, MLS would run without a hitch. However, when you went back to run MLS as "Unit xxxxx" (former "Clerk" account), it would hang indefinitely while starting until you killed the process. As far as I can tell, this error ONLY occurs after setting up new PC's with the LDS Provisioning tool that comes pre-installed.
I traced it down to a file that had one permission missing compared to other files in that folder. That file was:
C:\ProgramData\LDS Church\MLS\data\strings\str_tab0.data
Adding the missing permission back allowed MLS to run as Unit xxxxx again.
The bigger problem I see is it appears the LDS Provisioning tool is setting the permissions in the ProgramData folder differently than has been used before and this is affecting the ability to run MLS as a different Windows user. The following shows the old way of setting permissions for a typical file under ProgramData\LDS Church\:
Code: Select all
Type Principal Access Inherited From
---- --------- ------ --------------
Allow Users Full Control C:\ProgramData\Lds Church\MLS\
Allow SYSTEM Full Control C:\ProgramData\
Allow Administrators Full Control C:\ProgramData\
Allow Clerk Full Control C:\ProgramData\
Code: Select all
Type Principal Access Inherited From
---- --------- ------ --------------
Allow SYSTEM Full Control C:\ProgramData\
Allow Administrators Full Control C:\ProgramData\
Allow Clerk Full Control C:\ProgramData\
Allow Users Read & Execute C:\ProgramData\Lds Church\MLS\
Allow Users Write C:\ProgramData\Lds Church\MLS\
PLEASE don't attempt this if you are unfamiliar with file and folder permissions. You could easily prevent MLS from running at all.