What is this about? Read more about Visual Studio Team System here:
You can get VS2005 Beta2 as a MSDN subscriber or get the Visual Studio Team Suite Beta Expericene Kit here (for just 10 bucks, which is the cost of shipping): http://msdn.microsoft.com/getthebetas/
Installing Visual Studio Team Foundation (VSTF) when knowing what to do, takes around 5-10 hours, installing without much of a clue (like most of us) can take a couple of frustrating days. Most of the time you are waiting for an installation to complete, have a good book nearby :)
Don't install VSTF if you don't have the time for it, its still a Beta and the installation process is horrible (better than for CTP1, but in no way userfriendly).
First of all: I tried installing Windows 2003 Server to a Virtual PC 2004 and then doing all the steps described in the installer instructions, but it got WAY to slow. I got so many problems I started everything over with Virtual Server 2005, which worked much better and didn't cause any headaches when restarting or closing any remote control window. You can also use VMWare, which is a bit faster,
but still you will only get around 50% of the normal performance, read more about this here.
I got everything working with Virtual Server 2005, BUT its so freaking slow, its no fun to use (and you might get some timeouts while installing or creating projects, which may cause trouble). I had to wait up to several minutes until the VSTF server reacted, the overhead for the sql and vstf services is huge. For just checking VSTF out this is fine, but for using it, you should have a fast server.
Only for this reason I would really recomment installing everything on a single extra computer, start from a clean OS and work your way through the installation, if you have enough computers, you might also try the 2 server installation (1 data tier and 1 app tier). Before starting you might also want to set up an Active Directory domain (if you don't have one yet) and the required accounts for Team Foundation Server.
The TFSSetup account must be a domain account and have admin rights at the time of the installation, the TFSService account will work fine for the installation, but you might have to create a new account for the first login on your client machine later on. Install Win2003 and then use VNC to continue working, you will need a lot of copy+pasting, which is much easier to do from your comfortable PC ^^
This are my Visual Studio 2005 Beta 2 Team Foundation Server CTP (April 2005) Installer notes:
- Creating a project on the client might fail with a timeout (Rosetta stuff timed out) if the server is busy, this happend to me twice, so I suggest creating your first project directly on the server (with VS2005, just install the client tier). If the project creation failed on your client, just do it again with the same settings on the server and you should be fine (else you will have an unfinished project, not very pretty).
- Little tip at the end: You need a user to create anything in VSTF, if you are using VS2005 Beta2, just use "Run as" and enter your TFSSetup account, now create a new project and create a user for you as described in the official guide (you need a active directory account):
Now close VS2005 Beta2 and log on with your new account.
- On the Team menu, point to Team Foundation Server Settings, and then click Groups.
- In the Global Groups dialog box, select the group you want to add users to, and then click Properties.
- In the Team Foundation Server Group Properties dialog box, on the Members tab, select Windows User or Group, and then click Add.
- In the Select User Names or Groups dialog box, enter the domain name and username of the users you want to add.
- Time to read the Process Guidance, fill data into your project and start working :)
Just browse to the msdn forums and search there if you have a problem, maybe someone before you already had it and it was solved: http://forums.microsoft.com/msdn/
Most helpful link for me (stsadm + full trust issues for report service):
Optional section in case you have problems installing:
- I only needed this one time because something went wrong with SharePoint, you might want to skip this if everything is working fine. Also use this if the first attempt failed and you try again reinstalling (after restoring the pre VSTF installation state):
- If http://localhost/ site is not working (it should point to the team web site, same as http://localhost/Reports/), make sure the following line exists in the HttpModules section of C:\Inetpub\wwwroot\web.config:
<add name="Session" type="System.Web.SessionState.SessionStateModule" />
(That entry will already exist, but it is commented out, remove the <!-- and --> comment tags.)
In addition to adding the session state module, you must also enable session state for the pages element by changing the enableSessionState attribute from false to true. The entry in the configuration files should look like the following:
<pages enableSessionState="true" enableViewState="true" enableViewStateMac="true"
- Finally (this is optional, but it doesn't hurt), use the rsactivate utility to activate the local instance of Reporting Services. You need to install Administrative Tools and Utilities as part of Reporting Services setup in order to use the rsactivate utility. By default, rsactivate is located at C:\Program Files\Microsoft SQL Server\80\Tools\Binn. If you installed your report server to the default location, run the following at the command prompt:
rsactivate -c "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
- I would also restart the System now (again) if you did the past 3 steps to make sure all services start up correctly.
VSTF Installer Abort Errors:
- Issue: Setup fails when installing ADAM (Active Directory Application Mode).
This happend for me because I failed to logon with TFSService and continued installing with TFSSetup. I guess Active Directory authentication failed, there were also a lot of NetLogon errors in the system event log (no domain server found stuff).
After installing Active Directory correctly and no more NetLogon errors the installation succeeded finally. If you install Active Directory after IIS, Sql Server 2005 and SharePoint, make sure the http://localhost/Reports and http://localhost/ReportServer/ReportService.asmx work. You might have to adjust the security settings for some folders for the network service used for this websites on the following folders: C:\Windows\Microsoft.NET, C:\Windows\Temp and maybe more, check out the site error for additional dependencies.
- Error 26xxx (I don't remember the exact number anymore, 26201, 26202, 26204 or so):
I had them only in my first try and the reason was wrong order of installing SharePoint services stuffand not putting it in a seperate app pool, worked after fixing that. Google for your error if it is not sharepoint causing this trouble.
- Error 32000 (most common)
The full error is most likely: "Error 32000: The command line "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin\BisSubscribe/exe" /eventType ArtifactChangedEvent /userid Domain\TFSSERVICE /deliveryType Soap /Address http://localhost:8080/Currituck/BisService.asmx" returned non zero value: 1."
- BISIIS stuff, this is the error I had the most time when installing, retry did help for timeout issues, but did not help when something else was wrong.
It usually means something above failed and you are in trouble (either you did not follow some of the tips or there is something wrong with some web service components, check the installation log for more details and search for help at google and http://forums.microsoft.com/msdn/).
- Basically check if sql stuff (4 services) are running and localhost/reports and /reportserver do work without errors.
- Check out the Useful links section.
- The only way reinstalling worked for me in the first try was to completly reinstall windows 2003 OR using a backup (described above) to restore a previous disk drive state. The other suggestions here might work too, but I didn't got them working, so I won't recomment them.
- This might also work: For Reinstall delete any vstf directories, uninstall ADAM, remove TFSService from security in SQL manager and delete all VSFT databases.
- My TFSService account didn't work for my second install so I kept retrying and created a new account, it did not work either (maybe some kind of AD login error). Trying to fix this I logged out with TFSSetup and logged on with that account (TFSService) and then logged out and used TFSSetup again to install. That didn't help, I continued using a backup and started over (at least that worked ^^).
See above for the Active Directory issue (which was the cause for this problem).
- Then installing worked until I got some error with a temp file, then ADAM install failed, after
I removed some files, that worked, but then the MSI installer failed with some HRESULT with not much
help about it when searching google.
Instead continuing pocking around for more hours I just reinstalled Win2003 and started over using my plan here, then finally everything worked. The full reinstall did take less time than fixing all those errors, which is really annoying and frustrating. Reinstalling works most of the time by itself, you just have to press some buttons and wait for the most time.