Strange spooler error scenario - long

S

SBelling

Greetings:

Wondering if anyone could help me figure out why the
following scenario/series of events caused a particular
spooler error:

I was working with one of my peers yesterday. We have set
up for each of our managers in our IS Dept something we're
calling a Tactical Project. The idea is that the managers'
direct reports will use the Add Task function when they
are assigned a tactical (less than 40 hrs) project,
they'll add one task to the Tactical Project schedule and
log their time on that task.

The manager and I were testing this yesterday - he added
the task, clicked the update button to send it. Then,
since he was sending it to himself, he went to his Updates
page and accepted the added task.

First sign of trouble - we got a message referring to the
task using a local resource of the same name, did we want
to replace with the corresponding enterprise resource - we
said yes. Things seemed to work ok.

Later, we deleted the task from the associated project
plan and chose publish - publish new and changed
assignments (he wanted to see if deleting the task and
then republishing it would take it off of this manager's
timesheet view - I knew it wouldn't but figured I'd let
him see it himself). Next sign of trouble - Project Pro
told us there was nothing to publish, gave us three
reasons why this might be. As I recall one of them
referred to a resource issue.

We made some other changes to the file and were able to
publish it - then got this spooler error:

0x8C04000D - Windows account or user name conflicts with
existing account on server.

Now, this doesn't make any sense to me, because all the
user accounts and resources in our pool are sync'd from
the same AD group. THis manager created the task from his
PWA page, which auto-authenticates to his windows AD data.
Same story when logged in to PRoject Pro.

One thing - I did notice this morning that yesterday's
daily AD sync failed. I rescheduled it to occur this
morning so I could see if it failed again. But we aren't
experiencing any problems with any other users at this
time.

So - anyone have any ideas as to what could have caused
this to occur?

Thanks!
S Belling
 
G

Gary L. Chefetz \(MVP\)

The best way to avoid this type of update error is to close Project before
you apply updates. Allow Web Access to open Project as part of the update
process an you're less likely to have these problems which seems to occur
because you've got two separate sessions open with the server.

--

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

-
 
S

SBelling

Thanks for the insight - I will pass that along to our
users.

Do you have any thoughts on the part where the user
created a task for themselves, sent it out, then accepted
it and we got the message regarding local resource same as
enterprise resource?

This really threw me, since the resource pool and user
authentication is from the same AD group.

SBelling
 
Top