Server error 500 after upgrade to AMS 2.0 from 1.0 #230
-
I recently upgraded AMS to 2.0 and after that i cant get it to work. I had authentication on Integrated Windows Security and NTLM when running it on v.1.0 and it worked. When using Negotiate i get a blank page and in the log webapp.logg i can see the following:
And when using NTML i see this in the log: And running with value of Basic: Something is missing that cannot be null but what? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The ams service doesn't have permission to read the msds-principalname and a few others, on user objects. This is usually granted because "authenticated users" is by default a member of the "pre-windows 2000 compatible access" group. In some environments this membership is removed and users by default can't read properties of other users. Either add the service account to the pre win2k group, or manually delegate "read" permissions on user objects in the domain to the ams service account. AMSv1 resolved user attributes differently to V2. Hence the issue appearing here. |
Beta Was this translation helpful? Give feedback.
@Slinters
The ams service doesn't have permission to read the msds-principalname and a few others, on user objects.
This is usually granted because "authenticated users" is by default a member of the "pre-windows 2000 compatible access" group. In some environments this membership is removed and users by default can't read properties of other users.
Either add the service account to the pre win2k group, or manually delegate "read" permissions on user objects in the domain to the ams service account.
AMSv1 resolved user attributes differently to V2. Hence the issue appearing here.