Need a fix to area bug

I am running Visual Studio Team Foundation Server Beta 3 Refresh and have discovered that if a user without sufficient permissions tries to create an Area in the Areas & Iterations dialog that an error is given to the user but the Area is still created. It appears that the Area was not completely created though, it shows up in that dialog list, but is not available to be used by work items and it cannot be deleted by anyone. When I (from a global administrator account) try to delete the area, it gives me this message: "TF50309: You do not have sufficient permissions to perform this operation. Node cannot be deleted.". Is there a fix for this issue

Answer this question

Need a fix to area bug

Kazuryu C.
The areas actually got created in the database though. To explain how it worked, a developer who didn't have permissions created the areas, then I (an admin) on a different machine was able to see those areas but cannot delete them. So somehow they are in the database and need to be deleted. Can you at least direct me to the database and table where they would be located so I can delete them manually I could probably find them, but that might take a bit.
Nazim

Technically, the developer had half of the requisite permissions for B3R. There was a bug in B3R that area nodes would not registered with the security service if they were created by a user who had "Create and Order child nodes" permission but did not have "Edit Project-level information" permission. The result is that there is a node in the area tree upon which nobody has the rights to perform actions (delete, rename, move, etc).

It would be a very bad to manually delete rows from the database for this particular problem. Area and iteration information is actually mirrored in two databases with an external syncing process to maintain the parallel data structures. If performed incorrectly, altering the data could either leave the node in an even worse half-created state or cause the entire process to break down.

If you are planning to upgrade to RC, I would recommend waiting as the safest approach. After the upgrade scripts run, these half-created nodes will become fully-created. Afterwards, you or any other project admin may delete them through the UI.
MeMarko
Hi Bernd,

We do not have an existing script for this.

You can also try deleting the cache on the client to make it work on the Beta version. The client cache is located at:

<drive>:\Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Team Foundation.

You might also want to run the 'devenv' with /resetuserdata option.

Thanks,

Avanti
Ozzie Garzon
I'll just wait for the RC then, luckily the developer that created the nodes didn't create ones we actually wanted (not sure what he was thinking). Do you have a date for the RC yet Last I heard it was mid-February.
ShermanChin
Hi Bernd,

I am not able to repro this on the latest bits. It might have been fixed in some recent syncing fixes.

Thanks,

Avanti
Udhayakumar
Well, I guess I'll just wait for the RC to be able to not have it come up again. Is there a way (probably a SQL script) that I can delete the areas that were created by the user with insufficient permissions
Odysseus11
Hi Bernd,

I will follow up on this issue. I will open a bug in our system if needed.

Thanks for pointing it out.

Avanti
sirmmo

The latest information about the RC can always be found in Jeff Beehler's blog:

http://blogs.msdn.com/jeffbe/

I forgot to mention that, after RC, "Create and order child nodes" will be the only requisite permission for creating new nodes.
Need a fix to area bug

Answer this question