Thursday, February 09, 2012 6:50 PM
I have read the solutions to the other issues logged for this specific error and most are talking about a 'deactivated user'. In this case the AD sycnh error is only happening for 1 specific resource and this resource is ACTIVE?
The enterprise resource pool has resources which are in two different AD domains....not sure if that might have something to do with this? All of the other resources are in Domain A in active directory and they are all working okay......this is the first resource from Domain B which we have entered.
Here are the steps we took to 'add' this resource becuase there was manual intervention so maybe we messed up in terms of initial setup?
1. We added the resource to the correct AD group so that the resource would 'synch to PWA'
2. We were having other issues with AD synch and it was failing so the resource wasn't coming over? We then decided to manually add this resource to the Resource pool via PWA so that the project mgrs could access and so that approved non-working time could be entered. (Note: We checked the checkbox to "allow accces to project server" and we succesfully added the user login account as "Domain B\logon account". All other resource logn accounts are "Domain A\logon account" (none of these are having the synch issue?)
3. We have been able to resolve the 'other issues' with AD synch....and now the only issue which is coming up in Windows event log....is the above error specifically for this resource????????
I would also like any other suggestions on other places to look in terms of troubleshooting oustside of the windows event log?
Thank you for your help!
Friday, February 10, 2012 4:48 PM
You can use users from Domain B, make sure that you have two way trust established between domain A and B.
Hrushikesh Deshpande – Senior EPM Infrastructure Consultant, www.DeltaBahn.com
Wednesday, June 27, 2012 1:33 PM
Thank you Hrishi, with the info you provided above along with the answers and suggestions on other AD sync error threads we were able to resolve our AD sync error.
I appreciate your quick responses!