I'm trying to upgrade from TFS2012.2 to TFS2012.3.
I downloaded the ISO, ran the tfs_server.exe, and after a few reboots, I'm prompted with the Upgrade Wizard.
On step two(2) "Specify a Team Foundation Server configuration database to upgrade", I need to specify a SQL Server Instance. But when I click "List Available Databases", no database shows up in the list.
I tried different combinations of SQL Server Instance (servername, servername.domain, ., (local)) but all of them returns an empty list. Note SQL is not running named instance.
SQL is up and running and I can see the TFS databases (Tfs_Configuration, Tfs_DefaultCollection, Tfs_Warehouse).
Everything is running on this one machine.
Digging deeper, in the Event Logs (Team Foundation Server Build Service Events), I found this:
Exception Message: TF400686: The requested schema property TFS_SCHEMA_VERSION did not match the expected value. The server requires the Microsoft Team Foundation Server 2012 M49 schema but the database currently implements Microsoft Team Foundation Server 2012 M44 (QU2). (type DatabaseSchemaException)
I'm not sure if this is a clue or not.
Last point: If I go to the TFS Admin Console, when I click on Application Tier, the screen shows a "This features has been installed but needs to be configured. Click on Configure Installed Features to begin initial configuration."
Did I miss a step?
Related
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.
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
Usually connect to an external database but I wanted to fiddle with creating a project with a local database. I am using SQLServer Express Local Database, not CE.
I can add tables with EF but if I right click on Tables in Server Explorer the only options I have are Refresh and Properties, i.e. no Add Table menu option. Similarly, if I right click on one of the tables EF has created I also get only the Refresh and Properties menu options so I can't add rows, etc. Same problem with stored procedures; I can't add any (should I want to do some testing with EF and stored procedures) because I only have the Refresh and Properties menu options.
FOLLOW UP:
I have isolated this problem to VS2012 Professional. When I use VS2010 it works exactly as expected: I can add tables and stored procedures. Following the same steps with VS2012 results in the situation where there is no menu option to add either tables or stored procedures. I produced these test results with SQLServer 2012 LocalDB.
If you only see Refresh and Properties when you right click on Tables in Server Explorer, you probably need to install SQL Server Data Tools from http://msdn.microsoft.com/en-us/data/hh297027 .
I had a similar problem only with Visual Studio 2012 Express for Web following along with the "Getting started with ASP.Net MVC3" at www.asp.net. The tutorial used a Sql Server Compact edition but I have SQL Express 2012 so I changed the connection string to have the data source point at my local instance, .\SQLExpress2012. The app worked fine and was able to read and write to the database. However I could not edit the database in the Visual Studio Express Database Explorer (all the context menu options were missing except "refresh" and "properties).
I found that changing the data source in the connection string to "Data Source=(LocalDB)\v11.0;" fixed the problem. I read somewhere that if you use LocalDb instead of the SQL Server instance name then it will be accessed under your user account - must have been some kind of permissions issue.
The whole (working) connnection string is:
"Data Source=(LocalDB)\v11.0;AttachDBFilename=|DataDirectory|Movies.mdf;Integrated Security=True;"
Hope this saves someone a bunch of hours pulling their hair out, I'm almost bald now :)
I found that when installing Visual Studio 2013, I had not requested the 'SQL Server Data Tools' feature.
By re-running the installer from 'Control Panel' > 'Programs and Features', using the 'Modify' option, I could add the missing feature. On completion, the 'Add New Table' menu item was available.
I created a "Test" project that I want to delete, using the following command:
TfsDeleteProject /server:xyz\sqlserver2008 “Test“
Getting this error:
TF30076: The server name or Uniform Resource Identifier (URI) you typed,
xyz\sqlserver2008, cannot be
resolved to a Team Foundation server.
If you type a server name, it must match the name you typed in the
Add Team Foundation Server dialog. If you type a URI, it must use
the following syntax: http[s]://:
The server instance is valid. (The installation of TFS is app tier and db are on seperate boxes) What might be going on ?
xyz is eht server name, sqlserver2008 is the db instance. For eg. I access the db using sql server management studio client app using xyz\sqlserver2008 as dbname.
Specify the full server URI including the http:// and :port. Also look for these error numbers in the MSDN.
Edit: Follow the first link, Andrew posted that's where I got my info from :)
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.