Duplicate Name Error with Enterprise Resource

S

Sara - EPM

Hello,

I am running Project Server 2003 without SP1. An enterprise resource was
created in PWA as a team member. Now, when we try to create a Professional
account for this team member, we get an error: "Duplicate name". We are
unable to delete this resource from PWA; the error is that we do not have the
appropriate permissions and to contact the administrator. I am the
administrator. We also do not see the resource in Professional in Build
Team.

It seems the Windows account for this user has been locked somehow by PWA.
We cannot delete in either PWA or Professional. We cannot edit the user in
Professional.

Thanks in advance,

Sara - EPM
 
E

Earl Lewis

Sara,

We have our system set to automatically create accounts in project server whenever a new resource is added. This way we just add the resource via project pro by opening the enterprise resource pool, make sure the windows user account specifies the correct AD account information for the user and the account creation on the PWA side is automagic. I would highly recommend you follow this practice. It will eliminate this problem.

You can't delete the account via PWA>Admin>Manage Users and Groups>Users?

Earl
Hello,

I am running Project Server 2003 without SP1. An enterprise resource was
created in PWA as a team member. Now, when we try to create a Professional
account for this team member, we get an error: "Duplicate name". We are
unable to delete this resource from PWA; the error is that we do not have the
appropriate permissions and to contact the administrator. I am the
administrator. We also do not see the resource in Professional in Build
Team.

It seems the Windows account for this user has been locked somehow by PWA.
We cannot delete in either PWA or Professional. We cannot edit the user in
Professional.

Thanks in advance,

Sara - EPM
 
S

Sara - EPM

Thank you, RSK.

We've actually experienced this issue before and discovered the article you
referenced below. Unfortunately, it did not work for us. Our solution was
to export the existing resource pool and rebuild the environment from
scratch. We had other issues which lead to the rebuild, but the rebuild
solved the duplicate name issue.

When we executed the directions per the article below, we were still unable
to see the duplicate resource; we were unable to add/delete the resource in
both PWA and Professional.

Any other suggestions would be greatly appreciated.
 
S

Sara - EPM

Hi Earl,

Our system is set up the same way as yours...when a resource is created in
Professional, a PWA account is automatically created. We then adjust the PWA
account to add categories and permissions as needed.

Our duplicate name issue was caused when we accidently created a resource in
the reverse order...when we created a PWA account prior to creating the
accounting in Professional. It was an accident on our end and now, we cannot
release that Windows account.

Within PWA, Cleanup Database, we can delete all assignments/task
change/status report for that particular resource; however, when we go to
delete the resource on that same admin tab, we get an error to the effect of
not having enough permission. We are administrators with full rights to
everything.

We can not delete this resource either in PWA or Professional. In
Professional, the resource does not appear in the check out Pool or in Build
Team.

Thanks!

Sara
 
R

RSK

Sara,

Have you tried deleting the resource from the SQL server tables (Method 3)?
In your case, you do not need to look for a duplicate name. Just delete the
account that exists and try creating a new one. I have found this to work for
me in the past. Mind you, this is a direct delete from the underlying tables.
You mention in your message that you have already deleted the resource's
assignment so deleting from the tables should be ok. You can backup your
database for added safety.

I can try to replicate your scenario on my dev environment but am not too
clear on the exact sequence of events.

RSK
 
G

Gary L. Chefetz \(MVP\)

Sara:

When you setup a user as a PWA account first, and then want to make that
user a member of the Resource Pool, the best way to do it is to setup the
user in an otherwise blank project plan and then use the Import Wizard which
will map the two and make them one provided you type in matching information
in the otherwise blank mpp file.

--

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

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-
Sara - EPM said:
Hi Earl,

Our system is set up the same way as yours...when a resource is created in
Professional, a PWA account is automatically created. We then adjust the PWA
account to add categories and permissions as needed.

Our duplicate name issue was caused when we accidently created a resource in
the reverse order...when we created a PWA account prior to creating the
accounting in Professional. It was an accident on our end and now, we cannot
release that Windows account.

Within PWA, Cleanup Database, we can delete all assignments/task
change/status report for that particular resource; however, when we go to
delete the resource on that same admin tab, we get an error to the effect of
not having enough permission. We are administrators with full rights to
everything.

We can not delete this resource either in PWA or Professional. In
Professional, the resource does not appear in the check out Pool or in Build
Team.

Thanks!

Sara
Click to expand...
server whenever a new resource is added. This way we just add the resource
via project pro by opening the enterprise resource pool, make sure the
windows user account specifies the correct AD account information for the
user and the account creation on the PWA side is automagic. I would highly
recommend you follow this practice. It will eliminate this problem.
 
S

Sara - EPM

Hi All,

Actually, we figured it out. Somehow, during the create account process in
PWA, the account was created without an RBS code. Without an RBS, we, as
administrators, could not see the resource in Professional.

I went into the MSP_Web_Resources table and found those resources. After
chaning their RBS EUID from -1 to any value, the resource appeared in our
resource pool and we can now edit as needed.

Thank you for all your comments!

Sara
 
B

Brian K - Project MVP

Sara said:
Hi All,

Actually, we figured it out. Somehow, during the create account
process in PWA, the account was created without an RBS code. Without
an RBS, we, as administrators, could not see the resource in
Professional.
Click to expand...
Another solution for this is to create another Category for
administrators that does not rely on the RBS for it's viewing of
resources. that way you do not create resources you cannot see.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Adding PWA Team Member as enterprise resource error 4
How to delete several resources at once 1
How do I restrict Team Member from opening enterprise resource dat 7
Outlook Desktop (latest) stopped syncing IMAP accpounts from selfowned Mail server. 0
Password Required for PWA/Project Professional 1
Resources Greyed Out 1
Add resources to PWA, when can see them in Project PRO 4
Enterprise resource duplicate 1

Top