AD sync issue

[Arman]

I am having problems with AD sync. I have a Project Server group in AD and I
added a user to the group in AD. When I run the group sync the user isn't
added to PS. My AD synch worked with no problem, the only thing different
about this case is that the user has been manually added to Enterprise
Resource Pool by one of our Resource Managers before she was added to Project
Server group in AD. What complicates the issue even more is the fact that AD
sync doesn't give me any errors, even when I check the queue, the job status
is success.

Any help will be greatly appreciated!

 

[NZ Projects]

Arman,

I don't understand what's making you think that AD sync is not working. You
say the users isn't added via AD sync, but then go on to say the user has
been added manually.

Can you please explain you issue in more detail?

Generally AD sync issues are related to user objects which are checked out.

 

[Arman]

A resource has been added manully not a user. So if she were to try and
login, it would fail. Usuall with AD group sync, the user gets added and then
the Resource Pool sync adds the user to enterprise resource pool.

Hope this clears the confusion.

 

[NZ Projects]

Raise the logging level of the AD Sync ULS log to verbose and re-run AD sync.
Is there any additional detail in the log ?

 

[Arman]

NZ,

Thanks a lot for trying to help me. Nothing really stood out. The verbose
messages were mostly:

Entering UpdateResource.
Not updating resource
Leaving UpdateResource.


Then I get to checked out resources:

Entering CheckoutResources number to checkout: 20.
Attempting to checkout 20 resources.
Leaving CheckoutResources number checked out: 0.

And then I get couple of exceptions, I'll try to summarize them, couldn't
find a way to attach a file:

A general exception occurred during communication with Active Directory.
Context: SyncGroup. Additional Information: An exception occurred while
syncing a project server group with active directory

ULS Event: AdSyncExceptionOccurred, tag tag_95vo was associated with
exception: System.NullReferenceException: Object reference not set to an
instance of an object. at
Microsoft.Office.Project.Server.BusinessLayer.AdSync.UpdateResourcesToDatabaseWork(SyncTypeEnum
syncType, ActiveDirectoryUserCollection members, List`1
resourcesToCheckoutForUpdate, List`1 ResUids, DataRowState operation,
ADSyncStatus& status) at
Microsoft.Office.Project.Server.BusinessLayer.AdSync.UpdateResourcesToDatabase(SyncTypeEnum
syncType, ActiveDirectoryUserCollection members, List`1
resourcesToCheckoutForUpdate, List`1 resourcesToDeactivate, List`1 resUids,
ADSyncStatus& status

Unexpected ...Sync.SyncAdGroup(SyncTypeEnum syncType, String adGroupName,
ActiveDirectoryUserCollection members, List`1 resUids, Boolean
reactivateInactiveUsers, Type resType, Boolean groupNotSet, String
eventPrefix, ADSyncStatus& status

Resource 'cb628dfe-1e8e-410b-b577-17c750c632a9' already exists in group
'69fc9d0d-0b5f-4f4a-a9ef-c05a60eb5236'.

The unique ID didn't match though.

Any thoughts?

 

[Jonathan Sofer]

Is this AD Synch in MSPS 2007? Was this resource created with the option
"Resource can logon to Project Server" turned off?

 

[Arman]

This is 2007, unfortunately, since I'm not the one who created the resource,
I'm not even sure if they've unchecked the option.

 

[Jonathan Sofer]

Go to the resource center and select the resource for editing and you can
see whether that option is enabled or not.

 

[Arman]

Jonathan,

Thank you very much, that did it. I checked the box and selected Windows
authentication and it works now.

Thanks again for your help!

 

[Jonathan Sofer]

You are welcome.

Jonathan,

Thank you very much, that did it. I checked the box and selected Windows
authentication and it works now.

Thanks again for your help!