Whilst installing a TFS & CCNet demo system I got an exception
System.Security.SecurityException: That assembly does not allow partially trusted callers
when I tried to load the CCNet WebDashboard.
The problem was that default CCNet installer had created the WebDashboard on the default web site as the virtual directory
As this was also a TFS server the default web site was a WSS3 server. Bascially the SharePoint did not like (trust) the CCNet virtual directory’s DLLs.
The fix I used was to create a new website and point it as the WebDashBoard directory so it could be accessed without effecting the SharePoint e.g.
I could also have edited the SharePoint’s web.config to trust the CCNet DLLs
I was installing a Dual Tier Team Foundation Server 2008 at a clients today and got a problem that when installing the Application Tier (AT) I entered the name of the Data Tier server (DT) and it said the server could not be found.
Unlike TFS 2005, 2008 does not require you to to do a separate install on the DT to create the empty DBs, so I assumed it was just a connectivity problem. However there was none to be found, so I checked the detailed TFS install error log and saw I had a TS220066 error that also mentioned SQLRS – I guessed at a reporting services issue.
I turns out, stupidly, I had forgotten install SQL Reporting Services on the AT – after all I have previously posted about following the walk-thru for the install!
Once this was installed all was OK; so if you cannot see the DT during the AT install it may not be the remote connectivity issues the dialog says, check the error for more details.
Don’t make the mistake I did with Team Foundation Server 2008 media on MSDN downloads.
The MSDN file en_visual_studio_team_system_2008_team_foundation_server_workgroup_x86_x64wow_dvd_X14-29253.iso is the workgroup edition, as the file name suggests. The problem is that you cannot upgraded it to a full edition. TFS documentation says that a trial or workgroup edition can be upgraded by entering a valid CD-key when in Add remove programs, maintenance mode; however this option is greyed out if you install from this media. I checked with Microsoft and there is no way round this for this ISO image.
So if you want to install or upgrade to TFS 2008 full edition make sure start with the right media, else you will downgrade your installation to a 5 user workgroup.
Since I upgraded my VS2008 Beta2 to the RTM, the intellisense has not been working. I have seen a few posts about this, some suggesting you need to reset the configuration by running
but this did not work for me.
So I had a poke about in Tools|Option and found that on the Text Editor|All Languages that the three checkboxes for Statement Completion where showing neither empty or checked but a fully coloured box – which usually means an unknown settings. So a set these all to checked (a tick) and my Intellisense started working.
Today I had to do some work on an old VB6 system, a development environment I do not have on my Vista laptop.
So I copied a Virtual PC image I had with most of the tools I needed and ran it on one of our Virtual Servers. As this VPC needed to run at the same time as the VPC I copied it from, I ran NewSid to change the SID and the PC names.
All seemed good until I tried to use the network, both within our LAN and the Internet it was very intermittent, but I saw no errors.
To cut a long story short the problem was I had two VPC images with the same MAC address. Once I stopped the new VPC, changed the MAC address and restarted it all was fine.
So the Technical Tip is – if you copy a VPC image you need to run NewSID and manually alter the MAC address to avoid network clashes
I have been working on my DDD6 demo, I intend to show eScrum at end of my session on Scrum. I thought I would use the VPC I had from DDD5, this was based on the TFS Orcas Beta1 and had all the tools I wanted configured. To get some more realistic data in the reports I wanted to leave TFS server running for a week and on a daily basis update the work items as if the project was progressing.
The problem was the underlying operating system evaluation license expired at the start of November. So I tried:
- a Windows 2K3R2 disk and did an in-place upgrade with a valid key, this seemed to work but when I tried to run any ASP.NET it failed, basically all the rights seemed to be lost
- tied to force the system to ask for a new key using the KB328874 procedure – this does not work on Windows 2003, just XP it seems, though some web sites seem to say it does work.
- did a SYSPREP on the server, this allowed me to enter a new key, but after 1 hour I still got the evaluation period expired message – it seems you have to use new media to removed the evaluation time bomb.
So this left me back at a fully working Beta1 VPC that was on an expired OS, or the option to installed a complete new system using VS2005 with ‘real’ licenses, from scratch.
But then I thought about what ‘expired’ means for a Windows 2003 evaluation install; it means after 1hr you get a message the server has expired, and an hour later it restarts. Now this is not much use for any real application, but does all I needed, so I could have saved a good deal of messing around over the past couple of days!
I was still a little worried that the bi-hourly resets may mean the timed jobs that keep the TFS data warehouse up to date might not occur, so I also installed the tool by Eric Lee to allow the update process to be triggered whenever I needed it
So hopefully I now have a system I can build a reasonable demo data set on over days up to DDD6.
For a while I have been suffering that when I switch on my Acer Core2 Duo Vista laptop, both cores sometimes go to 85%+ utilization, so the PC is slooooow. Usually after a few reboots it seems to clear. This can happen after a resume from hibernate and complete restart; there was no obvious pattern. Task manager only says that the load is due to the NT Kernel process – so not much help there.
After a bit of google’ing I found other people reporting the problem after installation of Microsoft Network Monitor 3.1, which I did months ago Interestingly I have only seen the problem is recent. However, as soon as I went into the network protocol stack and disabled the network monitor protocol on my WiFi card the problems have gone away.
My guess is some strange race condition caused by a recent service patch; this not a major problem as you can switch the protocol on and off as required without a reboot.
It turned out to be two problems:
Some the projects I had registered to be used via the Escrum web site were not using the eScrum template, they were using the Conchango Scrum one.
So the fix was to follow the method at the end of http://msdn2.microsoft.com/en-us/library/ms194914(vs.80).aspx i.e export the work item types then import them. Once this was done I could select the updated project and got not errors.
The only down side of this method is that the project now contain the old and the new style of work items, but I can live with that.
You also have to import all the Reporting Services reports, if you don’t eScrum cannot show you reports. You do this via http://localhost/reports then add the reports from the WIT export you created. Remember to add spaces to the names of the reports e.g. SprintBurndown.xml becomes Sprint Burndown. I also had to then edit each report to point it at my global data sources (Reports and OLAP) for TFS in Reporting Services
When creating a product in eScrum you have to assign the product owner (and you can also set the team members). The combo for the product owner is filled using the contributors – not the administrators, so make sure the users are in the right group.
If when you add a user to a group in TFS and it does not show up in the eScrum product owner dialog, do a AppPool recycle on the eScrum site to clear the cache.
NB The way we manage users is to add an Active Directory group to each TFS group then manage user rights to projects in the AD.
As I posted before I have been updating our TFS server to 2008 Beta2, today it was the WSS from 2.0 to 3.0. Well I followed the process on Sudhir Hasbe’s blog and it just worked, so now we have WSS3.0 running the the TFS application tier. The final step will be to move the SharePoint sites to our main MOSS 2007 farm, but that is for another day.
As part of today’s upgrade I was working on process templates. We use Escrum but I had noticed our Escrum web site was not showing all the projects using that template. I had completely forgotten that you had to manually add Team Projects to the Escrum web site. This is done using a URL like:
The main reason I forgot this is that the admin page is not shown on any menu! A nice bit of security by obscurity. Anyway using this admin form you can add projects to the Escrum web site. The problem is that the UI does no validation other than checking you typed a string. You have to know and type in the projects names correctly. Once the entry is made it is stored in the
[program files]\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Escrum\RegisteredGroups.XML
Useful to know the location so you can remove the rubbish you type in by mistake.
Today I decided to bite the bullet and upgrade our ‘live’ TFS installation to 2008 Beta2, now there is support from Microsoft. The only reason I have delayed this long has been we have been involved in the delivery of a big project and I did not want to take the TFS server down for any reason.
Our TFS installation is dual server, the data tier (DT) running on our central SQL2005 64bit server and the application tier (AT) on a virtual server as a VPC. I have kept the AT virtual as it is easy to backup.
So the first thing of note that surprised me is that you do the upgrade only from the AT. Before I read the installation notes I had assumed you would update the DT and then the AT like the original installation.
Anyway I ran the setup.exe on the AT, it found a few warnings but they were all down to the fact I was running on a VPC (warnings over CPU performance, memory and disk size), so I continued with the upgrade gave it some user IDs and pressed start and it progressed OK first installing .NET 3.5 then TFS 2008.
During the TFS 2008 upgrade I got two errors that stopped the setup with a ‘retry or cancel’ option. In both cases I managed to fix the issues and a retry worked. This is what I had to do to fix the problems:
- Error 29109 Team Foundation Report Server Configuration – All this turned out to be was a timeout. On the AT I opened the URL http://localhost/reports in a browser (this took a long time for some reason) but I did eventually get the usual reporting services page. I then retried the step in the upgrade tool and it continued fine.
- Error 28925. TFServerStatusValidator – Basically this means the setup program cannot access http://localhost:8080/services/v1.0/ServerStatus.asmx on the AT. If you manually run the URL you get a generic ‘page not found’ error. On looking the the event log I was that an ISAPI filter authenticationfilter.dll for the TFS web site could not be loaded. Interesting the path it was trying to loaded was for TFS2005, and of course this file no longer existed. I then remembered that we had installed this ISAPI filter when we had TFS 1.0 and were trying to get HTTPS connectivity working, so I just deleted the ISAPI filter entry, I then checked I could start the URL in a browser and then tried the step of the setup and it continued OK
When all this was done the server was rebooted and it had been upgraded server.
The next step will be to upgrade the AT from WSS 2.0 to WSS3.0 then move all the Sharepoint bits our central MOSS 2007 server, thus making the AT little more than a web server.