T
Tonco
Hi all,
I've searched many forums for an answer to the following problem, but only
came across a number of users with the same problem, however didn't find any
resolutions yet. Maybe anyone here can point me in the proper direction.
Situation:
I've got a Windows 2003 Server with Project Server 2003 installed. I've got
a Windows 2000 Server SP4 which runs Active Directory. In Active Directory, a
security group has been set up, called EPM Resources, which contains all the
users that should be usable as resources in projects.
I've configured Project Server 2003 to synchronize the resource pool with
the EPM Resources security group in AD.
The synchronization is partially succesful, however for a number of users I
get per user an event log entry, which is as follows:
---
Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 5/20/2005
Time: 3:01:34 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: ServerX
Description:
Component: AD Connector
File: AutoADProcess
Line: -1
Description: <Description><![CDATA[AD Res Pool Sync - PDS ADD Res failed:
William of Orange]]></Description>
---
The user name in the description is not the 'real' one of course, but of
exactly in the same format. There are no special signs (like square brackets
or anything), just plain characters.
I have applied the Project Server 2003 Service Pack 1, which did not provide
the solution.
Maybe it is useful to note the following, however it might be sheer
coincidence...
The users that have been synchronized succesfully, were all added as users
to Active Directory, after the date that Service Pack 4 was applied to the
windows 2000 server that is running Active Directory. The users that failed
to synchronize with the Resource Pool were thus addes before the application
of SP4 to Windows 2000. I don't know if there's some AD attribute that might
cause the failing of synchronization, or if this has anything to do with the
problem, but we just noticed it...
I hope anyone can point me in the proper direction to a solution.
Thanks in advance for any input, it is greatly appreciated.
Best regards,
Tonco
I've searched many forums for an answer to the following problem, but only
came across a number of users with the same problem, however didn't find any
resolutions yet. Maybe anyone here can point me in the proper direction.
Situation:
I've got a Windows 2003 Server with Project Server 2003 installed. I've got
a Windows 2000 Server SP4 which runs Active Directory. In Active Directory, a
security group has been set up, called EPM Resources, which contains all the
users that should be usable as resources in projects.
I've configured Project Server 2003 to synchronize the resource pool with
the EPM Resources security group in AD.
The synchronization is partially succesful, however for a number of users I
get per user an event log entry, which is as follows:
---
Event Type: Warning
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 1
Date: 5/20/2005
Time: 3:01:34 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: ServerX
Description:
Component: AD Connector
File: AutoADProcess
Line: -1
Description: <Description><![CDATA[AD Res Pool Sync - PDS ADD Res failed:
William of Orange]]></Description>
---
The user name in the description is not the 'real' one of course, but of
exactly in the same format. There are no special signs (like square brackets
or anything), just plain characters.
I have applied the Project Server 2003 Service Pack 1, which did not provide
the solution.
Maybe it is useful to note the following, however it might be sheer
coincidence...
The users that have been synchronized succesfully, were all added as users
to Active Directory, after the date that Service Pack 4 was applied to the
windows 2000 server that is running Active Directory. The users that failed
to synchronize with the Resource Pool were thus addes before the application
of SP4 to Windows 2000. I don't know if there's some AD attribute that might
cause the failing of synchronization, or if this has anything to do with the
problem, but we just noticed it...
I hope anyone can point me in the proper direction to a solution.
Thanks in advance for any input, it is greatly appreciated.
Best regards,
Tonco