Can't create new project in Team Foundation Server - tfs

We're switching over to Team Foundation for our version control, and I have to learn it and set it up. Our IT guy did the installation of the both the data tier and the app tier, and he is of course convinced that it's right. However when i log in as tfssetup and try to create a new project, i get the error:
Error
Insufficient permissions to create a new SQL Server Reporting Services at tsttfsapp1.
Explanation
The permissions granted your user name and ID on the SQL Server Reporting Services at tsttfsapp1 do not allow you create a new project. You must be granted specific permission by the server administrator.
User Action
Contact the Administrator for the SQL Server Reporting Services at tsttfsapp1 and ask that the permission "Content Manager" be added to your user account
So i tried to log in to http://servername/Reports_TFS it asks for the credentials but doesn't accept them. Even stranger when i try to access it from a computer and user that aren't on the same domain as the app tier server, it doesn't ask for credentials and lets me right in. As far as i know the default name of the site should be Reports, not Reports_TFS is it possible that his renaming of that could be causing the problem?
tfssetup is definitely a "Content Manager" as far as i can tell, so i don't understand why we are getting this problem. Also any recommendation for good websites or books that can take a complete beginner and help me become an expert in 3 weeks (what's left of the 6 week time frame allowed for me to learn) would be appreciated.
Thanks

I'm not sure this will help, but we had this error at my place of work on our 2005 TFS server. We opened a ticket with Microsoft and sent them our TFS database. They were able to replicate the issue with the copy of the database. Somehow the TFS database had gotten into an invalid state, but they weren't able to determine how this happened or how to fix it. Unfortunately, this error kept us from being able to upgrade the server to TFS 2008 too. We ended up getting latest of all the code and adding it to source control on a new install of TFS. What a pain.

OK so it turns out it was only a problem because I was using a 2005 client with a 2008 server. A 2008 client has no problem creating a project on the 2008 server, but the 2005 client is not able to create a project on a 2008 server.

Related

TFS246017: Team Foundation Server could not connect to the database

While attempting Branch operation from within VS I get the error message TFS246017: Team Foundation Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server. (The error message box looks like the one in this question).
I logged on to the TFS virtual machine. In event viewer I see a warnning with with the same message as above + Process Name: w3wp, User: domain\MyUser. The IIS TFS site is started.
I opened the TFS console on the TFS machine using both domain\MyUser and domain\tfssetup (this is the user running the Visual Studio Team Foundation Background Job agent service), the console opens successfully. Both users appear in the Administration Console Users list. I did reapply account for both users. I also did update password for domain\MyUser. It shows a connection string with Datasource and Initial Catalog. I logged in to the DB machine, opened SQLSERVER users: the tfssetup user is there with sysadmin and owner of relevant instances. I also added the domain\MyUser and added admin privileges (but the error persists).
I also installed SSMS on TFS machine & was able to connect to DB server using both domain\MyUser and domain\tfssetup and view tables.
This error did not happen in the past. This error didn't happen when branching a different location in the source control ($/Project1/Main vs $/Project2/Main) beforehand. The Source Control Explorer appears to show OK (so TFS is working). Using Visual Studio 2013. TFS 2017. AFAIK Virtual Machines were not moved, IP address were not changed. Using vSphere it seems there is enough disk space for both TFS and DB machines. The error appears after ~4 seconds.
What else can be tried?
Looking in the TFS SQLSERVER log there was a "SERVER ASSERTION" error and this was the cause for the TFS generic error.
In my case the error was very similiar to the one here. CHECKDB and updating to the latest service pack didn't help. What helped was changing the recovery mode to full as recommended in that thread.

Domain credentials suddenly invalid

I previously had TFS 2017 and SQL 2016 working well on a single 250GB Server 2016 .VHDX with two partitions, C: and D:. SQL is installed on C:, with its data directories on D:.
Oddly, C: started filling up unexpectedly, so I decided to move the D: partition to its own .VHDX and expand C:.
This all went well, and I now have two 100GB .VHDXs with C: and D:, respectively. (This is a one-man shop, so data storage needs are quite small at present. These needs will increase soon, however, so this is another reason to split off into multiples like this.)
The trouble comes when I try to sign in to TFS using the same domain account (DOMAIN\User) that worked before all of this took place. I'm now unable to sign in, and I'm prompted for credentials in a continuous loop (unless I cancel the basic auth dialog, in which case I get a 401-Unauthorized).
I've reapplied all accounts using the TFS Management Console, but this hasn't worked. FYI I'm able to boot to the server desktop and connect to the SQL instance and browse TFS tables using SSMS.
What must I fix to be able to sign in as before?
Seems the relationship between TFS and SQL server is destroyed by the partition expanding.
First, please check if there are problems for the SQL Server and TFS databases. If no issues, just try to Re-RegisterDB and RemapDBs for TFS.
If that still not work, I am afraid that you have to reconfigure the TFS. uninstall the application tier then reinstall it again using the existing database. If the SQL Server and TFS database also have problems, you have to reinstall sql server and restore the backed up data.
Similar thread for your reference : TFS 2013 Admin Console locks Tfs_Configuration preventing it's restoration

What reason and solution for WebConnector Error : "Update aborted. Company file is locked by another client ASP17"

I am using WebConnector version -2.1.0.30 with QuickBooks 2015 Enterprise.
WebConnector was working fine but all of a sudden when I run WebConnector and click on "Update Selected" button then it came up with this error (Note: by that time no one was logged on to QuickBooks).
Then as a quick fix I have deleted that QWC file and added a New one, that works fine.
Can any one please come up with a better solution and the reason behind this error.
Thanks in advance.
Chances are you're running QuickBooks on a shared Windows Server, or in a hosted scenario with someone like Right Networks, Intuit Cloud, Cloud9, etc.
If so, this error means that Windows Server auto-logged-out some user and closed QuickBooks for them, but is still holding the file lock on the QuickBooks company file. Windows will automatically release the file lock after a short amount of time (usually 30 minutes to an hour).
There is no "fix" outside of waiting for a while, and then trying again.

Team Foundation Server 2012 broken web access - Error TF400893

I have installed TFS 2012 Express on my computer but I can't get TFS web access portal to work. If I try to view a page with work items I get error:
TF400893: Team Foundation Server services are not available.
This is most likely caused by a network error.
Please check your connection and try again.
It's weird because other parts of the TFS web portal works (e.g. source) so I don't think it's network error. If I connect to the TFS server from Visual Studio everything is working, so I suppose TFS service is running.
I tried to reinstall TFS, but it didn't help :-(
Any ideas what can be wrong?
Try an other browser. I have used Opera and got the error. Using IE should work.
Try changing the account from Applicaiton Tier on TFS Administration Console to your current domain and user info. The default value is NT AUTHORITY.
You should check for any firewalls or other IPS devices between the browser and the application tier for SQL injection attack rules. WIQL being sent from the browser in the AJAX request looks far too much like regular SQL so gets canned by such rules.
As we were experiencing this issue where I work, I decided to take a network packet capture of the browser traffic on a machine experiencing the problem. This yielded a whole bunch of TCP retransmits on the packet containing the plain-text WIQL. Upon presenting this evidence to the company's network team, they located the offending IPS rule which was triggering on these packets, disabled it for packets targeting the TFS Application tier and the problem was solved.
I just got the same error while adding a comment to a work item which included a SQL Statement to drop some tables.
After changing my language to not include explicit T-SQL "DROP TABLE" syntax, I was able to add the comment. My guess is something trying to prevent SQL injection.

Error TF218027 when creating a Team Project in TFS 2010

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.
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.
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.
I just run throught the same issue. I granted the user rights in SharePoint, TFS, and Report Server. And still I was getting the same error message. Then I realized something. I added that user to the Report Server's local administrator's group. It worked! Hopefully this help you out.

Resources