Spooler error - resource name conflict with existing account

[SBelling]

Greetings:

Wondering if anyone has a fix for this scenario:

Project Server 2003, Post Service Pack 1 - we saved some
projects as files, deleted them from the Prj Svr database,
the imported them back in. No problems during the import
process. But, when republishing tasks, getting a spooler
error message to the effect that a resource name is
conflicting with an existing account.

We have no duplicate resources - we sync a dedicated
Active Directory group with our enterprise resource pool.

We've had this occur on two projects so far. I'm hoping
someone knows something to do to fix this.

Thanks,
SBelling

 

[Gary L. Chefetz \(MVP\)]

It sounds like you may have the resource listed as a local resource in the
plan.

--

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

-

 

[SBelling]

Nope - definitely not the case. However, this particular
person is the Admin who does all of the install work and
Windows 2003, SQL Server configuration (NOT Prj Svr Admin -
that's me). The only thing I wondered is if for some
reason the system is seeing her once as the server admin
and once as an enterprise resource in the AD group, thus
the conflict.

Thoughts?
SBelling

 

[SBelling]

I retract the above statement - they were indeed in as a
non-etnerprise resource (but not as a local resource). I
know this occurred when I had to save the proejct as a
file, delete it and then re-import it.

ANy idea whay this makes some resources become non-
enterprise? We've seen this behavior on one other project.

-----Original Message-----
Nope - definitely not the case. However, this particular
person is the Admin who does all of the install work and
Windows 2003, SQL Server configuration (NOT Prj Svr Admin -
that's me). The only thing I wondered is if for some
reason the system is seeing her once as the server admin
and once as an enterprise resource in the AD group, thus
the conflict.

Thoughts?
SBelling

 

[Gary L. Chefetz \(MVP\)]

AFAIK, this can only happen in the import process if you fail to map the
resources back to enterprise resources during the import process. Otherwise
the system will create all new accounts for these.

--

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

-

I retract the above statement - they were indeed in as a
non-etnerprise resource (but not as a local resource). I
know this occurred when I had to save the proejct as a
file, delete it and then re-import it.

ANy idea whay this makes some resources become non-
enterprise? We've seen this behavior on one other project.