Error TF218027 when creating a Team Project in TFS 2010

Question

Consider the scenario of a user creating a new Team Project. The user is a developer who wants to create and manage their Team Project.

• Why can't this user create a new Team Project, including the Reporting Services components?
• What can be done to resolve this error?

The exception is

TF218027: the following reporting folder could not be created on the server running SQL Reporting Services.

SQL Reporting services is running under an Active Directory service account created expressly for this purpose.

The developer attempting this action is a member of a TFS group with the following permissions.

Answer 1

The workaround way that I implemented was to ensure the developer was in a group that had 'Content Manager' permissions in the SQL Reporting Services.

I simply added the appropriate AD group in the textbox, and the operation worked perfectly. First I visited the SSRS page at http://myServer/TFS/Reports/MyCollection

Enter the "New Role Assignment" screen.

Answer 2

I actually blogged about this not too long ago. You usually see this error if Reporting Services gets set up with something other than the NETWORK SERVICE account.

FTA:

I was playing around with my test instance of Team Foundation Server today, trying to create a new project, when I got error TF218027 when it tried to create the Reporting Services folder for the project. The strange thing was, this was not my first project created on this server.

I searched the Internet for anything similar, and found a post that said Reporting Services should be run with the NETWORK SERVICE account. Since this was a hastily put together server, I was running it with the Administrator account, so I tried switching it over.

No dice. I got the same TF218027 error, but this time it was due to it not being able to decrypt the symmetric keys. Apparently, it's a bad thing to change the account on the Reporting Services service.

I hastily changed the account back to Administrator and resarted the service. Interestingly enough, this seems to have fixed the problem.