there may be multiple issues here. The first one around the user's details not coming through is not necessarily a problem, rather a choice. If you want infromation about the user to be synced you need to set synchronization.syncWhenMissingPeopleLogIn = true which will trigger a differential sync when a user has been authenticated successfully but does not exist in Alfresco's user repository e.g. someone has just had a new user created in AD and the last time Alfresco synced with AD was this morning.
There is still the possibility that the user won't be available to Alfresco with synchronization.syncWhenMissingPeopleLogIn = true. E.g. if your synchronization configuration is only targeting a select set of users to sync and this user is outside that, of if the user was created before the last time Alfresco synced, but for some reason the user didn't get pulled in (e.g. sync failure, communication issue etc).
In this case, if synchronization.autoCreatePeopleOnLogin = true, then a new user will be auto-created for them in Alfresco with only the base properties (username, display name) and it won't get any group memberships that might exist in AD either. The next time Alfresco does a <em>FULL</em> sync, then this user will be updated to match the record in AD.
The other issues around resolving the view, could be something different, and you'll need to look into share.log to find out the full reason for that exception
Regards
Steven
