2007 PS Project Import - resource nt account already in use error

[wdritt]

Hello, I am trying to import projects from a 2003PS 2003 to PS 2007 and keep
actuals per completed and started tasks.

My approach is to save the files locally as .mpp files then open and resave
in Project Pro 2007 (locally). Then open up Project Pro, connect to the 2007
server and run the project import via tools/enterprise options/import project
to enterprise

When going through the project import wizard I am running into an error for
some of the resources. For 5 of th 25 resources on the project , the wizard
will not "validate" and says "resource nt account already in use"

All resources in my plans already exist as enterprise resources in PS 2007.
Whats odd is that dispite this error message, the import wizard keeps the old
resources as local, yet still adds the new resources to the same tasks. (I
can differentiate between old and new, because the new resources are listed
as last name/first name compared to first name/last name)

Any ideas on what I am doing wrong?

 

[Ben Howard [MVP]]

Hi WDR,

The import will try and match on names, so Ben Howard is not the same as
Howard Ben, even though they might have the same nt account eg ad\ben.howard.
I think the best thing to do is to replace Ben Howard with Howard Ben during
the import, manually. It's alot of work, but that's the way it goes...

BTW, I don't think you need to save the file locally in Project Pro 2007,
you could just try and save it directly to the server - this is my preferred
method.

 

[wdritt]

Ben, thanks for your reply. Per your suggestion, I think this was my method
in "mapping" local to enterprise resources, unless I am misunderstanding
your point.
When going through the import, it prompts you to designate whether the
resource will be a local resource (where you can designate a calendar) or
whether you want to choose a resource from the enterprise to replace the
resource in the plan. After replacing each resource manually with the
enterprise resource, once I try to validate that, a handful of resources show
the error.

Were you referencing this process or another?