More things to know about installing SP1

I’ll let this post be a running list of issues that I hear about as people try installing SP1. So far I’ve heard mostly good things about the installation process but a few problems as well. Here’s a few things to know:

1) If you get a Windows Update prompt to reboot during SP1 installation, ignore it (don’t reboot). Wait until after the SP1 installation completes and then reboot.

2) If you have a prerelease of the Team System for Database Development GDR (that supports SQL 2008) installed, you will need to uninstall and 2reinstall it after upgrading to SP1.

3) Apparently you can’t create the admin mode/slipstream TFS installer when running on a Vista 64-bit OS. I suspect it won’t work on any 64-bit OS but the customer report I saw said it was 64-bit Vista but it worked on 32-bit Vista. Of course TFS itself can only be installed on Windows 2003 or Windows 2008 and the application tier still only supports 32 bit. Yes, I know, I know. We’ve gotten tons of feedback about how bad it is not supporting 64-bit. That’s coming in our Rosario release.

That’s a little longer than what I have heard is "typical" – not sure why. However, the install is not fast no matter how you slice it. Over an hour is pretty normal.

Brian

10 years ago

Tom

I had an issue installing TFS SP1. Kept getting a unique key failure when trying to create an index on the dbo.Constants table in one of the database tables. There were somehow 4-5 entries with the same username and RemovedDate (or DateRemoved, I am at home now and don’t remember the exact name) which caused the setup to have a fatal error and left TFS in an unusable state until I figured out what was going on by looking at the msi log file. To resolve the issue, I simply changed the minute value of each duplicate entry to make them unique and then re-ran the installation. Not sure if this is a known bug or what but you may want to look into it.

Will there be a seperate installation for the Team Explorer. We have a team where there is a need for installing the Team Explorer to get access to work items, sources, etc. but member do not work with Visual Studio for coding etc. Installing a 800mb sp1 where the original installation is 387mb seems overkill.

Other thing: when installing I only had 600mb free space. Installation could only start when I had 2.3gb available. After freeing up until 2.3gb I ended up with having 1.7gb free after installation. Is the 2.3gb really needed?

Long installs might be the result of the prompt for the original installation disk "popping under" the install progress dialog box.

10 years ago

GuyO

After getting SP1 up and running – I went to add the infragistics Silverlight controls to the toolbox — as soon as the openfile dialog box posts, VS2008 vanishes with two separate errors appearing in the event log….NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (6AFA0F92) (0)

Mac, the only thing you are suggesting that would worry me at all is Team Build SP1 against a pre-SP1 server. It will probably work but all of our testing is always done using matched versions of TFS and Team build. You’ll be blazing a bit of new territory in that respect.

We have confirmed the bug and it is in the UI framework in the .NET Framework. The team is still assessing the issue. If this issue is a real problem for you, you could contact customer service and request a hotfix. That will initiate a process internally. We don’t honor all hotfix requests but our goal is to honor at least 90% of them.

Once SP1 for TFS is installed, in a dual-server config, what’s the proper upgrade order for SQL Server? Does the reporting server on the AT need to be upgraded first; does the database server need to go first; does it matter?

I wound up doing that (but with RS first since the SQL docs said it was a supported config).

I ran into issues with the repair though with WMI exceptions. I use three FQDN’s (wss. for sharepoint/rs, tfs. for tfs and tswa. for web access). The tfrsconfig command kept failing, so I wound up renaming it and putting a dummy do-nothing program in its place. I also had an issue with CreateDS which I solved the same way. After the repair finished, I restored the original commands and ran used a modified command line that was in the msi log but pointing to the correct name…

I actually skipped tfrsconfig since it’s already setup right, but I did re-run CreateDS as it created a new datasource name from what was there.

Now things seem to work with the exception of TSWA. TSWA’s Reports tab shows an error that it didn’t get the response it was expecting.

Mac, running an SP1 build agent/server against an RTM TFS 2008 server will work correctly. Also, a TFS SP1 server will work with an RTM build agent/server. We tested it both ways.

Buck

10 years ago

Rick

I see GuyO already posted a similiar issue but an FYI…I just installed vs 2008 sp1 and am attempting to add the wpf datagrid control to my toolbox but when doing so, VS immediately closes down and I also get the 2 errors in my event viewer:

For me, VS2008 SP1 crashes and I get exactly the same errors as Rick in the event log when the WPF designer loads (i.e. when openíng a XAML file). The designer worked at first but now it crashes every time, even after reboot.

Any solution/workaround for this problem yet?

Btw, I’m running on Win 2003.

10 years ago

Mattias

Now I’ve tried to uninstall and reinstall SP1 and also to remove all thirp-party add-ons (suggested somewhere else) but to no effect. Only thing left now, I guess, is to remove SP1 and wait for a resolution to the problem.

10 years ago

Jim Duncan

I read (somwhere, can’t find it again) that if you have both the client and app tier on the same machine, you need to install the VS SP1 first and THEN the TFS SP1…

I did a ‘slipstreamed’ install of TFS w/ SP1 but now I need to install Team Explorer on the TFS box.

What’s going to happen if I install Team Explorer on there and then VS SP1? Will it break? Is there a way to do a ‘slipstreamed’ install of Team Explorer w/ VS SP1?

10 years ago

snuchia@statsoft.com

This is a VS/VC/PSDK issue, not a TS issue, but everybody talking about plans to upgrade their build servers should take a chill pill:

Issue 2.3.1.13 in the release notes is the tip of an iceberg, the manifests for any DLL or EXE built against the CRT and/or MFC import libs have the RTM version number embedded in them, leading to a failure when the built program is deployed. Connect issue 362504.

One can’t help wondering what role native code scenarios play in the VS test plans. One also wonders, perhaps knowing it to be "just one of those things", how the ATL problem came to be written up in the release notes without somebody thinking to check all the other import libraries. But perpaps the root causes are unrelated. And by "unrelated" I mean related only through the cultural antipathy of the VS team toward native code tools and toward we who depend on those tools.

Actually it probably isn’t fair to characterize it as antipathy, it’s probably just apathy. But even that is a shallow analysis: I’ve come to believe that thinking of VS as an application rather than a mission-critical systems program (when it is really both) has allowed the developers and the QA apparatus to focus on feature churn to the exclusion of core/legacy functionality and the interactions among features. Having had a lot of time to meditate on this, my considered opinion is that this imbalance is probably the root cause of this deplorable situation. It just feels better to cast aspersions on the morals and motives of individuals I’ve never met for some reason. Probably because their decisions have caused me a great deal of inconvenience and embarassment of late.

Oh well, that’s my $0.02 worth.

Why am I posting here? Because the light is on and someone is home here. They shoot the messenger from behind hard cover over in the other camp.

10 years ago

Tom

VERY SLOW INSTALL…

The progress bar stayed at 100% for over an hour on a dual core processor system.

This does not give us a good feeling about the quality of this product!

10 years ago

Östen Petersson

i get the same fatal execution error today as the above when i click f5…

we have wpf in our windowsapp – but there is another error msg before :

– System

– Provider

[ Name] Application Error

– EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

– TimeCreated

[ SystemTime] 2008-08-22T11:25:12.000Z

EventRecordID 17269

Channel Application

Computer [removed}

Security

– EventData

devenv.exe

9.0.30729.1

488f2b50

unknown

0.0.0.0

00000000

c0000005

330001ca

348

01c9043c88a15c93

10 years ago

snuchia@statsoft.com

UPdateing my rant about the library dependencies: I’ve updated the connect ticket. There are two real problems, neither is a show-stopper.

One, the rules that determine how DLLs are chosen at runtime are extremely complex and there is very poor visibilitiy into them. Depends.exe, the best tool available as far as I can tell, has a bug and a design deficiency. The bug is what caused me to chase down this rabbit hole in the first place.

But that’s a good thing, because otherwise it would have been a while before I noticed that our build outputs showed dependencies on older versions of the libraries. That means that our cusomters could end up running our program against the wrong libraries, creating a huge regression risk.

I’m still trying to undestand how all the moving parts interrelate but I’m moving forward again, will try once again to get an automated build going.

It’s been a long strange trip. TFS source control is a huge win. Everything else has been a huge disappointment.

10 years ago

Will Dieterich

One the .NET Runtime version 2.0.50727.3053 error uninstall powercommand tools for visual studio.

Here’s one that could be a symptom of installing SP1 on the development machine while the server remains at RTM:

I’m trying to do a large merge. I get a few hundred conflicts and spend a couple of days, between other tasks, resolving them. All resolved now. No intervening checkins on either branch. But when I try to check in my thousands of pending changes I get the checkin progress dialog briefly, followed by the conflict resolution dialog. It’s list is empty and it has the "(!) All conflicts resolved but no files checked in due to initial conflicts." message across the top.

I’ve tried exiting and restarting the IDE, no joy. I’ve merged many similar batches along this same merge path prior to installing SP1. I’m hoping to upgrade the server soon but right now I’m full time banging my head against our build automation conundrum.

I think I’ll try backing SP1 out of the machine that has the merge pending and see what happens.

10 years ago

snuchia@statsoft.com

Nah, that didn’t help. I tried the checkin from the command line and got the warnings: two files which had been deleted in the target branch were silently pended as merge, edit. I undid them and re-executed the merge, it pended them silently again.

That was with SP1 deinstalled from VS TeamDev and Team Explorer but I left the Framework installed. Anyway, the checkin completed once I identified the problem files.

I checked, there was nothing in the source control Output window; no indication from inside the IDE as to what was really wrong.

Both of these were files changed earlier in the source branch and I must have skipped them in previous merges. I just don’t recall having seen it act this way; the empty conflict resolution dialog seems new.

10 years ago

hutty

I have the same problem as Rick and Guy. Where can I get the hotfix for the net runtime error? I have been trying to install VS2008 for the last two weeks.

swn1, I’m sorry you’ve had so many issues. I am passing on your various pieces of feedback to all of the right people in DevDiv. I’ll let you know what I hear back.

Brian

10 years ago

Michal

Hello swn1,

sorry about problems during the merge operation.

The files resurrected during the merge are definitely confusing, it would be nice to do history on both the source and target item, to see what changes need to be propagated.

The empty Resolve Dialog is disturbing. How did you perform checkin initially – I understand it was inside VS – was it from the Pending Changes Toolwindow, Solution Explorer or Source Control Explorer? Am I correct, that when you did checkin from command line, resolve dialog contained conflicts? It would indicate bug in code that displays Resolve dialog inside VS.

10 years ago

hutty

Thanks Brian for the feedback.

10 years ago

snuchia@statsoft.com

Michal –

TFS source control gets easily confused when renames, undeletes, and other namespace operations are composed, with each other or with edits. I’ve found that I sometimes have no choice but to check in a preliminary changeset to conform the target namespace to the source before attempting a merge.

A mathematician would recognize this as a broken "group" problem and provide some high-level analysis to help resolve it. I’ve seen very recently some blog text from somebody on the team who understands the math — he was talking about SCC namespaces in a way that actually made sense — so you’ve got the resources in-house.

I always use the Pending Changes window to launch checkins; it was what I discovered first and it gives me the most confidence / best chance at not messing it up. I multitask a lot and way too frequently have changes belonging to different tasks pending.

A way to partition pending changes into groups (proto-changesets) would be a great feature.

When I did the checkin from the command line it did not give me a conflict dialog at all, if I remember correctly. But that’s not reliable, I may have dismissed it. In any case, there was console output including text in yellow that described the underlying problem and identified the two files that were involved. With that clue I was able to work around it.

As I mentioned, that diagnostic output did not appear in the Output window within VS.

Hope this helps,

-swn

10 years ago

StevenIBSI

Just completed the sp1 install.

First did vs2008 sp1 and that took 45 min.

Then did the TFS 2008 sp1 and that took about 25 min. The progress bar reached 100% at least several minutes before the installation completed so be patient.

After the install the team service was not running. Restarted it and then had to enable the build agent as well.

Thanks for the feedback swn1. We know there are issues with conflict resolution and management. We are in process of reworking that for our next release and I think you will find both to be much better.

The request for multiple pending changesets has been on our backlog for a while. I’m not sure when we will get to it but we won’t forget it.

swn1, Sorry it took so long but here’s a response to your VC issue. I can’t take credit for it – the VC team put it together for me 🙂

Firstly, thanks very much for taking the time to post and highlight this issue. It is true that there was recently a change to the default behavior of binding to versions of the CRT/MFC/etc. I would like to point out that this was not an accidental change but rather one that the VC team took after a lot of customer feedback and internal evaluation. Changing default behavior is never an easy choice, because of the “surprise” that it creates. I could go into lots of detail about the pros and cons of the situation but it is probably best if I just point you to the articles that the VC team posted around this decision:

As you can see from the articles there is also a way to specify your behavior using a set of defines if you prefer the original behavior, again I will leave it to the articles to provide the complete set of options. I also see that the resolution on the Connect site was probably frustrating, just hearing that something is “By Design” is not always a great customer experience – sorry if that added to your annoyance with this issue. As always we really value your feedback on our decisions, if you have any follow up comments or questions please feel free to post again, either here or if you prefer to go straight to the horse’s mouth, over on the VC team blog. Since the original VC Blog article is now closed for comments, you could use this more recent SP1 article.

Brian

10 years ago

snuchia@statsoft.com

I’ve been having extreme problems with Team Build and I wanted to put up some yellow tape around the big open hole so nobody else fall in it:

With the build server and SCC server as VMs on the same big VM server, MSBuild and TFSBuildService crash (seemingly) randomly. I rebuilt my build server as a stand-alone machine and all is well: the clouds parted and birds began to sing.

After more than a year of messing with it I finally have a reliable automated build system that operates on my source tree as-is.

There’s a long list of other configuration and install sequence differences between the working server and all the failed incarnations but another user on the forum reported a similar finding and I tried an awful lot of permutations before giving up on the VM. I’m fairly sure it will turn out to be the zero-latency networking exposing a race in the TFS client code common to those two programs.

I’m the PM for Team Build and I’d like to get some details on the configuration you were using when you were seeing spurious failures. I think you were running the application tier and the build service in separate VMs on the same host. Is that right? Could you provide some specifics on the configuration?

* What virtual machine manager were you using?

* What software was running on each VM?

* How much memory, hard disk space, etc. was allocated for each VM?

* Were there any event log entries coinciding with the spurious failures?

If you’d like to contact me directly, you can initiate a conversation through my MSDN blog at:

I had checked in some delete files the previous day. The next day I got latest from SC. Made some changes. Tried to checkin and the deleted changes from the previous day showed up again, alsong with my new changes. With several attempts to checkin failing with the following: "All conflicts resolved but no files checked in due to initial conflicts." And no conflicts listed.

To resolve I had a co-worker checkin a changeset. I got latest on that changeset. Performed Undo operations on the deletes. Got latest again. Checked in successfully.

I first encountered this issue well after I had installed PowerCommands (which appears to be the cause of the issue) but directly after installing StyleCop. I believe the StyleCop install made a path or config change that precipitated the issue.

10 years ago

michael

i got this problem when install azure sdk, but after reinstall .net framework 3.5 sp1 then it’s OK