Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataDog agent installation failed on windows #3840

Open
minzhuo opened this issue May 2, 2019 · 9 comments
Open

DataDog agent installation failed on windows #3840

minzhuo opened this issue May 2, 2019 · 9 comments

Comments

@minzhuo
Copy link

minzhuo commented May 2, 2019

I tried to use the latest datadog installer on a windows machine and at the end it does finish with "setup wizard ended prematurely" error.

I tried the .exe and .msi both way. didn't work.

Output of the info page

This is from exe
[3820:2A44][2019-05-02T11:29:00]i001: Burn v3.11.0.1701, Windows v6.1 (Build 7601: Service Pack 1), path: C:\Users\U\AppData\Local\Temp\{805363BE-2DC0-4D55-BB43-8E76193612DF}\.cr\ddagent-cli-latest.exe
[3820:2A44][2019-05-02T11:29:00]i009: Command Line: '-burn.clean.room=C:\Users\U\Downloads\ddagent-cli-latest.exe -burn.filehandle.attached=272 -burn.filehandle.self=276'
[3820:2A44][2019-05-02T11:29:00]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\U\Downloads\ddagent-cli-latest.exe'
[3820:2A44][2019-05-02T11:29:00]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\U\Downloads\'
[3820:2A44][2019-05-02T11:29:00]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\U\AppData\Local\Temp\Datadog_Agent_Installer_20190502112900.log'
[3820:2A44][2019-05-02T11:29:00]i000: Setting string variable 'WixBundleName' to value 'Datadog Agent Installer'
[3820:2A44][2019-05-02T11:29:00]i000: Setting string variable 'WixBundleManufacturer' to value 'Datadog Inc.'
[3820:2D54][2019-05-02T11:29:00]i000: Setting version variable 'WixBundleFileVersion' to value '5.32.2.1'
[3820:2A44][2019-05-02T11:29:00]i100: Detect begin, 2 packages
[3820:2A44][2019-05-02T11:29:00]i101: Detected package: upgrade_helper.exe, state: Absent, cached: None
[3820:2A44][2019-05-02T11:29:00]i101: Detected package: datadog_agent_5.32.2_1_x86_64.msi, state: Absent, cached: None
[3820:2A44][2019-05-02T11:29:00]i199: Detect complete, result: 0x0
[3820:2D54][2019-05-02T11:29:03]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[3820:2A44][2019-05-02T11:29:03]i200: Plan begin, 2 packages, action: Install
[3820:2A44][2019-05-02T11:29:03]w321: Skipping dependency registration on package with no dependency providers: upgrade_helper.exe
[3820:2A44][2019-05-02T11:29:03]i000: Setting string variable 'UninstallRelatedProductsLogPath' to value 'C:\Users\U\AppData\Local\Temp\Datadog_Agent_Installer_20190502112900_000_upgrade_helper.exe.log'
[3820:2A44][2019-05-02T11:29:03]i000: Setting string variable 'WixBundleRollbackLog_datadog_agent_5.32.2_1_x86_64.msi' to value 'C:\Users\U\AppData\Local\Temp\Datadog_Agent_Installer_20190502112900_001_datadog_agent_5.32.2_1_x86_64.msi_rollback.log'
[3820:2A44][2019-05-02T11:29:03]i000: Setting string variable 'WixBundleLog_datadog_agent_5.32.2_1_x86_64.msi' to value 'C:\Users\U\AppData\Local\Temp\Datadog_Agent_Installer_20190502112900_001_datadog_agent_5.32.2_1_x86_64.msi.log'
[3820:2A44][2019-05-02T11:29:03]i201: Planned package: upgrade_helper.exe, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: Yes, uncache: No, dependency: None
[3820:2A44][2019-05-02T11:29:03]i201: Planned package: datadog_agent_5.32.2_1_x86_64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[3820:2A44][2019-05-02T11:29:03]i299: Plan complete, result: 0x0
[3820:2A44][2019-05-02T11:29:03]i300: Apply begin
[3820:2A44][2019-05-02T11:29:03]i010: Launching elevated engine process.
[3820:2A44][2019-05-02T11:29:09]i011: Launched elevated engine process.
[3820:2A44][2019-05-02T11:29:10]i012: Connected to elevated engine.
[3F58:3EF0][2019-05-02T11:29:10]i358: Pausing automatic updates.
[3F58:3EF0][2019-05-02T11:29:10]w308: Automatic updates could not be paused due to error: 0x80240025. Continuing...
[3F58:3EF0][2019-05-02T11:29:10]i360: Creating a system restore point.
[3F58:3EF0][2019-05-02T11:29:26]i361: Created a system restore point.
[3F58:3EF0][2019-05-02T11:29:26]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{978a0a68-619b-43f4-be0e-0b1d23c9d627}, options: 0x7, disable resume: No
[3F58:3EF0][2019-05-02T11:29:27]i000: Caching bundle from: 'C:\Users\U\AppData\Local\Temp\{BA605171-E991-4580-B4CD-B479ABFDAFB6}\.be\datadog-agent-5.32.2-1-x86_64.exe' to: 'C:\ProgramData\Package Cache\{978a0a68-619b-43f4-be0e-0b1d23c9d627}\datadog-agent-5.32.2-1-x86_64.exe'
[3F58:3EF0][2019-05-02T11:29:27]i320: Registering bundle dependency provider: {978a0a68-619b-43f4-be0e-0b1d23c9d627}, version: 5.32.2.1
[3F58:3EF0][2019-05-02T11:29:27]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{978a0a68-619b-43f4-be0e-0b1d23c9d627}, resume: Active, restart initiated: No, disable resume: No
[3F58:1CC4][2019-05-02T11:29:28]i305: Verified acquired payload: upgrade_helper.exe at path: C:\ProgramData\Package Cache\.unverified\upgrade_helper.exe, moving to: C:\ProgramData\Package Cache\60A05E127B16E6DB058520EC3B62AFB996299B36\upgrade-helper.exe.
[3F58:1CC4][2019-05-02T11:29:29]i305: Verified acquired payload: datadog_agent_5.32.2_1_x86_64.msi at path: C:\ProgramData\Package Cache\.unverified\datadog_agent_5.32.2_1_x86_64.msi, moving to: C:\ProgramData\Package Cache\{176836B9-0B31-43C5-8B39-384B8DD8D925}v5.32.2.1\datadog-agent-5.32.2-1-x86_64.msi.
[3F58:3EF0][2019-05-02T11:29:29]i301: Applying execute package: upgrade_helper.exe, action: Install, path: C:\ProgramData\Package Cache\60A05E127B16E6DB058520EC3B62AFB996299B36\upgrade-helper.exe, arguments: '"C:\ProgramData\Package Cache\60A05E127B16E6DB058520EC3B62AFB996299B36\upgrade-helper.exe" -oldcode={82210ed1-bbe4-4051-aa15-002ea31dde15} -newcode={0c50421b-aefb-4f15-a809-7af256d608a5}'
[3820:2A44][2019-05-02T11:29:29]i319: Applied execute package: upgrade_helper.exe, result: 0x0, restart: None
[3F58:3EF0][2019-05-02T11:29:29]i323: Registering package dependency provider: {176836B9-0B31-43C5-8B39-384B8DD8D925}, version: 5.32.2.1, package: datadog_agent_5.32.2_1_x86_64.msi
[3F58:3EF0][2019-05-02T11:29:29]i301: Applying execute package: datadog_agent_5.32.2_1_x86_64.msi, action: Install, path: C:\ProgramData\Package Cache\{176836B9-0B31-43C5-8B39-384B8DD8D925}v5.32.2.1\datadog-agent-5.32.2-1-x86_64.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" APIKEY="" TAGS="" HOSTNAME="" NOTUPGRADE="" PROXY_HOST="" PROXY_PORT="" PROXY_USER="" PROXY_PASSWORD=""'
[3F58:3EF0][2019-05-02T11:34:50]e000: Error 0x80070643: Failed to install MSI package.
[3F58:3EF0][2019-05-02T11:34:50]e000: Error 0x80070643: Failed to execute MSI package.
[3820:2A44][2019-05-02T11:34:50]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[3820:2A44][2019-05-02T11:34:50]i319: Applied execute package: datadog_agent_5.32.2_1_x86_64.msi, result: 0x80070643, restart: None
[3820:2A44][2019-05-02T11:34:50]e000: Error 0x80070643: Failed to execute MSI package.
[3F58:3EF0][2019-05-02T11:34:50]i318: Skipped rollback of package: datadog_agent_5.32.2_1_x86_64.msi, action: Uninstall, already: Absent
[3820:2A44][2019-05-02T11:34:50]i319: Applied rollback package: datadog_agent_5.32.2_1_x86_64.msi, result: 0x0, restart: None
[3F58:3EF0][2019-05-02T11:34:50]i329: Removed package dependency provider: {176836B9-0B31-43C5-8B39-384B8DD8D925}, package: datadog_agent_5.32.2_1_x86_64.msi
[3F58:3EF0][2019-05-02T11:34:50]i351: Removing cached package: datadog_agent_5.32.2_1_x86_64.msi, from path: C:\ProgramData\Package Cache\{176836B9-0B31-43C5-8B39-384B8DD8D925}v5.32.2.1\
[3F58:3EF0][2019-05-02T11:34:50]i351: Removing cached package: upgrade_helper.exe, from path: C:\ProgramData\Package Cache\60A05E127B16E6DB058520EC3B62AFB996299B36\
[3F58:3EF0][2019-05-02T11:34:50]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{978a0a68-619b-43f4-be0e-0b1d23c9d627}, resume: None, restart: None, disable resume: No
[3F58:3EF0][2019-05-02T11:34:50]i330: Removed bundle dependency provider: {978a0a68-619b-43f4-be0e-0b1d23c9d627}
[3F58:3EF0][2019-05-02T11:34:50]i352: Removing cached bundle: {978a0a68-619b-43f4-be0e-0b1d23c9d627}, from path: C:\ProgramData\Package Cache\{978a0a68-619b-43f4-be0e-0b1d23c9d627}\
[3F58:3EF0][2019-05-02T11:34:50]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{978a0a68-619b-43f4-be0e-0b1d23c9d627}, resume: None, restart initiated: No, disable resume: No
[3820:2A44][2019-05-02T11:34:50]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

Additional environment details (Operating System, Cloud provider, etc):
windows 7 (64bit)

Steps to reproduce the issue:

  1. Download the latest the MSI, and install
@cvkrreddy
Copy link

I tried MSI on windows server 2016 failed on AWS but EXE succeeded

@olivielpeau
Copy link
Member

@minzhuo @cvkrreddy thanks for reporting these issues.

Since these issues seem quite specific to your environments, please contact our support team and send them your logs.

Thanks!

@cornebester
Copy link

MSI on windows server 2016 also fail on Azure 2016 image (CIS hardened) but EXE succeeded

@augustz
Copy link

augustz commented Jul 20, 2019

Same issue in Windows Server 2016 on-prem. Couldn't get MSI to work. Couldn't find exe to try.

@brophyjustin
Copy link

If you are installing the agent on a Domain Controller, a service account must be created in Active Directory and the following parameters must be passed during the install DDAGENTUSER_NAME & DDAGENTUSER_PASSWORD.

See here --> https://docs.datadoghq.com/agent/faq/windows-agent-ddagent-user/#installation-in-a-domain-environment

@mattinmelbourne
Copy link

this fails for myself as well. As per Datadog Docs:
Note: When upgrading the Datadog Agent on a domain controller or host where the user has supplied a username for the Agent, you need to supply the <DDAGENTUSER_NAME> but not the <DDAGENTUSER_PASSWORD>:
I have a domain user named mydomain\ddagentuser
does this user need to have any permissions set on the domain controller before installing? ie. user rights assignment?
note: this fails on server 2012 R2, 2016 and 2019

@ayooki
Copy link

ayooki commented Nov 17, 2020

@Phatix I encountered this problem but I was able to install it with a normal domain user account. No further permissions needed.

@darin-sai
Copy link

We seemed to be encountering something similar when installing onto our domain controller. Every attempt to install was rolling back.

Finally, we tried what @privojustin suggested and created the service account in AD manually first, then passing the username and password parameters into the msiexec command. It looks like the installer could NOT create the account automatically, as implied by the docs, but if it already existed, then it worked.

We then tried to reset the service account password. We changed the PW in AD, and then went to services.msc and edited the Log On user for the Datdog services. This appears to have been successful.

@testworksau
Copy link

I had the same issue and error log file contents, on two machines, attempting an upgrade from agent versions:

  • 7.23.1 on Windows Server 2019 (10.0 Build 17763)
  • 7.19.2 on Windows Server 2012 R2 (6.3 Build 9600)

My issue was caused by a misinterpretation, on my behalf, of the Upgrading instructions in the upgrading tab:
https://docs.datadoghq.com/agent/basic_agent_usage/windows/?tab=upgrading

I had downloaded using the EXE installer link:
https://s3.amazonaws.com/ddagent-windows-stable/ddagent-cli-latest.exe

instead of using the Datadog Agent installer link in the Gui tab:
https://docs.datadoghq.com/agent/basic_agent_usage/windows/?tab=gui

which links to:
https://s3.amazonaws.com/ddagent-windows-stable/datadog-agent-7-latest.amd64.msi

When running the latter installer, my upgrades worked correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants