Can't access MLS from another Windows account
Posted: Sat Sep 03, 2016 1:18 am
As the STS, I have all the PC's in our stake setup with a StakeAdmin Windows local account with administrator privilege so I can help if the regular Clerk account goes haywire. I also have a StakeAdmin (out of unit) username in MLS with admin rights on each clerk PC. This has served me well for years.
I recently received 8 new Lenovo ThinkCentre M700's for our stake and set them up by first letting the LDSProvisioning software run and answering the questions for each unit's PC. When the provisioning ended, I ran MLS using the unit's newly created Windows login and created a StakeAdmin MLS user to make sure it installed OK. (I was careful not to do a Send/Receive at this point, but thinking back, it would have failed anyway due to security reasons.) I then added a StakeAdmin Windows account with administrator privilege and attempted to run MLS from it. About 3 seconds after launching MLS, I got the popup window shown below. As you can see, there is only one option and that's to exit MLS. All 8 PC's performed the same way.
On one of the new PC's, I logged into Windows as StakeAdmin and tried right-clicking on the MLS icon and set it to Windows 7 compatibility, no change. I then took that off and set it to run as an administrator. It ran MLS this time, however, when I logged back into the Unit's account, it had a problem accessing MLS. (Sorry, I can't recall the exact error.) While still logged into the unit's Windows account, I right-clicked the MLS icon and ran it as an administrator. Thankfully, this cleared the problem and I could run MLS once again without needing to elevate to admin.
The Dell Optiplex PC's that were getting replaced were mostly Windows 10, with 2 still on Windows 7. Some were using MLS 3.8.4, while others were on 3.8.5. On every one of these older PC's I could log into Windows as StakeAdmin and open MLS using the StakeAdmin username with zero problems. After transferring all the data from the old to the new PC's, I was hopeful something would change for the better, but no dice.
Anyone ever see this error message before? I sure don't want to have to remember every unit's password. I can't see how it could be intentionally designed to run this way as this would seriously impact those who need to have multiple units share the same PC.
I recently received 8 new Lenovo ThinkCentre M700's for our stake and set them up by first letting the LDSProvisioning software run and answering the questions for each unit's PC. When the provisioning ended, I ran MLS using the unit's newly created Windows login and created a StakeAdmin MLS user to make sure it installed OK. (I was careful not to do a Send/Receive at this point, but thinking back, it would have failed anyway due to security reasons.) I then added a StakeAdmin Windows account with administrator privilege and attempted to run MLS from it. About 3 seconds after launching MLS, I got the popup window shown below. As you can see, there is only one option and that's to exit MLS. All 8 PC's performed the same way.
On one of the new PC's, I logged into Windows as StakeAdmin and tried right-clicking on the MLS icon and set it to Windows 7 compatibility, no change. I then took that off and set it to run as an administrator. It ran MLS this time, however, when I logged back into the Unit's account, it had a problem accessing MLS. (Sorry, I can't recall the exact error.) While still logged into the unit's Windows account, I right-clicked the MLS icon and ran it as an administrator. Thankfully, this cleared the problem and I could run MLS once again without needing to elevate to admin.
The Dell Optiplex PC's that were getting replaced were mostly Windows 10, with 2 still on Windows 7. Some were using MLS 3.8.4, while others were on 3.8.5. On every one of these older PC's I could log into Windows as StakeAdmin and open MLS using the StakeAdmin username with zero problems. After transferring all the data from the old to the new PC's, I was hopeful something would change for the better, but no dice.
Anyone ever see this error message before? I sure don't want to have to remember every unit's password. I can't see how it could be intentionally designed to run this way as this would seriously impact those who need to have multiple units share the same PC.