Installing Team Foundation Server beta 3
Tue, Sep 27 2005 4:56 PM

I got the opportunity at my work to start an experiment with Team Foundation Server. It took me all day yesterday to install beta 3.

While installing beta 3 I kept getting the error 28100 because the Event Web Service could not find the Microsoft.TeamFoundation.Common component.
Luckely with every installation step, I made a Ghost image so I could restore the machine to a clean state after every attempt. That turned out to be a basic necessary because the Foundation Server installation rollback removes more then its installed components.. (It also damages SharePoint services.)
I noticed in the detailed setup log that an error concerning a user id occured at a earlier point in the installation. Apparantly it is not considered critical and the installation ignores it.

I had followed the installation guide (TFSInstall-v50920.chm) to the letter. As the installation guide stated as an option I used different account names than the examples TFSSETUP, TFSSERVICE and TFSREPORTS. That is were it went wrong. When I added the example names and ran the installation with these accounts it all worked like a charm. I guess there are 'hardcoded' references in the installation.

Next step is to test it and then get it on the internet and use it in some R&D projects.

by Edward van Steenderen | 2 comment(s)
DTS hangs after reading/writing 1000 rows
Tue, Apr 5 2005 10:36 PM
At one of my current projects I use DTS to get data in and out a Sql Server 2000 database. Because some of these processes take a while I show the progress messages of DTS in the StatusBar of my C# winapp.
I basically used the sample in a support article to build the handling of DTS from my client.
With some of the processes I experienced suddenly that DTS hangs after the first 1000 rows.
 
Because the OnProgressMessage event of a DTS Package fires every 1000 rows I guessed it had something to do with that event. So I turned off my handler for the event and that solved the problem.
Looking more into it I discovered that these problems occur when the event fires at a high frequency (many per second). In my case most of the importing or exporting to flat ASCII files happened (too) fast.
 
Despite the fact I spent quite a bit of time on it I found no better solution than the workaround. In my situation the workaround was sufficient but I'm still curious. So if someone knows a better solution please leave a remark.
by Edward van Steenderen | with no comments
"No files were found to look in.Find was stopped in progress." in VS 2003
Mon, Jan 31 2005 9:50 PM

To find my way around in someone else's sources the Find Files functionality is an essential facility in Visual Studio. Especially since it does not have conditional breaking like Visual Studio 6 has. (I refuse to get over that.) Imagine my almost hurtful eyebrow frowning when Find Files suddenly stopped working at a fixed time project.
 
I still don't know why it happened but with every Find attempt the result box immediately showed the message "No files were found to look in.Find was stopped in progress." Ever experienced this oddity?
On the internet I found posts stating even reinstalling Visual Studio didn't fix this. It took me a while to find the solution to it (a few months ago). Via another reference I found the solution on gotdotnet.com.
Because a solution to this problem deserves more attention I'm making a link to it here: http://www.gotdotnet.com/Community/MessageBoard/Thread.aspx?id=217037&Page=1#218705
 
It also deserves a nomination in the problem solving category Spin around on your chair 3 times, clap your hands twice and then press... because the solution is to press Control + Scroll Lock and all is fixed.
Maybe it's a easter egg gone bad...

by Edward van Steenderen | 7 comment(s)

Search

This Blog

Community

Archives

Syndication

Email Notifications