M
Milrod
Hello everyone,
If you got as frustrated as I did installing and configuring Project
2003, hopefully some of this will be usefull.
First off, as of July 11th 04, I would immediately apply patches from
KB articles: (need to call MS)
KB-838881 Project Server 2003
KB-840314 Project Pro
Before I applied 838881, I couldn't get project pro to authenticate to
project server in any way, shape, or form. once I applied this patch,
I immediately authenticated (based on the administrator user, or
whatever users you created in web admin).
The easiset way to add the NT users into the Enterprise Resource pool
as project calls it, is to log onto project pro as the project server
administrator and "check out" the global enterprise resource pool.
You can add the NT users here either from active directory, or your
exchange address book and your NT accounts will be nsync with Project.
Now if you go back into the web admin program for project, you should
see whatever NT users you added from project pro. If you're like me,
you will still probably see some kind of syncing error in event viewer
if you try and manually run a sync, or schedule it to run at a certain
time, however your nt accounts will be added into the resource pool
anyway since you added them in from project pro.
I'm still having AD sync errors, and was getting the 0x4e20 error with
autoadprocess and AD connector also coming up in the event viewer
message. I tried everything including starting services with
administrator privledges.
IMO, this was one of the poorest quality of software installations
I've ever had the misfortune of having to be a part of. One being
that out of the box, Project Pro could not authenticate with the
server, and also the sync'ing issues.
If you got as frustrated as I did installing and configuring Project
2003, hopefully some of this will be usefull.
First off, as of July 11th 04, I would immediately apply patches from
KB articles: (need to call MS)
KB-838881 Project Server 2003
KB-840314 Project Pro
Before I applied 838881, I couldn't get project pro to authenticate to
project server in any way, shape, or form. once I applied this patch,
I immediately authenticated (based on the administrator user, or
whatever users you created in web admin).
The easiset way to add the NT users into the Enterprise Resource pool
as project calls it, is to log onto project pro as the project server
administrator and "check out" the global enterprise resource pool.
You can add the NT users here either from active directory, or your
exchange address book and your NT accounts will be nsync with Project.
Now if you go back into the web admin program for project, you should
see whatever NT users you added from project pro. If you're like me,
you will still probably see some kind of syncing error in event viewer
if you try and manually run a sync, or schedule it to run at a certain
time, however your nt accounts will be added into the resource pool
anyway since you added them in from project pro.
I'm still having AD sync errors, and was getting the 0x4e20 error with
autoadprocess and AD connector also coming up in the event viewer
message. I tried everything including starting services with
administrator privledges.
IMO, this was one of the poorest quality of software installations
I've ever had the misfortune of having to be a part of. One being
that out of the box, Project Pro could not authenticate with the
server, and also the sync'ing issues.