User Account Conflict

[Russ]

Running Project 2003 and I've just encountered an error. For some reason,
when I attempt to publish to the server from the Project client, I get this
message:

the windows user account or user name for the affected user account
conflicts with an exisitng account on the server (0x8C04000D).

Any ideas? Thank you.

 

[Gary L. Chefetz \(MVP\)]

Russ:

This indicates that you have a local representation of an Enterprise
Resource in your project plan. How do you add resources to your project? How
do you add them to tasks?

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[Russ]

Since I am letting Project use Windows authentication, in the Project
Professional client, I create a task and enter in the windows user names in
the resources section, save my project and publish.

 

[Gary L. Chefetz \(MVP\)]

Russ:

Your entry procedure will ultimately yield this result. The correct way to
do this is to use Build Team to add resources to your projects and either
use the split-screen view or the Assign Resources dialog to assign your
resources to tasks.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[dwolf]

Gary,

Having now discovered by your statement that this may be the cause of
our headaches. (Thank You, you have no idea how much this will help if
this works). It would have been so nice to have had some clue of this
6 months or more ago. No help for that now...

Do you have any idea how to correct all of the files back that were
staffed by the incorrect method back into alignment that have been
entered the other way?

I have over 300 projects that will need to be corrected - I have no way
of knowing which were entered by which method. Any ideas would be
greatfully appreciated.

Thanks,

--DWolf

 

[dwolf]

Gary,

Thank you for this tip. This may be the clue we have been pounding our
heads against the wall looking for. Now the next tough question.
Having already committed this process error you describe, how do we
correct it?

Hopefully there is a way of tracking these errant project assignments
down. I have a system with approximately 325 projects to sort through.

Any suggestions at this point would be most greatfully apprectiated.

--DWolf

 

[Gary L. Chefetz \(MVP\)]

Your question is bigger than the news group.<g> My suggestion is to get
properly trained on using the tool. At this point, implement the corrected
behaviors and clean up the plans as required. Consider having a Project
Server Doctor examine your system if you can't isolate the problem projects
and cure them.

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[dwolf]

Gary,

Thanks for the response. Finding adequate Admin level training has
been difficult, so I have had to make do with your books and teach
myself. I have created an Access query to locate resources in the
Resource table using a join against the Text table that are either
missing an email listing or a windows account associated with a project
file not the resglobal (Proj ID =1). This does seem to provide a
definite listing of the files that contain our problem children
assignments, but not necessarily all of them. Each time we have
removed the offending resource completely from the file and added them
back through the Build Team method, adjusted each assignment for Work
and Actual Work as necessary and republished. This method does seem to
solve that one individual problem child.

When we last went through and tracked them down, we got down to a
listing of two and then 5 more popped up. Now we are back up to 40.
It is like the game of smacking prairie dogs.

Would you know a Server Doctor in the Chicago area that you would
recommend or should I just go through the MPUG?

Unless you would be willing of course to make a house call, herr doctor
<g>?

Thanks again,

DWolf

 

[otabari]

Hi,
I have the following scenario:
a group of managers who want to work on their project without the other
managers ability to see them, they all have the same privileges, but i
thought maybe a special group can be set up for them and when they are
added to it their projects become private and cant be seen by others.
can that be done? if so, how?
thanks in advance.

 

[otabari]

Hi,
I have the following scenario:
a group of managers who want to work on their project without the other
managers ability to see them, they all have the same privileges, but i
thought maybe a special group can be set up for them and when they are
added to it their projects become private and cant be seen by others.
can that be done? if so, how?
thanks in advance.

I forgot to mention, we are using project server 2003 with sharepoint
services running on a windows 2003 server.

 

[Dale Howard [MVP]]

otabari --

The default security permissions in Project Server 2003 permit each project
manager to see only his/her own projects and not to see the projects of any
other project manager. Have you changed the persmission somehow to permit
everyone to see everyone else's projects? If so, what did you change? What
Categories and what Groups? Let us know.

 

[otabari]

otabari --

The default security permissions in Project Server 2003 permit each project
manager to see only his/her own projects and not to see the projects of any
other project manager. Have you changed the persmission somehow to permit
everyone to see everyone else's projects? If so, what did you change? What
Categories and what Groups? Let us know.

well all the managers are in these groups:
Project Managers
and are in these Categories:
My Projects, My Resources, My Tasks

they can see all the projects in the PWA and also they can open them
when running project professional 2003
if you need further information please ask, i dont know what else to
supply, i hope this will be enough.
kindest regards.

 

[otabari]

otabari --

The default security permissions in Project Server 2003 permit each project
manager to see only his/her own projects and not to see the projects of any
other project manager. Have you changed the persmission somehow to permit
everyone to see everyone else's projects? If so, what did you change? What
Categories and what Groups? Let us know.

well all the managers are in these groups:
Project Managers
and are in these Categories:
My Projects, My Resources, My Tasks

they can see all the projects in the PWA and also they can open them
when running project professional 2003
if you need further information please ask, i dont know what else to
supply, i hope this will be enough.
kindest regards.

 

[Dale Howard [MVP]]

otabari --

Are the project managers assigned as resources in each other's projects? If
so, that automatically grants each project manager permission to see and
open projects in which he/she is assigned tasks.

Are you absolutely certain the Project Server administrator has not changed
the default permissions settings in Categories and Groups? Let us know.