If you are having a problem with the TFS 2010 MOSS Configuration tool crashing when you try to configure MOSS 2010, you may be able to use this workaround to get it to work.
The problem is a CLR .NET 3.5 bug (fixed in newer versions of .Net Framework), but it doesn’t always appear and it’s not clear to me exactly what causes the problem. The first time I tired to use the tool, it worked flawlessly. But then when I rolled back my vm to capture my efforts on video, I couldn’t get the tool to work. Exact same environment, but this time with 100% more frustration. Fortunately for me, I have access to the developer who created the tool. Fortunately for you, I love to share.
The developer who figured out this workaround is a really smart person who doesn’t mind rolling up her sleeves for some old fashioned troubleshooting. You perform the procedure on the computer running MOSS 2010 (this workaround is only for MOSS 2010). What will the workaround do to your server? Good question. The ngen tool (step 3) creates native images of code to improve the performance of managed applications. When you uninstall the image, you’re forcing the tool to compile the code at run time. You won’t notice the performance hit.
TFS 2010 MOSS Configuration Tool Workaround for MOSS 2010
- Open a CMD prompt with administrative privilege.
- Cd to this location*: %systemdrive%\Windows\Microsoft.NET\Framework64\v2.0.50727
- Run this command: ngen uninstall “Microsoft.SqlServer.OlapEnum, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91”
*If you’re on a 32 bit machine, you may have to adjust the location to “Framework” instead of “Framework64”.