Skip to content

Server error 500 after upgrade to AMS 2.0 from 1.0 #230

Closed Answered by ryannewington
Slinters asked this question in Q&A
Discussion options

You must be logged in to vote

@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.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Slinters
Comment options

Answer selected by Slinters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants