Skip to main content

TFS 2010 Setup: Gotchas

I'm sure I missed a step somewhere during setup but...so the search engines catch 'em, I'm going to post my TFS/VSTS 2010 setup missteps below:

Issue: "TF255147: The following server that is running SQL Server is not listening on the expected TCP port: SERVER"
Resolution: Open SQL Server Configuration Manager. Under SQL Server Network Configuration, Protocols for MSSQLSERVER, right-mouse Enable TCP/IP. Restart SQL Server. Re-run TFS configuration wizard.

Issue: "TF255282: Windows SharePoint Services 3.0 cannot be installed. The program is already installed on this server"
Resolution: Open up Add/Remove Programs (or "Programs and Features" under Win2k8 Server) and remove Microsoft Windows SharePoint Services 3.0. Re-run TFS configuration wizard.

Issue: Couldn't get Full-Text search within SQL 2008 to install.
MSI (s) (14:AC) [00:03:21:091]: Source is incorrect. Unable to open or validate MSI package D:\Setup\sql_engine_core_shared.msi.MSI (s) (14:AC) [00:03:21:093]: Note: 1: 2203 2: D:\Setup\sql_engine_core_shared.msi 3: -2147287037 MSI (s) (14:AC) [00:03:21:093]: Source is incorrect. Unable to open or validate MSI package D:\Setup\sql_engine_core_shared.msi.Please insert the disk: Please insert next disk
Resolution: I'm installing on a VPC so I simiply download ISO installs, "Capture ISO image..." from the CD menu of the VPC and install. Works great...usually. In this case, for some reason, the installation would get 2/3rds to completion and die with very innocuous errors. I kept coming up empty searching for "error" within the 500k MSI log file. Finally stumbled onto something referring to "Unable to open..." having something to do with subst.exe and network or simulated mapped drives. I expanded the ISO with MagicISO, copied it to the VPC hard drive and wala, no more issue. That was a good 6 hours of struggle.

Comments

Jason Barile said…
Thanks for sharing these Jeff!

Popular posts from this blog

TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.

Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.

I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.

Detailed message:


TF53010: The following error has occurred in a Team Foundation component or extension:


Date (UTC): 6/7/2011 4:18:53 PM

Machine: TFSATBOX

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600

Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)

Process Details:

Process Name: w3wp

Process Id: 3676

Thread Id: 5752

Ac…

Verified by Visa: Everything We Tell Folks to Avoid

Phishing is defined by F-Secure as: "Fraudulent e-mail or website claiming to be legitimate seeking indentifiable information. Phishing is an attempt to steal your personal data."When I recently attempted an online purchase from WalMart using my VISA card, being a security wanta-be, I immediately thought phishing when redirected to verifiedbyvisa.com and saw this dialog:

Seriously, these folks have to be kidding. You're asking for my personal data during a transaction and claim that's its a service "...at no additional cost." Wow! Thanks...but absolutely not, you jokers. As a malicious thief, I can go a long way with this data.

This is exactly the type of experience which aids malfeasance and the folks trying to steal personal data / identities. How long have we been working to educate folks to avoid providing this type of data under these type of circumstances? Years. And we're just now starting to turn the corner.

VISA, get rid of this! When folks submi…

Windows 10 Creator's Update and Office Conflicts

Recently, Microsoft pushed the "Creators Update" out to Windows 10. It was available in April but it seems to have been force-pushed in the past 2 days. On my mother-in-law's computer, Creator's caused Excel to render a "Bad Image" message when attempting to start declaring "MSVCP140.dll is either not designed to run on Windows or it contains an error". I attempted the SFC and DISM repairs as advised on Tom's site to no avail. When I attempted an Office repair, Office disappeared completely. At this point, I definitely started to panic.

Fortunately, I noticed a pending reboot due to an install/update. Allowing Windows to install that update and rebooting twice brought Excel and Office back to life. I did have to re-register the software but all is well now. If you encounter this issue, stop what you're doing and install/restart Windows. Anecdotally, I've since hear of many folks encountering similar issues.