After all that, installing the client should be easy, right? Well, install ran OK, but when I try to run it, get message box saying "Invalid license data. Must reinstall". Need I say that reinstalling didn't help?
Installed and attempted to run using same tfssetup a/c used in server installs.
Any suggestions?
Many thanks,
John Rhoads
Thanks,
Michael
I am having the same issue. I followed the directions for single server installation. I also noticed that Sql Server did not install the Sql Management Studio... either that or Team Foundation empties the IDE directory on install.
Any help would be apprieciated.
Thanks
Victoria
Ok, I uninstalled everything and started over. This time I selected to install Client Tools and Books etc (the last option) which prompted for CD2. I no longer had the License problem.
But now when we try to create a new Team Project, it fails because it can't connect to Share Point (which was only installed as Server Farm).
We give up. Spent two full days on this.
All,
Sorry to hear of your frustrations.
The invalid license issue is in many cases related to installing different versions of the products. For the client, I assume you mean Team Explorer (Team Foundation Client is its old name).
Do you also have a copy of VST* on the machine?
We've seen this issue when there is version of VSTS (or other Whidbey product) which is later than the PDC build.
The SQL tools issue is interesting, was this on your client machine or TFS machine? And, which version of SQL were you using?
In any case, we see this typically when product versions don't all align.
marc
This must have something to do with the SQL tools installing visual studio before Team Explorer.
-win2003
- SQL Server 2005 standard (release version)
- WSS
- WSS SP2
- TFS
- TFS Build
- TFC client
the SQL server management studio is also not available.
any solution?
I did change the install routine.
In SQL server I also checked client tools and notification services.
I also downloaded WSS with SP2 included and installed that version.
I now have the following install order
- Win 2003
- IIS
- MSSQL 2005 dev edition full version (all options checked)
- WSS with SP2
- TFS
- TFS build
- TFS client.
We have recently found an issue where TFS build drops a key in the registry that confuses windows installer during the setup of Team Explorer. After installing TFS Build, you should look in the registy, and remove this license key.
HKCR\Licenses\895E2152-C3F9-4C49-968B-15B08ADA0F37
If you already have Team explorer, you should uninstall it, remove the registry key, and reinstall it. Nicolas Coderre
After that, you can safely install Team Explorer.
SDE, CoreIDE
6A7693BA-3139-41fd-BF3D-299961C965D5
A3CA4A41-58C9-4804-8B80-11FAD9E20A2A
CCF5A555-D92E-457b-9235-2B326B64035A
I have previously uninstalled my VS.NET betas in preparation for installing the RTM versions.
Can you help?
Shaun
Thanks! Aaron
