Windows User Account Conflicts With an Existing Account

[Jeremy Jensen]

When a Project Manager in our organization republishes
tasks associated with a certain user he gets the
following spooler error:

The Windows user account or user name for the affected
user account conflicts with an existing account on the
server (0x8C04000D)

I also notice in the Enterprise Resource Pool that the
resource it is referring no longer has a Windows User
Account or other resource fields. I re-enter them, save
the resource, but it won't "stick." The Account
information is not there the next time I open it.

Also, there is no "conflicting" or "duplicating" user
account for the resource.

Any ideas anyone? I cannot figure this one out

 

[Gary L. Chefetz \(MVP\)]

Jeremy:

It sounds like the user exists as a local user in the plan, and not an
enterprise resource; or there's at least one instance of the resource as a
local resource.

--

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

-

 

[Jeremy Jensen]

As far as I can tell, that's not the case, but thanks for
taking a stab at it. Do you have any other ideas?

Jeremy

 

[dwolf]

Gary,

I am still trying to track down this identical problem. I cannot
locate any duplicates either within Project or through SQL queries.

Your comment here suggests a possible solution. How would I go about
locating a local resource instance in the data base? Can you suggest
what tables/fields I would use in the query to compare to locate the
offending project assignments (ie Local vs Enterprise version of the
same resouce)?

This has been driving us buggy for quite a while.

Thanks for any help you can give to a REALLY annoying problem.

DWolf

 

[dwolf]

Gary et al.,

Some additional findings:

We located a file where a resource (Agent Smith?) had replicated 385
times!! The resource had been removed or "cleaned" from the
database using the Admin cleanup routine. The resource had the
distinctive "DELETED xx/xx/xxx" stamp generated by the routine.
Attempts to delete him from the file on the server choked even the most
robust PC, pegging the processor at 100% and requiring us to close out
of Project Pro. We saved the file to a local drive, deleted it from
the server and then proceeded to delete the instances of the resource 2
at a time to keep it from freezing up the PC and then re-published the
file to the server.

Curiously, the resource in question had NO assignments within the file.

Later that day we located, using PWA, an instance of this same resource
without the "DELETED xx/xx/xxx" stamp. We used the merge routine
in PWA to combine them so that the local DELETED version remains. We
have now tracked every assignment instance and verified that they are
consistent with the correct version.

We have also created an MS Access query to look for resources without
email addresses and located 34 files where these problem children
reside. These seem to be consistent with the spooler error incidents
we are seeing. Some of these resources are so new to the company, that
it is difficult to believe that there are duplicates, plus there does
not seem to be a pattern in the list. There are resources that are in
other projects that the spooler error does not occur and the email
field is filled in.

This seems to be a resource-file combination corruption.

Hopefully this will give someone some ideas where to look for a
solution to this mystery. If I had to make a guess I would point to
the Clean up Project Server Database routine.

Any and all assistance gratefully accepted.

DWolf

 

[dwolf]

Here is a query that I came up with using Access... It shows only SOME
of the resources that have missing email addresses and/or windows
accounts.

SELECT dbo_MSP_RESOURCES.PROJ_ID, dbo_MSP_PROJECTS.PROJ_NAME,
dbo_MSP_RESOURCES.RES_EUID, dbo_MSP_RESOURCES.RES_UID,
dbo_MSP_RESOURCES.RES_ID, dbo_MSP_RESOURCES.RES_NAME,
dbo_MSP_TEXT_FIELDS_2.TEXT_VALUE AS [Email Address],
dbo_MSP_TEXT_FIELDS.TEXT_VALUE AS WinAcct, dbo_MSP_RESOURCES.RES_TYPE,
IIf([dbo_MSP_RESOURCES]![RES_RTYPE]=1000,"INACTIVE","ACTIVE") AS
Inactive
FROM ((dbo_MSP_RESOURCES LEFT JOIN dbo_MSP_TEXT_FIELDS AS
dbo_MSP_TEXT_FIELDS_2 ON (dbo_MSP_RESOURCES.PROJ_ID =
dbo_MSP_TEXT_FIELDS_2.PROJ_ID) AND (dbo_MSP_RESOURCES.RES_UID =
dbo_MSP_TEXT_FIELDS_2.TEXT_REF_UID)) LEFT JOIN dbo_MSP_PROJECTS ON
dbo_MSP_RESOURCES.PROJ_ID = dbo_MSP_PROJECTS.PROJ_ID) LEFT JOIN
dbo_MSP_TEXT_FIELDS ON (dbo_MSP_RESOURCES.RES_UID =
dbo_MSP_TEXT_FIELDS.TEXT_REF_UID) AND (dbo_MSP_RESOURCES.PROJ_ID =
dbo_MSP_TEXT_FIELDS.PROJ_ID)
WHERE (((dbo_MSP_TEXT_FIELDS_2.TEXT_FIELD_ID)=205520931) AND
((dbo_MSP_TEXT_FIELDS.TEXT_FIELD_ID)=205521207))
GROUP BY dbo_MSP_RESOURCES.PROJ_ID, dbo_MSP_PROJECTS.PROJ_NAME,
dbo_MSP_RESOURCES.RES_EUID, dbo_MSP_RESOURCES.RES_UID,
dbo_MSP_RESOURCES.RES_ID, dbo_MSP_RESOURCES.RES_NAME,
dbo_MSP_TEXT_FIELDS_2.TEXT_VALUE, dbo_MSP_TEXT_FIELDS.TEXT_VALUE,
dbo_MSP_RESOURCES.RES_TYPE,
IIf([dbo_MSP_RESOURCES]![RES_RTYPE]=1000,"INACTIVE","ACTIVE"),
dbo_MSP_RESOURCES.RES_RTYPE
HAVING (((dbo_MSP_RESOURCES.PROJ_ID)<>1) AND
((dbo_MSP_RESOURCES.RES_EUID) Is Not Null) AND
((dbo_MSP_TEXT_FIELDS_2.TEXT_VALUE) Is Null) AND
((dbo_MSP_RESOURCES.RES_RTYPE)=0 Or
(dbo_MSP_RESOURCES.RES_RTYPE)=1000)) OR (((dbo_MSP_RESOURCES.RES_EUID)
Is Not Null) AND ((dbo_MSP_TEXT_FIELDS.TEXT_VALUE) Is Null))
ORDER BY dbo_MSP_PROJECTS.PROJ_NAME, dbo_MSP_RESOURCES.RES_NAME;

Also, while tracking this down we discovered two incidents where a
deleted resource had been replicated to the extreme. In one case 384
times and the other over 14,000 times. There is no indication as to
what caused this other than both had the indicative tag line "deleted
xx/xx/xxxx" from being clean off the server by the PWA administrative
account. My guess would be a hang-up during deletion. My IT
department wishes to dump the server and reload from scratch with a
clean install of 2003. With over 325 active projects, this is not my
first preference.

The mystery continues... As usual, any assistance would be greatly
appreciated.

--DWolf