Active Directory (AD) Connector

[OlegK]

I have a problem with my AD Synchronization.
I have a positive result only performing manual update on the server. Even I
log on using my domail account or log off, this automatic process fails.

Log:
--------------
Component: AD Connector
File: AutoADProcess
Line: -1
Description: <Description><![CDATA[AD PWA sync for : projman - AD Group
Error - cause likely to be group does not exist]]></Description>

Component: AD Connector
File: AutoADProcess
Line: -1
Description: <Description><![CDATA[Accessing AD group projman failed due to
error 13-FetchGroup: Type mismatch]]></Description>

 

[ThomasF]

Hi, I am having the same problems. I have recently did a test setup using only Windows 2003 servers via Virtual PC. Everything worked as expected with one 2003 DC, and a Project Server. The AD synced correctly to Project 2003 Server with Groups, Organisational Unit (not documented feature); However, on our current production environment, I have installed Project 2003 on a Win2K3 box which is a member of the domain, with WSS and project server. When I attempt to do a AD Sync under Manager Users and Groups >> Groups, I get lots of errors in the event viewer, mainly the same as the one in the previous post (group not found etc). I have matched the names with the system and made sure that everyone exists with Name and email address. The only thing I can thing of is that our WIn2k domain runs in PRE-2000 mode for some win95 clients. Would this have an effect?

 

[ThomasF]

Hi Everyone,

A followup to my previous post, I have experimented with the different modes and it seems the errors occur when you have a Win2K3 server in application mode (i.e. NOT a domain controller) and the rest of your DC are Win2k. The problem appears to be a different schema that Project 2003 doesn't regonise, hence it keeps returning with a type-mismatch in the eventlog. When I did the experiment with the Virtual PCs, I had to update the schema on the Win2k server and once I did that, everything worked straight away - (you need to update the schema on the WIN2k schema master by running adprep from the WIN2K3 CD). Search on adprep and see whether that is suitable for your envirnoment

Hope this helps anyone who is out there pulling their hair out wondering why it wouldn't work... I know I spend 2 days doing that

 

[Chris Covey]

Is this the only solution?
ADPREP on the Win2000 DC?..............cc

Hi Everyone,

A followup to my previous post, I have experimented with the

different modes and it seems the errors occur when you have a Win2K3
server in application mode (i.e. NOT a domain controller) and the rest
of your DC are Win2k. The problem appears to be a different schema
that Project 2003 doesn't regonise, hence it keeps returning with a
type-mismatch in the eventlog. When I did the experiment with the
Virtual PCs, I had to update the schema on the Win2k server and once I
did that, everything worked straight away - (you need to update the
schema on the WIN2k schema master by running adprep from the WIN2K3
CD). Search on adprep and see whether that is suitable for your
envirnoment.