Skip to main content

TFS 2018–Installation failure

Didn’t had my best day yesterday as I was trying to rollout Team Foundation Server 2018 at a customer.

When we tried to start the installation, it failed while installing the .NET Framework 4.7 with a not-so-clear error message “Cannot find object or property”.

clip_image002

Inside the setup log, we found a little more information:

[1930:1564][2018-08-16T09:54:05]i319: Applied execute package: netfxfullredist, result: 0x80092004, restart: None

[1930:1564][2018-08-16T09:54:05]e000: Error 0x80092004: Failed to execute EXE package.

[1AC0:00A8][2018-08-16T09:54:05]i351: Removing cached package: netfxfullredist, from path: C:\ProgramData\Package Cache\76054141A492BA307595250BDA05AD4E0694CDC3\

[1AC0:00A8][2018-08-16T09:54:05]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2b3bf919-c7d8-41a9-bff7-734a9750b00c}, resume: None, restart: None, disable resume: No

[1AC0:00A8][2018-08-16T09:54:05]i330: Removed bundle dependency provider: {2b3bf919-c7d8-41a9-bff7-734a9750b00c}

[1AC0:00A8][2018-08-16T09:54:05]i352: Removing cached bundle: {2b3bf919-c7d8-41a9-bff7-734a9750b00c}, from path: C:\ProgramData\Package Cache\{2b3bf919-c7d8-41a9-bff7-734a9750b00c}\

[1AC0:00A8][2018-08-16T09:54:05]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2b3bf919-c7d8-41a9-bff7-734a9750b00c}, resume: None, restart initiated: No, disable resume: No

[1930:1564][2018-08-16T09:54:05]i000: MUX:  Apply Complete: Disk Space Used in bytes for Installation:  MaxAppDrive: 0  MaxSysDrive: 2208534528  AppDrive: 0  SysDrive: 1619668992

[1930:1564][2018-08-16T09:54:05]i000: MUX:  Free Disk Space after install:  SystemDrive C:\ 32985960448 bytes  AppDrive C:\ 32985960448 bytes

[1930:1564][2018-08-16T09:54:05]i000: MUX:  Go to Finished page.

[1930:1564][2018-08-16T09:54:05]i000: MUX:  Watson Bucketting Parameters

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P1 - tfs_trial

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P2 - 16.131.27701.1

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P3 - 16.131.27701

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P4 - Install

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P5 - netfxfullredist

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P6 - Install

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P7 - 0x80092004

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P8 -

[1930:1564][2018-08-16T09:54:05]i000: MUX:  P9 -

[1930:1564][2018-08-16T09:54:05]i399: Apply complete, result: 0x80092004, restart: None, ba requested restart:  No

It is clearly a problem with the installation of the .NET Framework and searching for the error code 0x80092004 gave some results.

Unfortunately every solution we found and tried didn’t solve the problem. Sad smile

To be continued…

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
OSZAR »