Tim Elhajj

One IT PRO writer vs. all of MSDN


Leave a comment

Upgrade SQL Server 2012 for TFS 2013 to SQL Server 2014

Originally posted on Team Foundation Server, SharePoint Server, .NET, and SQL Server:

Starting July 1st, Microsoft will be adding SQL Server 2014 to the list of license grants for Team Foundation Server 2013.  SQL Server 2014 is supported by TFS 2013 with the caveat that it has increased hardware requirements compared with previous versions.

Microsoft also has a KB Article titled “Performance decreases in TFS 2013 Update 2 after you upgrade to SQL Server 2014″ which you should also be aware of if you have a large configuration (> 500 users).  It specifically addresses a Work Item Tracking performance issue and can be easily mitigated by increasing the RAM by 410MB on the server hosting the SQL Server instance for each Team Project Collection database.

Example: two (2) Team Project Collections X 0.4 GB = 0.8 GB of RAM

Note:  If you have SQL Server Reporting Services deployed on a separate server in your TFS 2013 environment make sure you don’t forget…

View original 109 more words


Leave a comment

Did you uninstall Release Management Server and lose access to the Release Management client?

It can happen. If you uninstall the RM server and a client is still pointing to that server (one that is now no longer available, because you just uninstalled it), you will get this error message the next time you launch the client.

You can recover by using ReleaseManagementConsoleAdjustConfigFile.exe, a new command line tool included with VS update 2. If you installed using all the defaults, you can find it  here: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\

Use an administrative command prompt and run this command:  

ReleaseManagementConsoleAdjustConfigFile.exe -configfilename .\Microsoft.TeamFoundation.Release.Data.dll.config -newwebserverurl http://servername:1000

Where:

  • ConfigFileName, use the name of the config file.
  • NewWebserverUrl, use the URL to the new Release Management server and its port number.

The tool will update the configuration file with the new URL. You will not get any success notification in the command prompt. The next time you launch the client, it will connect to the new server. If the new server you point to isn’t the same version as the client, you will be prompted to update the server.

If you have trouble with the command line tool, there is another option. You can uninstall the client and install it again. After the installation, you will be prompted for a server URL. Both tasks achieve the same goal, so it’s really up to you.


Leave a comment

2013 in review

The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 35,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 13 sold-out performances for that many people to see it.

Click here to see the complete report.


2 Comments

TF18017 or TF250044: having problems with the TFS project creation wizard?

Have you ever had this happen to you? You installed TFS with SharePoint for a colleague. You make sure TFS is running, make sure SharePoint is up. You add your colleague to the local administrators group. You add her to the TFS admin tool. You write her an email telling her where to find her fresh installation of TFS and you’re just about to pat yourself on the back, when you get a message from her saying she can’t run PCW. She’s getting an error message that looks like this one:

If you’re anything like me, you sigh mightily.

Why can’t she (user2) run PCW? What is this about!? I already added her to the Farm Admin group (see below), but that didn’t help with this error.

It’s a permission issue, but it’s not Farm Admin permissions that’s needed. The solution is to add the user in question to the SharePoint site at the collection level. So, for example, navigate here on the SharePoint site (not the SharePoint administration site, but the site where the portal for the team project is created):

http://sharepoint:80/sites/defaultcollection/default.aspx

Here is what I did:

1) Someone who already has permissions has to go to /sites/defaultcollection/default.aspx and share the site with the new user.

2) Once you add the user, go to site permissions (click the wheel) and then give the user “full control.”

If you click the name, it lights up Edit User Permissions and you can click Full control on the next screen.

And Walla!

Redmond\user2 can now run PCW with success!


Leave a comment

How to restart Win8 from a remote session

This used to be so easy.

Two options I know of for restarting the server (Win8 or WS2012) in a remote session.

1) Get to the desktop and then use Alt + F4 to get this:

Make sure you minimize anything else running on the desktop, or you’ll have to shut down each app individually, possibly muttering like a grizzled old man trying not to step on any of his cats on the way to the bathroom.

2) The other thing you can do is a the “shutdown /i” command from an admin CMD prompt.

Follow

Get every new post delivered to your Inbox.

Join 924 other followers