"An update has not yet been sent to resources ..."

[Ray]

I imported a project into Project Server 2003 SP2, mapped most of the local
resources to enterprise resources and left the remaining local resources
without a windows account and a workgroup of "none". The project shows up in
PWA but none of the resources have any tasks. When I try to republish the
tasks, I always get a dialog box saying:

"An update has not yet been sent to resources who have been removed from
task assignments. An update with this information will be sent now."

But nothing happens. I found an article where someone said they exported the
project and reimported it but it wasn't as easy as it sounds. I can't figure
out how to do even this and was wondering what its implications are.

Any guesses would be appreciated.

Thanks,

Ray

 

[Dale Howard [MVP]]

Ray --

You must republish the assignments using Collaborate - Publish - Republish
Assignments. Are you certain you used that, or did you click New and
Changed Assignments instead? Let us know.

 

[Ray]

Hi Dale,

Yes, that's what I did and that's when that dialog box popped up. I tried
the binary rebuild procedure from your FAQ to no avail. I did find the
procedure to export to XML and it's been running for a couple of hours now.
The .mpp file is only 16 MB, so I'm not sure why it's taking so long but
I'll find out tomorrow morning. how it did.

We had taken the remaining tasks from the local resources and moved them to
the enterprise resources and it looks like that's about the time it started.

The locals are set to Workgroup:none and I tried adding SMTP addresses to
them, but that didn't help. If I'm reading the docs right, the Workgroup
selection in the resource definition should be what controls whether Project
Server sends an email notification, so maybe I'll try setting all of the
enterprise resources to "none" tomorrow if the XML import doesn't do the
trick.

Take care,

Ray

 

[Me]

Hi Dale,

Well, here are the results.

I let it try to export to an XML file and it jumped to three blocks fairly
rapidly. Unfortunately it stayed there for the next eighteen hours and ran
the memory utilization to 1.4 GB on my desktop, far more than the amount of
physical memory installed. CPU utilization was normal. I killed the process.

I then tried exporting to a .MPD format and that went fairly quckly. The
good news is the import went well & the bad news is the problem with
publishing was still there.

I then changed all of the enterprise resources to a workgroup of "none" but
that didn't help.

So then I tried deleting each resource one at a time and after they all were
gone, the error still occurred.

Remembering that I had read about a program named Project Kickstart and that
it would read .mpp files, I downloaded a trial copy and ran it. I let it
read the 16 MB .mpp file and simply clicked through it without changing
anything. It saved to a .mpp file that was less than 5 MB in size. I
imported it and Shazaam! The error was gone!

I am getting just one error from the spooler about the manager not being
able to create a resource account, but other than that it looks pretty good
so far. I don't know which account it thinks it can't create because they
were all there and the error message doesn't say. I'm an admin on the
Project Server, so I shouldn't be getting the error anyway.

Well, now I get to go to work on Monday and begin working on this issue
officially.

Take care and thanks for the input,

Ray

 

[Dale Howard [MVP]]

Ray --

The "Manager cannot create account..." error has nothing to do with your
permissions level in Project Server. It always indicates that you are
trying to publish assignments for a local resource. Check your Resource
Sheet view in the project and this should reveal the source of the problem.
Glad you solved it, by the way. It sure sounds like you had a badly
corrupted project.

 

[Gaurav Wason]

Just try to publish one task and see if you get the same error.

--
Gaurav Wason
(e-mail address removed)
MCP - Project Server