Error 0x8C04000D User Account Conflics with Existing Account on Se

[Christie @ CGI-AMS]

Any help for the following issue would be greatly appreciated. One of our
task plans generates a Server Spooler error on any of the publishing
activities that says "The windows user account or user name for the affected
user account conflicts with an existing account on the server (0x8C04000D)."
The impacted resources are all ones that we recently marked Inactive (we do
not remove resources from the Resource Pool). The windows account for each
impacted resource is still included in the Resource Pool, but it is missing
from the Resource instance inside the one impacted task plan. Is there a way
to re-associated the resource in the task plan with the instance in the
Resource Pool? If not, is there another way to correct this error? Our DBA
is relatively inexperienced, so any specific instructions would be extremely
helpful. Thanks so much!!

 

[Kevin W Flanagan]

What is the reason for not wanting to delete a resource?

 

[Christie @ CGI-AMS]

If we delete the resource from the Resource Pool, we lose all the historical
information on the actuals the resource has charged against different
assignments. We use this historical data to refine our estimating process
and for planning for future efforts that may be similar to historical ones
captured in Project Server.

 

[Kevin W Flanagan]

In the Resource Pool, make sure the column "Windows Account" is showing and
make sure there is no information in that field for your inactive resources.
You can also insert the "Inactive" column to make sure they are inactive. My
suspicions are that the windows account is still present but has been removed
from the Active Directory.

 

[ProjectAnalyst]

I'm having similar problems and would love to hear some more ideas.

I have inactive users that retain their Windows Account data, even though
the underlying resource pool does not contain a value in the Windows Account
column. I synchronize my accounts with active directory, which clears the
Windows Account column when users are removed from the network.

This is causing multiple 0x8c04000d and 0x8c040012 errors when publishing is
attempted.

Help!

 

[Ger]

Here's what we do to workaround the problem:

1) Using Admin/Manage Users/Modify User we reactivate the resource. There
is no Windows account.
2) Open, save and close the project where the resource has assignments -
this resynchs the resource information between the project file and the pool
4) Deactivate the resource, this time using Project Pro to access the
resource record in the pool.

Do you have SP2 installed?