search

chocolatey / choco

Chocolatey - the package manager for Windows
https://chocolatey.org
Other
10.24k stars 897 forks source link

Chocolatey ExitCode 60008 #3038

Closed weiner22 closed 1 year ago

weiner22 commented 1 year ago

Checklist

What You Are Seeing?

I´m getting ExitCode 60008 during package installation on FIPS enabled Domain Controller.

What is Expected?

Install nuget packages well.

How Did You Get This To Happen?

choco installl -y -source https://internalnuget.server

System Details

Installed Packages

Trying packages from different vendors - I can install them out of FIPS enabled DC well. Even on other FIPS enabled DC outside domain.
Agents
-Microsoft Monitoring Agent
-Cortex XDR
-Guardicore
-Splunk Universal Forwarder

Output Log

Already described here 
https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/issues/753

Additional Context

No response

pauby commented 1 year ago

Can you :

The exit code is being reported by the installer and Chocolatey is reporting it back. So on the surface this looks to be an installer issue.

I can install them out of FIPS enabled DC well. Even on other FIPS enabled DC outside domain.

Can you clarify what you mean here?

weiner22 commented 1 year ago

Hello @pauby,

To answer you questions:

pauby commented 1 year ago

Well I do use it. What´s wrong using it?

There is nothing wrong with using it, but it's not something we produce, support or know about. A standard troubleshooting process is to remove all the layers of complexity to get to the bottom, and then work your way back up to find the issue. So, we need to understand where the issue is coming from, and to do that we have to strip away PSAppDeployToolkit and Chocolatey CLI.

I can install it on the other systems even without Chocolatey.

On the FIPS enabled system you are having the issue on (i.e. the one above), can you:

  1. Can you download the installer and run it manually and see if it installs (note this is without Chocolatey CLI or PSAppDeployToolkit).
  2. Can you install the software using Chocolatey CLI (note this is without PSAppDeployToolkit).
weiner22 commented 1 year ago

Here is the answer: On the FIPS enabled system you are having the issue on (i.e. the one above), can you:

Can you download the installer and run it manually and see if it installs (note this is without Chocolatey CLI or PSAppDeployToolkit). Yes, I can execute installed & successfully finish the installation.

Can you install the software using Chocolatey CLI (note this is without PSAppDeployToolkit). What do you mean by Chocolatey CLI? This is just set of choco cmdlets isn´t it? If I try choco install it fails. I don´t have server connected to the internet.

pauby commented 1 year ago

What do you mean by Chocolatey CLI?

I'm not sure I understand your question. This repository is for Chocolatey CLI and you've reported the issue about this.

This is just set of choco cmdlets isn´t it?

No. My understanding is that PSAppDeployToolkit is PowerShell scripts.

If I try choco install it fails. I don´t have server connected to the internet.

I'm not sure I understand again. How did you get it to install originally? All I'm asking you to do is the same again, but by using Chocolatey CLI directly and without using PSAppDeployToolkit.

It might be easier to go back to the original issue comment and under 'How did you get this to happen?' add steps that allow us to reproduce the issue. Without that we're unlikely to be able to move forward.

TheCakeIsNaOH commented 1 year ago

Can you install the software using Chocolatey CLI (note this is without PSAppDeployToolkit). What do you mean by Chocolatey CLI? This is just set of choco cmdlets isn´t it? If I try choco install it fails. I don´t have server connected to the internet.

Chocolatey CLI is the choco.exe program. It is written in C#, and is a package manager. It installs Chocolatey packages (.nupkg files), using the choco install command. During a package installation, if the .nupkg contains a chocolateyInstall.ps1, then choco will start up a custom PowerShell host with a number of helper functions/cmdlets and run the chocolateyInstall.ps1.

Much of the time, a chocolateyInstall.ps1 will run an installer or extract an archive. But it can also run other PowerShell code, pretty much anything required.

Inside a chocolateyInstall.ps1, it is possible to use PSAppDeployToolkit, but PSAppDeployToolkit is completely separate program from Chocolatey CLI.

weiner22 commented 1 year ago

Hello @pauby I have got custom developed NuGet packages, stored on local NuGet server, so that´s explaining why I´m not connected to the internet, and from where packages are taken. After @TheCakeIsNaOH ´s answer I understand your second question :)

How did you get this to happen? Well, I have got nuget packages which I have installed over 50 systems already without any problem. I tried to install on FIPS enabled DC and failed with the mentioned error. Only on FIPS enabled DC. I tried other FIPS enabled system, no issue. That´s how it comes.

weiner22 commented 1 year ago

Dear, so the issue has got resolution. I had an option to spoke with one very experienced guy, thanks Hans! :)

ExitCode 6008 is caused only on Domain Controllers and only when you have your package written by using PSAppDeploy Toolkit. I had all packages on 3.8.0. Basically, the issue was within the template itself.

Once I did download of newer version (3.9.2) from here: https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/releases and updated packages accordingly it got resolved. You had to ensure whole content of folder AppDeployToolkit is replaces as well as Deploy-Application.exe & Deploy-Application.exe.config. In my particular case packages came from SCCM team, so I had to also comment out few SCCM related cmdlets like Add-SCCMHistorylog, set-arpband, remove-arpband, set-tatto, remove-tatto & it got fixed - the file I updated is called Deploy-Appliation.ps1. After that I could run choco pack to create new Chocolatey package & distribute it over my network to DCs. :)

Hope it helps.

TheCakeIsNaOH commented 1 year ago

Thanks for letting us know how you fixed it @weiner22

I'll close this issue as it was resolved with a PSAppDeploy toolkit update.