Y
yann dupre
We have been experiencing an extremely weird behavior: When initially
implementing Project Server 2003 in our organization, we experimented
with Administrative projects. We created such an admin project with 3
tasks. However, after a few tests, we concluded we would NOT use admin
projects so we deleted the test admin project.
For some weird reason, when we create a new work resource (user) in the
global resource pool, that resource is apparently AUTOMATICALLY
assigned to the 3 tasks of that DELETED admin project: Right after
resource creation, we ask the user to log in to PWA, and instead of
being empty, their task list shows the deleted admin project and the 3
tasks assigned (!!!) We can also see that in the "Adjust actuals"
function of the resource tab.
I have searched everywhere for administrative project documentation. As
far as I know, newly created resource/user should never be
automatically assigned to a project, let alone a DELETED one.
Question 1: Has anyone experienced the same behavior and what did they
do about it? The issue is that users cannot hide tasks that belong to
admin projects.
Question 2: We believe we have some weird corruption in our database.
Is there a tool out there that allows to TRULY delete a project and all
associated tasks and assignments from the database (not just flag items
as deleted which seems to be what the PWA cleanup functions do).
Thanks
Yann
implementing Project Server 2003 in our organization, we experimented
with Administrative projects. We created such an admin project with 3
tasks. However, after a few tests, we concluded we would NOT use admin
projects so we deleted the test admin project.
For some weird reason, when we create a new work resource (user) in the
global resource pool, that resource is apparently AUTOMATICALLY
assigned to the 3 tasks of that DELETED admin project: Right after
resource creation, we ask the user to log in to PWA, and instead of
being empty, their task list shows the deleted admin project and the 3
tasks assigned (!!!) We can also see that in the "Adjust actuals"
function of the resource tab.
I have searched everywhere for administrative project documentation. As
far as I know, newly created resource/user should never be
automatically assigned to a project, let alone a DELETED one.
Question 1: Has anyone experienced the same behavior and what did they
do about it? The issue is that users cannot hide tasks that belong to
admin projects.
Question 2: We believe we have some weird corruption in our database.
Is there a tool out there that allows to TRULY delete a project and all
associated tasks and assignments from the database (not just flag items
as deleted which seems to be what the PWA cleanup functions do).
Thanks
Yann