www.jayntguru.com » upgrade

TFS 2008 to TFS 2010 Install notes

jayntguru — Sun, 13 Mar 2011 17:10:43 +0000

Recently (about 5 minutes ago) I did an upgrade in production of our Team Foundation 2008 server to Team Foundation 2010. I had a dry run that worked well but of course on the real thing I had a couple of issues. Here are some notes.

TFS requires sysadmin on the new SQL server, it wants to create/drop databases like crazy
TFS previous to 2010 required sharepoint to be installed, with 2010 it’s just an option, you can add it later.
To clean up from an earlier install (failed, test run, etc.) you can run this command (see the gotcha at the end!)

C:\Program Files\Microsoft Team Foundation Server 2010\Tools>tfsconfig setup /un
install:all

The steps are

Install TFS 2010
Configure TFS 2010 (this creates databases)
Backup your old TFS databases (all of them)
Restore your old TFS databases to your new sql instance
Run the TFS import command from command line. It should look like this:

C:\Program Files\Microsoft Team Foundation Server 2010\Tools>Tfsconfig import /s
qlinstance:server\instance /collectionName:imported /confirmed

Once you do this, you should be good to go

We had an error when trying to install on production because it kept finding information from the previous one. Apparently the tsconfig /setup uninstall:all doesn’t really uninstall all! There were extended database properties left over that we had to delete manually. Until we did this, we received this error:

TF30046: The instance information does not match.

There are very useful logfiles located in:

C:\ProgramData\Microsoft\Team Foundation\Server Configuration\Logs

In order to get visual studio 2005 to connect to TFS 2010, you have to install in this order:

Visual studio 2005
Tfs plugin for vs 2005
Vs 2005 sp1
Vs 2005 vista compatibility update (run windows update)
Vs 2005 TFS 2010 update
Then you enter the full URL in the server name field: http://tfs2010_server:8080/tfs
If it tells you that you can’t put in the “/” and such, it means you installed in the wrong order.

In order to get visual studio 2008 to connect to TFS 2010, you have to:

Install vs 2008
Install vs 2008 sp1
Install vs 2008 TFS compatibility pack
Enter servername as: http://tfs2010_server:8080/tfs

That’s all I have for now. After all the devs come in and hit this tomorrow I may have some more updates (but I hope not!).

scom missing performance counters

jayntguru — Fri, 07 Jan 2011 20:02:57 +0000

I recently had to make some changes to my scom test environment server. It’s a single virtual machine with scom, sql, ssrs, the works on it. Despite what one would think, it has performed well with about 30 agents. Recently I added about that many more and it pushed up the ram to the 4gb max that I had given it. When I added more I realized I had used 2008 x32 for the OS (oops) and was not able to see the extra ram. After some research I found that I could do an upgrade from 2008 standard to enterprise, which is what I did. Afterwards, scom wouldn’t run because the SDK service would not start. This is the event log message.

Log Name:      Operations Manager
Source:        OpsMgr SDK Service
Date:          1/7/2011 2:25:48 PM
Event ID:      26380
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:

Description:
The System Center Operations Manager SDK Service failed due to an unhandled exception.
The service will attempt to restart.
Exception:

System.TypeInitializationException: The type initializer for ‘Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess’ threw an exception. —> System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.Initialize()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager.CreateCounter(String categoryName, String counterName)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager.CreateCounters(PerformanceCounterCategoryDescriptor categoryInfo)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager..ctor(String instanceName, PerformanceCounterCategoryDescriptor categoryInfo)
   at Microsoft.EnterpriseManagement.Mom.Internal.SingleInstancePerformanceCounterCategoryDescriptor.CreateManager()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkPerfCounterManager..ctor()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess..cctor()
   — End of inner exception stack trace —
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.Initialize()
   at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)
   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">


    26380
    2
    0
    0×80000000000000

    10025424
    Operations Manager
    INFMGT52.accessgeneral.com


    System.TypeInitializationException: The type initializer for ‘Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess’ threw an exception. —> System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.Initialize()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager.CreateCounter(String categoryName, String counterName)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager.CreateCounters(PerformanceCounterCategoryDescriptor categoryInfo)
   at Microsoft.EnterpriseManagement.Mom.Internal.PerformanceCounterCategoryDescriptor.SingleInstancePerformanceCounterCategoryManager..ctor(String instanceName, PerformanceCounterCategoryDescriptor categoryInfo)
   at Microsoft.EnterpriseManagement.Mom.Internal.SingleInstancePerformanceCounterCategoryDescriptor.CreateManager()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkPerfCounterManager..ctor()
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess..cctor()
   — End of inner exception stack trace —
   at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.SdkDataAccess.Initialize()
   at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SdkSubService.AsyncStartCallback(Object notUsed)
   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

After some research I found this article from Microsoft that contains instructions on how to fix this problem.

upgrading from w7 rc to rtm

jayntguru — Sat, 31 Oct 2009 19:08:56 +0000

I usually don’t do upgrades but in this case upgrading from the release candidate to the full release of W7 didn’t seem like the worst idea. I used the instructions at this link and it worked.