4,757
I am in the testing phase of a 2015 upgrade for a customer using SL Access rather than AD access.
After the update scenario is run, none of the existing users can login. I get one of those CLR20r3 errors. When I delete all the passwords, all logins work.
Has anyone else seen this. I'd like to avoid deploying with no passwords if possible.
Hi
I am getting the same error as sysadmin even if I clear the passwords
Problem Event Name: CLR20r3
Problem Signature 01: MSDynamicsSL.exe
Problem Signature 02: 9.2.41201.2
Problem Signature 03: 58406931
Problem Signature 04: mscorlib
Problem Signature 05: 4.6.1087.0
Problem Signature 06: 583e5abb
Problem Signature 07: bd8
Problem Signature 08: b9
Problem Signature 09: System.FormatException
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: def2
Additional Information 2: def211d420ff7de438f6f9d3594f8fca
Additional Information 3: 142f
Additional Information 4: 142f6a232a30e08c90d55f90ee15c57a
Thanks for verifying this Elaine!
I talked with our env team.
They are finding that you pretty much always have to reset the passwords. This appears to possibly occur because a different encryption is used in the different versions.
We wrote bug 34667 for this issue. It looks to be corrected in the next release. Notes says this.
When a SL 7x database set for SQL authentication with existing user passwords is upgraded to SL2015, the users cannot get into SL. In the Login screen they can enter their SL User ID do a PV and select a company and then enter a password. Click OK and get: Microsoft Dynamics SL has stopped working.
The workaround we have is this.
Clear the existing user passwords:
Run this against the SL system database:
Update userrec set password=''
The users can then log in with blank password and go to the Tools menu and set their passwords
or the Sysadmin can go into User Maintenance and set the user passwords.
Well thanks for your comments, the only thing that works is to delete the passwords and reset them using the Set Password screen or the User Maint screen.
Go into the Database Maintenance utility and check the Authentication type. And you may also want to run the Synchronize All Ownership & Security.
Well, the system is using the same old SL Authentication. It's just that the passwords don't seem to survive the upgrade. I even had to reset the SYSADMIN pw to get into it.
I believe you are using Window Authentication mode now, so you are not deploying without passwords. If the domain account is disabled, their access to SL should be terminated as well.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
290,552
Super User 2024 Season 2
#2
Martin Dráb
228,552
Most Valuable Professional
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (