Team System Developer Center > Visual Studio Team System Forums > Team Foundation Server - Setup > Error installing SP1, KB949786 could not be installed. Error code 1603.
Ask a questionAsk a question
 

AnswerError installing SP1, KB949786 could not be installed. Error code 1603.

  • Monday, August 11, 2008 9:58 PMJuan Zamudio Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi all, i tried to install the SP1 on team foundation server and i get this error

    KB949786 could not be installed. Error code 1603.

    The App tier is Windows Server 2003 32 bits, and the data tier is SQL server 2005, if you need more info let me know, thanks.



    Juan Zamudio

Answers

  • Tuesday, August 12, 2008 2:06 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    It looks to me like the old account is still your RS Datasources account. I would recommend running TfsAdminUtil

     changeaccount for both the RS and the service user. It might fail because of the VS SP1 patch (i.e. there are now mismatched binaries) in which case we'll have to manually update the AppPools, Services, and RS account. The first two can be done through MMC and the latter through the site http://mst-tfs2k8:80/Reports

     

    Cheers,

    Adam

  • Tuesday, August 12, 2008 2:15 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    You may also have to update the TFS registration data. Use the "TfsReg.exe /export" command to see if there are any references to the old account. If so, replace them with the new account and then re-import the new settings.

     

    Cheers,

    Adam

     

  • Tuesday, August 12, 2008 2:40 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Looks like we're getting closer, at least. The other places it could be getting the old name from are Windows Services or the msiproperty.ini file under %programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\ (or a subfolder thereof). Can you see if it exist in either place?

     

    Cheers,

    Adam

     

  • Wednesday, August 13, 2008 7:58 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    From your text log: "You cannot run setup using the Team Foundation Service Account SFAM\admautobuild"

     

    Please run the TFS SP1 as a different TFS Administrator account. It looks like it doesn't want you to run it as the service account.

     

    Cheers,

    Adam

All Replies

  • Monday, August 11, 2008 10:17 PMJuan Zamudio Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I forgot, is the RTM version that failed.
  • Tuesday, August 12, 2008 6:20 AMDavid YackMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We had the same error occur - not sure what's causing it yet

     

  • Tuesday, August 12, 2008 7:45 AMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm getting the very same error. Luckily the failed installation doesn't break anything.

    Single server installation on Windows Server 2008 Standard w/ Sql Server 2005.
  • Tuesday, August 12, 2008 10:00 AMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     Jesper Hvid wrote:
    I'm getting the very same error. Luckily the failed installation doesn't break anything.

    Single server installation on Windows Server 2008 Standard w/ Sql Server 2005.


    Of course I spoke too soon. After installing Visual Studio 2008 SP1 on the TFS server the installation is now broken and all the TFS Web Services are generating HTTP 500 errors.

    I'm guessing shared assemblies have been updated and now the non-SP1 TFS 2008 server cannot load assemblies. Also, even better: the VS2008 SP1 cannot be uninstalled (I certainly cannot see how) so the server is effectively dead. This is just not good enough!

    TF53010: The following error has occurred in a Team Foundation component or extension:
    Date (UTC): 12-08-2008 09:49:18
    Machine: MST-TFS2K8
    Application Domain: /LM/W3SVC/1879938360/ROOT/Services-1-128630081558232113
    Assembly: Microsoft.TeamFoundation.Server, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
    Process Details:
      Process Name: w3wp
      Process Id: 3964
      Thread Id: 4072
      Account name: GLOBETEAM\ms-tfs2k8service

    Detailed Message: TF53013: A crash report is being prepared for Microsoft. The following information is included in that report:
    System Values
    OS Version Information=Microsoft Windows NT 6.0.6001 Service Pack 1
    CLR Version Information=2.0.50727.3053
    Machine Name=MST-TFS2K8 Processor Count=2
    Working Set=27090944
    System Directory=C:\Windows\system32
    Process Values
    ExitCode=0
    Interactive=False
    Has Shutdown Started=False
    Process Environment Variables
    Path = C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
    TEMP = C:\Windows\TEMP
    PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    USERDOMAIN = GLOBETEAM
    PROCESSOR_ARCHITECTURE = x86
    SystemDrive = C:
    APPDATA = C:\Windows\system32\config\systemprofile\AppData\Roaming
    windir = C:\Windows
    LOCALAPPDATA = C:\Windows\system32\config\systemprofile\AppData\Local
    TMP = C:\Windows\TEMP
    NUMBER_OF_PROCESSORS = 2
    USERPROFILE = C:\Windows\system32\config\systemprofile
    ProgramFiles = C:\Program Files
    FP_NO_HOST_CHECK = NO
    COMPUTERNAME = MST-TFS2K8
    APP_POOL_ID = Microsoft Team Foundation Server Application Pool
    USERNAME = MST-TFS2K8$
    PUBLIC = C:\Users\Public
    PROCESSOR_IDENTIFIER = x86 Family 15 Model 2 Stepping 9, GenuineIntel
    SystemRoot = C:\Windows
    ComSpec = C:\Windows\system32\cmd.exe
    CommonProgramFiles = C:\Program Files\Common Files
    PROCESSOR_LEVEL = 15
    PROCESSOR_REVISION = 0209
    lib = C:\Program Files\SQLXML 4.0\bin\
    ALLUSERSPROFILE = C:\ProgramData
    VS90COMNTOOLS = C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\
    ProgramData = C:\ProgramData
    OS = Windows_NT

    Request Details
    Url=https://ms-tfs01.globeteam.com:8081/Services/v1.0/ServerStatus.asmx [method = POST]
    User Agent=Team Foundation (devenv.exe, 9.0.30729.1)
    Headers=Content-Length=354&Content-Type=text%2fxml%3b+charset%3dutf-8&Accept-Encoding=gzip%2cgzip%2cgzip&Accept-Language=da-DK&Authorization=Negotiate+TlRMTVNTUAADAAAAGAAYAHwAAAAwATABlAAAABIAEgBYAAAABAAEAGoAAAAOAA4AbgAAABAAEADEAQAANYKI4gYAcRcAAAAPoiIOlLlWeIw%2fsOvg2xGpKWcAbABvAGIAZQB0AGUAYQBtAGoAaABKAEUASABYADMAMAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJqajdNYTIv6uPsHGrkvNpsBAQAAAAAAAPbeh65g%2fMgBX0Q0f9P94tAAAAAAAgASAEcATABPAEIARQBUAEUAQQBNAAEAFABNAFMAVAAtAFQARgBTADIASwA4AAQAIABhAGQALgBnAGwAbwBiAGUAdABlAGEAbQAuAGMAbwBtAAMANgBNAFMAVAAtAFQARgBTADIASwA4AC4AYQBkAC4AZwBsAG8AYgBlAHQAZQBhAG0ALgBjAG8AbQAFACAAYQBkAC4AZwBsAG8AYgBlAHQAZQBhAG0ALgBjAG8AbQAHAAgA9t6HrmD8yAEGAAQAAgAAAAgAMAAwAAAAAAAAAAAAAAAAMAAAvSBXbaiJW8jq52WlZBoVWILwHGKYOYoRLF2FZ8ZX9mQAAAAAAAAAAAAAAAACq%2bghBM6QnstWVB%2ftgA82&Expect=100-continue&Host=ms-tfs01.globeteam.com%3a8081&User-Agent=Team+Foundation+(devenv.exe%2c+9.0.30729.1)&X-TFS-Version=1.0.0.0&X-TFS-Session=ff1adf95-09ce-4a73-bce1-080fee8affe4&SOAPAction=%22http%3a%2f%2fschemas.microsoft.com%2fTeamFoundation%2f2005%2f06%2fServices%2fServerStatus%2f03%2fCheckAuthentication%22
    Path=/Services/v1.0/ServerStatus.asmx
    Local Request=False
    User Host Address=10.10.1.119
    User=GLOBETEAM\jh [auth = Negotiate]

    Application Provided Information
    Team Foundation Application Information
    Event Log Source = TFS Services
    Configured Team Foundation Server = http://MST-TFS2K8:8080
    License Type = EnterpriseLicense
    Server Culture = en-US
    Activity Logging Name = Integration
    Component Name = CS
    Initialized = No
    Requests Processed = 0


    Exception: TypeInitializationException
    Message: The type initializer for 'Microsoft.TeamFoundation.Server.IntegrationResourceComponent' threw an exception.
    Stack Trace:
       at Microsoft.TeamFoundation.Server.IntegrationResourceComponent.RegisterExceptions()
       at Microsoft.TeamFoundation.Server.Global.Initialize()
       at Microsoft.TeamFoundation.Server.TeamFoundationApplication.Init()
    Inner Exception Details
    Exception: ReflectionTypeLoadException
    Message: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    Stack Trace:
       at System.Reflection.Module._GetTypesInternal(StackCrawlMark& stackMark)
       at System.Reflection.Assembly.GetTypes()
       at Microsoft.TeamFoundation.Server.SqlResourceComponent.RegisterExceptions(Assembly assembly)
       at Microsoft.TeamFoundation.Server.IntegrationResourceComponent.RegisterExceptions()
       at Microsoft.TeamFoundation.Server.IntegrationResourceComponent..cctor()

    Application Domain Information
    Assembly Name=mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll
    Assembly File Version:
    File:             C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll
    InternalName:     mscorlib.dll
    OriginalFilename: mscorlib.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  Microsoft Common Language Runtime Class Library
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll
    InternalName:     System.Web.dll
    OriginalFilename: System.Web.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  System.Web.dll
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll
    InternalName:     System.dll
    OriginalFilename: System.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  .NET Framework
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
    InternalName:     System.Configuration.dll
    OriginalFilename: System.Configuration.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  System.Configuration.dll
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll
    InternalName:     System.Xml.dll
    OriginalFilename: System.Xml.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  .NET Framework
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=Microsoft.JScript, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=8.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\Microsoft.JScript\8.0.0.0__b03f5f7f11d50a3a\Microsoft.JScript.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\Microsoft.JScript\8.0.0.0__b03f5f7f11d50a3a\Microsoft.JScript.dll
    InternalName:     Microsoft.JScript.dll
    OriginalFilename: Microsoft.JScript.dll
    FileVersion:      8.0.50727.3053
    FileDescription:  Microsoft.JScript.dll
    Product:          Microsoft (R) Visual Studio (R) 2005
    ProductVersion:   8.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=CppCodeProvider, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=8.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\CppCodeProvider\8.0.0.0__b03f5f7f11d50a3a\CppCodeProvider.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\CppCodeProvider\8.0.0.0__b03f5f7f11d50a3a\CppCodeProvider.dll
    InternalName:     CppCodeProvider.dll
    OriginalFilename: CppCodeProvider.dll
    FileVersion:      8.0.50727.813
    FileDescription:  CppCodeProvider.dll
    Product:          Microsoft (R) Visual Studio (R) 2005
    ProductVersion:   8.0.50727.813
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=App_global.asax.veuigsvl, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
    Assembly CLR Version=v2.0.50727
    Assembly Version=0.0.0.0
    Assembly Location=C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\services\52c8ecbf\1045ef73\App_global.asax.veuigsvl.dll
    Assembly File Version:
    File:             C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\services\52c8ecbf\1045ef73\App_global.asax.veuigsvl.dll
    InternalName:     App_global.asax.veuigsvl.dll
    OriginalFilename: App_global.asax.veuigsvl.dll
    FileVersion:      0.0.0.0
    FileDescription:  
    Product:         
    ProductVersion:   0.0.0.0
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=Microsoft.TeamFoundation.Server, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=9.0.0.0
    Assembly Location=C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\services\52c8ecbf\1045ef73\assembly\dl3\7751d3cd\603ea9a2_d822c801\Microsoft.TeamFoundation.Server.DLL
    Assembly File Version:
    File:             C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\services\52c8ecbf\1045ef73\assembly\dl3\7751d3cd\603ea9a2_d822c801\Microsoft.TeamFoundation.Server.DLL
    InternalName:     Microsoft.TeamFoundation.Server.dll
    OriginalFilename: Microsoft.TeamFoundation.Server.dll
    FileVersion:      9.0.21022.8
    FileDescription:  Microsoft.TeamFoundation.Server.dll
    Product:          Microsoft (R) Visual Studio (R) 2008
    ProductVersion:   9.0.21022.8
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=Microsoft.TeamFoundation.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=9.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation.Common\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.Common.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation.Common\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.Common.dll
    InternalName:     Microsoft.TeamFoundation.Common.dll
    OriginalFilename: Microsoft.TeamFoundation.Common.dll
    FileVersion:      9.0.30729.1
    FileDescription:  Microsoft.TeamFoundation.Common.dll
    Product:          Microsoft (R) Visual Studio (R) 2008
    ProductVersion:   9.0.30729.1
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=Microsoft.TeamFoundation, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=9.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.dll
    InternalName:     Microsoft.TeamFoundation.dll
    OriginalFilename: Microsoft.TeamFoundation.dll
    FileVersion:      9.0.30729.1
    FileDescription:  Microsoft.TeamFoundation.dll
    Product:          Microsoft (R) Visual Studio (R) 2008
    ProductVersion:   9.0.30729.1
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=Microsoft.TeamFoundation.Common.Library, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=9.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation.Common.Library\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.Common.Library.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_32\Microsoft.TeamFoundation.Common.Library\9.0.0.0__b03f5f7f11d50a3a\Microsoft.TeamFoundation.Common.Library.dll
    InternalName:     Microsoft.TeamFoundation.Common.Library.dll
    OriginalFilename: Microsoft.TeamFoundation.Common.Library.dll
    FileVersion:      9.0.30729.1
    FileDescription:  Microsoft.TeamFoundation.Common.Library.dll
    Product:          Microsoft (R) Visual Studio (R) 2008
    ProductVersion:   9.0.30729.1
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         Language Neutral

    Assembly Name=System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Assembly CLR Version=v2.0.50727
    Assembly Version=2.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\System.Web.Mobile\2.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll
    Assembly File Version:
    File:             C:\Windows\assembly\GAC_MSIL\System.Web.Mobile\2.0.0.0__b03f5f7f11d50a3a\System.Web.Mobile.dll
    InternalName:     System.Web.Mobile.dll
    OriginalFilename: System.Web.Mobile.dll
    FileVersion:      2.0.50727.3053 (netfxsp.050727-3000)
    FileDescription:  System.Web.Mobile.dll
    Product:          Microsoft® .NET Framework
    ProductVersion:   2.0.50727.3053
    Debug:            False
    Patched:          False
    PreRelease:       False
    PrivateBuild:     False
    SpecialBuild:     False
    Language:         English (United States)

    Assembly Name=System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Assembly CLR Version=v2.0.50727
    Assembly Version=3.0.0.0
    Assembly Location=C:\Windows\assembly\GAC_MSIL\System.ServiceModel\3.0.0.0__b77a5c561934e089\Sy
  • Tuesday, August 12, 2008 10:15 AMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     Jesper Hvid wrote:
    I'm getting the very same error. Luckily the failed installation doesn't break anything.

    Single server installation on Windows Server 2008 Standard w/ Sql Server 2005.


    Update: The problem seems to be caused by the fact that the Visual Studio 2008 installation on the server is now Service Pack 1 (RTM) and the server isn't. This apparently breaks the TFS installation completely. I've no idea how to get out of this since I cannot uninstall Service Pack 1 for Visual Studio 2008 and I cannot install Service Pack 1 for TFS 2008.
  • Tuesday, August 12, 2008 12:58 PMJason BarileMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    This is due to the fact that the client and server bits on the machine are sharing the same assemblies. By installing SP1 for Visual Studio 2008 on the server machine but not TFS 2008 SP1, you're in an unsupported "mixed mode" configuration.

     

    We need to figure out why you can't upgrade to SP1.  That's really the only way to make this work - have both at the same service pack (or not) level.

     

    Did this server ever have any pre-release/beta bits installed?

  • Tuesday, August 12, 2008 1:01 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     Jason Barile - MSFT wrote:

     

    This is due to the fact that the client and server bits on the machine are sharing the same assemblies. By installing SP1 for Visual Studio 2008 on the server machine but not TFS 2008 SP1, you're in an unsupported "mixed mode" configuration.

     

    Can you elaborate on why you can't uninstall VS2008 SP1 or install TFS 2008 SP1?  That's really the only way to make this work - have both at the same service pack (or not) level.



    That's what I guessed...

    I can't uninstall VS2008 SP1 since it doesn't appear in add/remove programs.
    I can't install TFS 2008 SP1 because of error 1603. The same error as the poster.
  • Tuesday, August 12, 2008 1:03 PMCRathjen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Yes, the latest problem is due to the mixed SP level of the machine - the client and server have to be at the same service pack level.

     

    So, the 'fix' is to get the Server SP installed. Can you attach the logs from the 1603 error initially reported? The SP installer should link to the logs, but if you don't have that handy, look for something like "Microsoft Visual Studio 2008 Service Pack 1 2008...MSI0.txt" in either %temp% or the parent folder (%temp%\..). If there's more than one such file (quite likely at this point), look for the one with the 1603 error message.

     

     

  • Tuesday, August 12, 2008 1:05 PMCRathjen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I don't think we want to go down the 'uninstall VS 2008 SP1' path unless we have to, but it SHOULD be appearing in Add/Remove Programs.

     

    Do you have the 'show updates' box at the top of the dialog checked?

     

  • Tuesday, August 12, 2008 1:06 PMJason BarileMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    VS 2008 SP1 should appear when you select "Show Updates" in Add/Remove programs.  Are you not seeing it even in that case?

     

    We need to see your setup logs to pursue the 1603 error if you can supply them.

  • Tuesday, August 12, 2008 1:08 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     CRathjen - MSFT wrote:

     

    Yes, the latest problem is due to the mixed SP level of the machine - the client and server have to be at the same service pack level.

     

    So, the 'fix' is to get the Server SP installed. Can you attach the logs from the 1603 error initially reported? The SP installer should link to the logs, but if you don't have that handy, look for something like "Microsoft Visual Studio 2008 Service Pack 1 2008...MSI0.txt" in either %temp% or the parent folder (%temp%\..). If there's more than one such file (quite likely at this point), look for the one with the 1603 error message.

     

     



    I've got the log file for the TFS2008 setup. It's huge. Do you want the full file posted in here?

    Edit: Can't post the full file since it's > 50.000 characters. I've put it here:

    https://jollerbarn.dk/msilog.zip

     

  • Tuesday, August 12, 2008 1:18 PMCRathjen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Also, anyone seeing these problems:

     

    Anything else you can provide - the error, the logs, and more details about your configurations - will help us diagnose the problem(s).

     

    Can you report what version, edition, and service pack level of SQL you're using? E.g. is it SQL 2005 Enterprise SP2, or SQL 2005 Standard SP1, or 2005 DataCenter sp2, etc. The SP level isn't supposed to matter but I'm looking for more possible patterns.

     

    Also indicate whether or not you had SP1 beta (of the client or server) on any of the machines at some point - while we can get you to SP1 final in that case, there are some steps that must be followed particularly for the client SP1 beta.

     

  • Tuesday, August 12, 2008 1:27 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    It's a single server installation running on Windows Server 2008 x86 Standard Service Pack 1. The operating system language is English.

     

    SQL Server 2005 Standard (no service packs).

    Select @@version =

    Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)

    Feb 9 2007 22:47:07

    Copyright (c) 1988-2005 Microsoft Corporation

    Standard Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

     

    I've not had any beta service packs on the server at any time. I'm aware of the procedures to uninstall SP1 beta on the clients. I did this on my workstation, but I don't think that's what making the TFS web services crash. Other workstations running 2008 non SP1 are also making the web services crash.

     

    Is there anything else you need?

  • Tuesday, August 12, 2008 1:35 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    From the error log on your site:
    08/12/08 15:04:38 DDSet_Status: --- STATUS: Failed cracking name while parsing account: MST-TFS2K8\tfsservice (DS_NAME_ERROR_NOT_FOUND)
    08/12/08 15:04:38 DDSet_Error: *** ERROR: Unhandled exception causing exit: No mapping between account names and security IDs was done

    Does the account "MST-TFS2K8\tfsservice" still exist? Has it been disabled or has its password expired?

     

    Also, there should be an HTML log from around the same time in the %TEMP% folder. Can you share that, as well?

     

    Thanks-

    Adam

  • Tuesday, August 12, 2008 1:39 PMCRathjen - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Also, is the user running the SP install an admin?

  • Tuesday, August 12, 2008 1:43 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    That user does not exist anymore. The user running the application pool is a domain user with user name:

    globeteam\ms-tfs2k8service

     

    Are we looking at an database inconsistency in TFS accounts? It certainly didn't stop it from working before :-)

     

    HTML log:

    https://jollerbarn.dk/htmllog.zip

    The user running the install is a local administrator, yes.

  • Tuesday, August 12, 2008 2:00 PMMahmoud Abdel-Fattah - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Another possible reason why you may hit this error may be network problems or AD problems that prevented the correct resolution of the account. If you try the account and find that it is working, you can try re-running the patch installation and see if you still hit the same error.

  • Tuesday, August 12, 2008 2:02 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The user in the log definitely does not exist anymore. It's a local user.. and I honestly can't remember if I was at one time running with local accounts for the app pools. I might have. Now, however, it's a domain account. The domain user can be resolved, he exists and his password is not expired.

  • Tuesday, August 12, 2008 2:06 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    It looks to me like the old account is still your RS Datasources account. I would recommend running TfsAdminUtil

     changeaccount for both the RS and the service user. It might fail because of the VS SP1 patch (i.e. there are now mismatched binaries) in which case we'll have to manually update the AppPools, Services, and RS account. The first two can be done through MMC and the latter through the site http://mst-tfs2k8:80/Reports

     

    Cheers,

    Adam

  • Tuesday, August 12, 2008 2:15 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    You may also have to update the TFS registration data. Use the "TfsReg.exe /export" command to see if there are any references to the old account. If so, replace them with the new account and then re-import the new settings.

     

    Cheers,

    Adam

     

  • Tuesday, August 12, 2008 2:17 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    At http://localhost/reports the incorrect local user was configured. I changed this to the domain user on both the report sources.

     

    The application pools are already running with the correct domain user. The SP1 update still fails exactly as before. Is there anything else I can try? The log is still reporting that it can't crack the old "local" account name. Where else is it registered?

  • Tuesday, August 12, 2008 2:21 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I believe the last location is in the TFS Registration information. I found that reference after my previous post so didn't include it originally - sorry for the omission. The correct way to update it is to use the TfsReg.exe tool with /export, modify the usernames in the xml it outputs, and then re-import those entries with TfsReg.exe.

     

    Hope this helps-

     

    Cheers,

    Adam

     

  • Tuesday, August 12, 2008 2:23 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Currently struggling with getting tfsreg.exe to work. I'm running the following command:

    "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\tfsreg.exe" /export exported.xml ms-tfs2k8

     

    However, it can't connect to SQL:

    TFSReg - Team Foundation Server registration tool
    Copyright (c) Microsoft Corporation.  All rights reserved.

    A network-related or instance-specific error occurred while establishing a conne
    ction to SQL Server. The server was not found or was not accessible. Verify that
     the instance name is correct and that SQL Server is configured to allow remote
    connections. (provider: Named Pipes Provider, error: 40 - Could not open a conne
    ction to SQL Server)

     

    The SQL server is running just fine.. I've connected to it with SQL Server Management Studio.

  • Tuesday, August 12, 2008 2:25 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I thought your servername was MST-TFS2K8?

     

    On the AT itself, you can also just use "localhost".

     

    Cheers,

    Adam

  • Tuesday, August 12, 2008 2:28 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    You're right. I'm an idiot :-)

     

    It worked with the right machine name.. I'm updating the configuration file now. Will import it afterwards and let you know if the setup completes.

  • Tuesday, August 12, 2008 2:35 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Right, now I'm getting the following error:

     

    08/12/08 16:28:57 DDSet_Status: --- STATUS: Found TfsServiceAccount=globeteam\ms-tfs2k8service <-- correct account
    08/12/08 16:28:57 DDSet_Status: --- STATUS: Failed cracking name while parsing account: tfsservice  (DS_NAME_ERROR_NOT_FOUND) <-- where does this name come from?? It doesn't appear in the exported reg file??

  • Tuesday, August 12, 2008 2:40 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Looks like we're getting closer, at least. The other places it could be getting the old name from are Windows Services or the msiproperty.ini file under %programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\ (or a subfolder thereof). Can you see if it exist in either place?

     

    Cheers,

    Adam

     

  • Tuesday, August 12, 2008 2:51 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Plot thickens.

     

    This file contained old service names: C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\TF Setup\eleadservices.xml - updated it

     

    This file contained old service names:

    C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Microsoft Visual Studio 2008 Team Foundation Server - ENU\msiproperty.ini - updated it. However, setup is still reporting this:

     

     

    08/12/08 16:28:57 DDSet_Status: --- STATUS: Found TfsServiceAccount=globeteam\ms-tfs2k8service <-- correct account
    08/12/08 16:28:57 DDSet_Status: --- STATUS: Failed cracking name while parsing account: tfsservice  (DS_NAME_ERROR_NOT_FOUND) <-- where does this name come from?? It doesn't appear in the exported reg file??
  • Tuesday, August 12, 2008 2:56 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Have you checked the Services running on your machine? In particular, look for Coverage Analysis and Team Foundation Server Scheduler.

     

    Cheers,

    Adam

  • Tuesday, August 12, 2008 3:03 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Both services checked and updated.

     

    I'm currently running setup, and I now have a progressbar! :-) Haven't had that before.. will keep you updated.

     

    P.S.

    How in the world can the log on identity of a stopped service halt a service pack? :-)

  • Tuesday, August 12, 2008 3:07 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Service pack installed. Everything is back up again.

     

    Thanks for your help guys.

     

    I've now learned two things:

    1) How to change the logon identity of TFS service accounts

    2) Why not to change the logon identity of TFS service accounts

     

    Rgds.

    Jesper Hvid

  • Tuesday, August 12, 2008 4:19 PMJuan Zamudio Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I've reading all the post and my problem is a little bit different, i looked in the log and found this


    TFSActivityLogging,TFSBuild,TFSIntegration,TFSVersionControl,TFSWorkItemTracking,TFSWorkItemTrackingAttachments,TFSWarehouse
    SQL Error #1
    SQL Message: CREATE TABLE permission denied in database 'master'.
    SQL LineNumber: 13
    SQL Source: .Net SqlClient Data Provider
    SQL Procedure:

    System.Data.SqlClient.SqlException: CREATE TABLE permission denied in database 'master'.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.TeamFoundation.Admin.TFSQuiesce.Quiescer.DisableJobs(XPathNavigator workflow)
       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)
    Exception Data:
    Key: HelpLink.ProdName, Value: Microsoft SQL Server
    Key: HelpLink.ProdVer, Value: 09.00.3054
    Key: HelpLink.EvtSrc, Value: MSSQLServer
    Key: HelpLink.EvtID, Value: 262
    Key: HelpLink.BaseHelpUrl, Value: http://go.microsoft.com/fwlink
    Key: HelpLink.LinkId, Value: 20476

    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 = 9000.
    08/12/08 10:34:11 DDSet_Status: Process returned 9000
    08/12/08 10:34:11 DDSet_Status: Found the matching error code  for return value '9000' and it is: '29207'
    08/12/08 10:34:11 DDSet_Error:  9000
    08/12/08 10:34:11 DDSet_CARetVal: 29207
    08/12/08 10:34:11 DDSet_Status: QuietExec returned 29207
    08/12/08 10:34:11 DDSet_Exit: QuietExec ended


    I'm using the domain user i used to install TFS 5 months a go, but I guess the DBA change the permissions in SQL Server, I will check the permissions on the data tier and try again, thanks.


    Juan Zamudio

  • Tuesday, August 12, 2008 4:40 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The best way to change the account is with the TfsAdminUtil changeaccount command. This should update all of the necessary AppPools, tables, services, and files.

     

    Basically, what's happening is that GetCurrentTfsProperties is checking all of the parts of the system to see what state they're in and verify that they are valid. The error message could certainly be improved, though one other tool to try is the TFS BPA (Best Practice Analyzer) that checks the state of a currently running system. If you hit issues like this in the future, I'd recommend starting there.

     

    Cheers,

    Adam

     

  • Tuesday, August 12, 2008 4:41 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     Juan Zamudio wrote:
    System.Data.SqlClient.SqlException: CREATE TABLE permission denied in database 'master'.

     

    Are you running as an account that's a SQL Administrator?

     

    Cheers,

    Adam

  • Tuesday, August 12, 2008 5:53 PMJesper Hvid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Excellent, I'll do that.

    Again, thanks for the assistance.
  • Tuesday, August 12, 2008 7:41 PMJuan Zamudio Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Apparently yes, they changed the permissions on the server for that user, i tried again with the the service account but I'm getting this error:

    08/12/08 11:47:18 DDSet_Error: *** ERROR: Failed during check for TfsIntegration database: The SELECT permission was denied on the object 'tbl_service_interface', database 'TfsIntegration', schema 'dbo'. 08/12/08 11:47:18
    DDSet_Status: Process exited with exit code: 101

    it is OK that the service account doesn't have select permissions on the objects??, if that's true guess I'm gonna need another account to install the service pack.

    I also run the Best Practices Analyzer  with the service account, this are the results (critical results)

    The Windows SharePoint Services custom template "VSTS_MSFAgile" was not found on.
    (this template is installed but under the language 1033, i can create agile projects from the client with no errors, but for some reason the tool is not finding the template)

    The Windows SharePoint Services custom template "VSTS_MSF_CMMI" was not found on.
    Same as above, these are the results for the installed templates
    stsadm -o enumtemplates
    VSTS_MSF_CMMI - Language: 1033 - Site Template: _GLOBAL_#1 - Template Id: 1
    VSTS_MSFAgile - Language: 1033 - Site Template: _GLOBAL_#0 - Template Id: 1

    The Web service call "SharePointProductsandTechnologies Sites.GetSiteTemplate" at _vti_bin/Sites.asmx failed. Error message: "There is an error in XML document (0, 0)."
    I have no idea how to fix this one, and when i click on "Tell me more about this issue and how to resolve it" it just open the folder with the log of the scan.


    The directory on AT cd21vids1 referenced by '\\cd21vids1\C$\Documents and Settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys' has non-default permissions. They should be Everyone - Write, Read, Synchronize; and Administrators - FullControl.
    I tried to fix this one and get bite on the arse, i changed the permissions but then i had issues with the web service, getting exceptions like this "Keyset does not exist (type CryptographicException)"



  • Wednesday, August 13, 2008 7:48 PMJeff HunsakerMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I'm experiencing this on a single-server, Win2k3 RC2, SQL 2005 Standard SP2. Log files. I did not have SP1 beta bits installed but embarassingly, I believe I accidentally installed the VS2008 SP1 instead of the TFS SP1 (was installing on lots of clients first...clicked the wrong link). I've attempted to uninstall VS2008 SP1 but nothing appears under Add/Remove.

     

  • Wednesday, August 13, 2008 7:58 PMAdam Singer - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    From your text log: "You cannot run setup using the Team Foundation Service Account SFAM\admautobuild"

     

    Please run the TFS SP1 as a different TFS Administrator account. It looks like it doesn't want you to run it as the service account.

     

    Cheers,

    Adam

  • Wednesday, August 13, 2008 8:50 PMJeff HunsakerMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Brilliant! That resolved the issue (running the installation as another administrator). Thanks!