VS90SP1-KB974558-x86 fails to install on Win Server 2003

Locked VS90SP1-KB974558-x86 fails to install on Win Server 2003

  • Monday, July 30, 2012 8:47 AM
     
     

    I am getting a fatal error when I try to install the forward compatibility patch onto our TFS 2008 server. I have already installed TFS2008 Service Pack 1 with no issues. I am installing this to deal with some migration issues occurring when using theTFS Integration Platform.


    The main point of interested is highlighted in the logfile with multiple entries as below: 


    "DEBUG: Error 2746:  Transform RTM.1 invalid for package C:\WINDOWS\Installer\19f6bd98.msi. Expected product {B997F79D-9A2B-3FEF-87E0-FF63E8F0D9D0}, found product {35ED788B-DA6B-3373-BB2B-A68C149EA81A}."


    The error appears to be caused by a hotfix with a product key of {35ED788B-DA6B-3373-BB2B-A68C149EA81A}

    Does anyone have a clue how to resolve this?

    I also have a very verbose logfile which is over 60K characters, so I cannot post it here.

    UPDATE: there is a further error:

    Executing workflow 'Quiesce ATDT'...
    Stopping Windows Service 'TFSServerScheduler'...
    Stopping Windows Service 'CoverAn'...
    Stopping Windows Service 'W3SVC'...
    Starting Windows Service 'W3SVC'...
    Disabling SQL Jobs for databases TFSActivityLogging,TFSBuild,TFSIntegration,TFSVersionControl,TFSWorkItemTracking,TFSWorkItemTrackingAttachments,TFSWarehouse
    Blocking service account from accessing database TFSActivityLogging
    Blocking service account from accessing database TFSBuild
    Blocking service account from accessing database TFSIntegration
    Microsoft.TeamFoundation.Admin.TFSQuiesce.RunningWithServiceAccountException: You cannot run setup using the Team Foundation Service Account DOTCOM\LK46
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.ChangeServiceAccountState(XPathNavigator workflow, String action, String dbName)
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.ProcessSqlDatabaseElement(XPathNavigator workflow, String action, String dbName)
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.ExecuteWorkflowStep(XPathNavigator workflow, String action, String nameAttribute)
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.ExecuteWorkflowStepWithRetry(XPathNavigator workflow, String action, String nameAttribute)
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.RunWorkflow(String workflowName)

    Executing workflow 'Unquiesce ATDT'...
    Enabling SQL Jobs.
    Unblocking service account from accessing database TFSActivityLogging
    Unblocking service account from accessing database TFSBuild
    Unblocking service account from accessing database TFSIntegration
    Unblocking service account from accessing database TFSVersionControl
    Unblocking service account from accessing database TFSWorkItemTracking
    Unblocking service account from accessing database TFSWorkItemTrackingAttachments
    Unblocking service account from accessing database TFSWarehouse
    Stopping Windows Service 'W3SVC'...
    Starting Windows Service 'W3SVC'...
    Starting Windows Service 'TFSServerScheduler'...
    Starting Windows Service 'CoverAn'...

    Workflow 'Quiesce ATDT' failed! ExitCode = 8000.
    07/29/12 11:41:34 DDSet_Status: Process returned 8000
    07/29/12 11:41:34 DDSet_Status: Found the matching error code  for return value '8000' and it is: '29206'
    07/29/12 11:41:34 DDSet_Error:  8000

    I found that the account I was using to install the patch was a member of the "Service Accounts" group on the TFS App Server.

    Would this cause my issue?


    • Edited by zedhex1 Monday, July 30, 2012 10:56 AM
    •  

All Replies

  • Tuesday, July 31, 2012 7:04 AM
    Moderator
     
     

    Hi zedhex,

    Thank you for your post.

    VS90SP1-KB974558-x86 is an update for VS 2008 SP1, let vs 2008 could connect TFS 2010. But, from the question, your TFS version is TFS 2008. Apply this update is not suitable. If I have misunderstood anything, please free feel to let me know.

    Regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us

  • Tuesday, July 31, 2012 8:08 AM
     
     

    Apparently you have misunderstood my post. I am applying the Forward Compatibility patch to a TFS2008 server in order that it can be used as a source for a TFS Integration Platform migration. The server has the VS2008 Team Explorer SP1 installed on it, and now it needs the compatibility patch so that it can connect to a TFS2010 server. So I am using the patch to connect to a TFS2010 server from a TeamExplorer 2008 instance.

    The compatibility patch has two main components: an update for Team Explorer and an update for TFS2008 server. This is standard practice when migrating code from a Tfs2008 server to a TFS2010 server using TIP. I already have two other TFS2008 servers correctly configured in this way, so the patch should definitely install.

    See this post:

    "VersionControlMigrationException: Compatibility Error: Successful migration requires a server version of 2005 SP1 or later - AGAIN"


    • Edited by zedhex1 Wednesday, August 01, 2012 2:10 PM
    •  
  • Wednesday, August 01, 2012 6:20 AM
     
     

    Hi Zedhex,

    By "The compatibility patch has two main components: an update for Team Explorer and an update for TFS2008 server", how do you know that? VS90SP1-KB974558-x86.exe is update for VS 2008 SP1, make VS 2008 team explorer could work with TFS 2010.

  • Wednesday, August 01, 2012 1:10 PM
     
     

    because you can see it in the logs:

    Patch (c:\00cecf5670dabc4a5c\VS90SP1-KB974558.msp) install succeeded on product
    (Microsoft Visual Studio 2008 Team Explorer - ENU).

    Patch (c:\00cecf5670dabc4a5c\VS90SP1-KB974558.msp) install failed on product
    (Microsoft Visual Studio 2008 Team Foundation Server - ENU).

    I have installed this on two other TFS2008 servers without incident. The snippet above is from the TFS2008 server section of the log. The msi runs perfectly happily until the:

    Workflow 'Quiesce ATDT' failed! ExitCode = 8000.
    07/29/12 11:41:34 DDSet_Status: Process returned 8000
    07/29/12 11:41:34 DDSet_Status: Found the matching error code  for return value '8000' and it is: '29206'
    07/29/12 11:41:34 DDSet_Error:  8000

    section occurs. I also have another log from a successful install which succeeds past this point. Like I said: this is standard practice when migrating from Tfs2008 to TFS2010 using TIP.

  • Friday, August 03, 2012 7:30 AM
    Moderator
     
     

    Hi zedhex1,

    Please use Best Practices Analyzer tool to verify whether the TFSEXECROLE and TFSADMINROLE database roles exist and are assigned to the following databases:
    TfsActivityLogging
    TfsBuild
    TfsVersionControl
    TfsWarehouse
    TfsWorkItemTracking
    TfsWorkItemTrackingAttachments
    TfsIntegration

    The problem may be TFS Service Account DOTCOM\LK46 is not a member of the TFSEXECROLE database role. To add a service account as a member role.
    1. Open SQL Server Management Studio.
    2. Expand Databases, and then expand the database that the message specifies (for example, TfsActivityLogging).
    3. Expand Security, expand Database Roles, and then expand Roles.
    4. Right-click TFSEXECROLE, and then click Properties.
    5. In the Database Role - TFSEXECROLE dialog box, click Add.
    6. In the Select Database User or Role dialog box, click Browse.
    7. In the Browse for Objects dialog box, select the check box for the service account for Team Foundation Server check box, and then click OK twice.
    8. In Members of this role, verify that the service account for Team Foundation Server is listed, and then click OK.

    Regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us

  • Thursday, August 09, 2012 10:41 AM
     
     
    Why has this been marked as an answer? - I have run the BPA and I have no issues - the TFSEXECROLE and TFSADMINROLE  roles are fine, but the patch still fails to install.
    • Edited by zedhex1 Thursday, August 09, 2012 10:41 AM
    •  
  • Friday, August 10, 2012 6:53 AM
     
     

    Hi zedhex1,

    any update information, there is no more information to cathe the issue.