Azure DevOps deployment #129

Nouneds · 2023-04-18T08:31:19Z

Nouneds
Apr 18, 2023

Hi,
im trying to deploy the intune management into azure devops pipeline. Sadly i have an issues with powershell error stopping the job.
Any idea what exactly blocks the silent job ?
Here is some log file from failing step :

2023-04-18T07:54:59.5796946Z ##[section]Starting: Export Test
2023-04-18T07:54:59.6546658Z ==============================================================================
2023-04-18T07:54:59.6546792Z Task : PowerShell
2023-04-18T07:54:59.6546854Z Description : Run a PowerShell script on Linux, macOS, or Windows
2023-04-18T07:54:59.6546932Z Version : 2.212.0
2023-04-18T07:54:59.6546990Z Author : Microsoft Corporation
2023-04-18T07:54:59.6547049Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2023-04-18T07:54:59.6547133Z ==============================================================================
2023-04-18T07:55:01.8146047Z Generating script.
2023-04-18T07:55:01.8288765Z Formatted command: . 'D:\a\1\s\IntuneManagementTool\Start-IntuneManagement.ps1' -silent -JsonSettings -JsonFile Backup/settingsMAIN.json -SilentBatchFile Backup/BulkExport.json -tenantId XXX -AppId XXX -Secret XXX
2023-04-18T07:55:01.9203350Z ========================== Starting Command Output ===========================
2023-04-18T07:55:01.9528233Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\e0f2be94-8d68-437f-beae-8d40cb8a50d1.ps1'"
2023-04-18T07:55:03.9085225Z Use json settings file: D:\a\1\s\Backup\settingsMAIN.json
2023-04-18T07:55:03.9340806Z #####################################################################################
2023-04-18T07:55:03.9373513Z Application started
2023-04-18T07:55:03.9417581Z #####################################################################################
2023-04-18T07:55:03.9507349Z PowerShell version: 5.1.20348.1366
2023-04-18T07:55:03.9555153Z PowerShell build: 10.0.20348.1366
2023-04-18T07:55:03.9601315Z PowerShell CLR: 4.0.30319.42000
2023-04-18T07:55:03.9696989Z PowerShell edition: Desktop
2023-04-18T07:55:03.9941145Z OS: Windows Server 2022 Datacenter 10.0.20348.1607
2023-04-18T07:55:04.0816046Z Initialize-CloudAPIManagement : A positional parameter cannot be found that accepts argument '3'.
2023-04-18T07:55:04.0816891Z At D:\a\1\s\IntuneManagementTool\Start-IntuneManagement.ps1:24 char:1
2023-04-18T07:55:04.0817410Z + Initialize-CloudAPIManagement -View "IntuneGraphAPI" @param
2023-04-18T07:55:04.0817666Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-04-18T07:55:04.0818125Z + CategoryInfo : InvalidArgument: (:) [Initialize-CloudAPIManagement], ParameterBindingException
2023-04-18T07:55:04.0818569Z + FullyQualifiedErrorId : PositionalParameterNotFound,Initialize-CloudAPIManagement
2023-04-18T07:55:04.0818849Z
2023-04-18T07:55:04.1903105Z ##[error]PowerShell exited with code '1'.
2023-04-18T07:55:04.2443858Z ##[section]Finishing: Export Test

Answered by Micke-K

Apr 20, 2023

Hello!

I did not expect it to be fixed. I just added extra logging.

That looks like it doesn't have the modules folder downloaded eg the the logs says !!! 1.1 D:\a\1\s\IntuneManagementTool\Extensions

The next line says !!! 4.
That suggests that it can't find the Extensions folder so no modules are imported and therefore it fails.

Not sure why but it looks like it can't detect that folder.

Cheers!

View full answer

Micke-K · 2023-04-18T09:56:00Z

Micke-K
Apr 18, 2023
Maintainer

Looks like an issue on or after row 184 in Core.ps1: if(Test-Path $global:modulesPath)

It writes the PowerShell and OS information to the log, which is just above that.

So the error must be the Test-Path call or in Import-AllModules. Not really sure why tough. You could try to add some additional logging eg. add the Write-Log lines below to identify exactly where it fails.

Write-Log "!!! 1"
if(Test-Path $global:modulesPath)
{
Write-Log "!!! 2"
Write-Log "!!! 2.1 $($global:modulesPath)"

    Import-AllModules
}
else
{

Write-Log "!!! 3"
Write-Log "!!! 3.1 $($global:modulesPath)"
Write-Warning "Extensions folder $($global:modulesPath) not found. Aborting..." 3
exit 1
}
Write-Log "!!! 4"

Cheers!

0 replies

Nouneds · 2023-04-19T12:14:46Z

Nouneds
Apr 19, 2023
Author

Thanks for answering Micke!
I've tried to gather logs with your instructions but sadly it did not worked. Can You take a look?

2023-04-19T12:06:16.5451674Z ##[section]Starting: Export Test
2023-04-19T12:06:16.6411841Z ==============================================================================
2023-04-19T12:06:16.6411974Z Task : PowerShell
2023-04-19T12:06:16.6412039Z Description : Run a PowerShell script on Linux, macOS, or Windows
2023-04-19T12:06:16.6412124Z Version : 2.212.0
2023-04-19T12:06:16.6412191Z Author : Microsoft Corporation
2023-04-19T12:06:16.6412251Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2023-04-19T12:06:16.6412344Z ==============================================================================
2023-04-19T12:06:18.2630492Z Generating script.
2023-04-19T12:06:18.2727588Z Formatted command: . 'D:\a\1\s\IntuneManagementTool\Start-IntuneManagement.ps1' -silent -JsonSettings -JsonFile Backup/settingsMAIN.json -SilentBatchFile Backup/BulkExport.json -tenantId XXXX -AppId XXXX -Secret XXXX
2023-04-19T12:06:18.3278248Z ========================== Starting Command Output ===========================
2023-04-19T12:06:18.3498200Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\ce3a36ec-7e6c-43a0-984f-fd6467f88d0c.ps1'"
2023-04-19T12:06:21.0490060Z Write-Log : The term 'Write-Log' is not recognized as the name of a cmdlet, function, script file, or operable
2023-04-19T12:06:21.0491033Z program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2023-04-19T12:06:21.0491407Z At D:\a\1\s\IntuneManagementTool\Core.psm1:194 char:1
2023-04-19T12:06:21.0491749Z + Write-Log "!!! 1"
2023-04-19T12:06:21.0492052Z + ~~~~~~~~~
2023-04-19T12:06:21.0492790Z + CategoryInfo : ObjectNotFound: (Write-Log:String) [], ParentContainsErrorRecordException
2023-04-19T12:06:21.0492997Z + FullyQualifiedErrorId : CommandNotFoundException
2023-04-19T12:06:21.0493270Z
2023-04-19T12:06:21.1514569Z ##[error]PowerShell exited with code '1'.
2023-04-19T12:06:21.1879786Z ##[section]Finishing: Export Test

0 replies

Micke-K · 2023-04-19T13:21:10Z

Micke-K
Apr 19, 2023
Maintainer

That looks like it broke somehow. It did not even write the PowerShell info to the log.

Can you tried the attached version? I ran that with a silent batch job without any issues.

Core.zip

0 replies

Nouneds · 2023-04-20T07:53:20Z

Nouneds
Apr 20, 2023
Author

Sadly still the same issue.

2023-04-20T07:49:27.9712826Z ##[section]Starting: Export Test
2023-04-20T07:49:27.9837758Z ==============================================================================
2023-04-20T07:49:27.9837893Z Task : PowerShell
2023-04-20T07:49:27.9837961Z Description : Run a PowerShell script on Linux, macOS, or Windows
2023-04-20T07:49:27.9838043Z Version : 2.212.0
2023-04-20T07:49:27.9838111Z Author : Microsoft Corporation
2023-04-20T07:49:27.9838169Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2023-04-20T07:49:27.9838258Z ==============================================================================
2023-04-20T07:49:29.1567997Z Generating script.
2023-04-20T07:49:29.1627764Z Formatted command: . 'D:\a\1\s\IntuneManagementTool\Start-IntuneManagement.ps1' -silent -JsonSettings -JsonFile Backup/settingsMAIN.json -SilentBatchFile Backup/BulkExport.json -tenantId XXXX -AppId XXXX -Secret XXXX
2023-04-20T07:49:29.2077259Z ========================== Starting Command Output ===========================
2023-04-20T07:49:29.2333377Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a_temp\ed15cbef-7a3c-4c2d-bb62-ce1a58e22799.ps1'"
2023-04-20T07:49:30.6373968Z Use json settings file: D:\a\1\s\Backup\settingsMAIN.json
2023-04-20T07:49:30.6517654Z #####################################################################################
2023-04-20T07:49:30.6544662Z Application started
2023-04-20T07:49:30.6607124Z #####################################################################################
2023-04-20T07:49:30.6675784Z PowerShell version: 5.1.20348.1366
2023-04-20T07:49:30.6722520Z PowerShell build: 10.0.20348.1366
2023-04-20T07:49:30.6767367Z PowerShell CLR: 4.0.30319.42000
2023-04-20T07:49:30.6813617Z PowerShell edition: Desktop
2023-04-20T07:49:30.6980047Z OS: Windows Server 2022 Datacenter 10.0.20348.1668
2023-04-20T07:49:30.7006644Z !!! 1
2023-04-20T07:49:30.7032215Z !!! 1.1 D:\a\1\s\IntuneManagementTool\Extensions
2023-04-20T07:49:30.7070381Z !!! 4
2023-04-20T07:49:30.7836144Z Initialize-CloudAPIManagement : A positional parameter cannot be found that accepts argument '3'.
2023-04-20T07:49:30.7837107Z At D:\a\1\s\IntuneManagementTool\Start-IntuneManagement.ps1:24 char:1
2023-04-20T07:49:30.7837726Z + Initialize-CloudAPIManagement -View "IntuneGraphAPI" @param
2023-04-20T07:49:30.7837981Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-04-20T07:49:30.7838477Z + CategoryInfo : InvalidArgument: (:) [Initialize-CloudAPIManagement], ParameterBindingException
2023-04-20T07:49:30.7838971Z + FullyQualifiedErrorId : PositionalParameterNotFound,Initialize-CloudAPIManagement
2023-04-20T07:49:30.7839135Z
2023-04-20T07:49:30.8743644Z ##[error]PowerShell exited with code '1'.
2023-04-20T07:49:30.9225660Z ##[section]Finishing: Export Test

1 reply

Micke-K Apr 20, 2023
Maintainer

Hello!

I did not expect it to be fixed. I just added extra logging.

That looks like it doesn't have the modules folder downloaded eg the the logs says !!! 1.1 D:\a\1\s\IntuneManagementTool\Extensions

The next line says !!! 4.
That suggests that it can't find the Extensions folder so no modules are imported and therefore it fails.

Not sure why but it looks like it can't detect that folder.

Cheers!

Answer selected by Nouneds

Nouneds · 2023-04-20T14:11:15Z

Nouneds
Apr 20, 2023
Author

Indeed that was the case , we forgot to push that folder to devops repository. Thanks for Your help it works fine now !!!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Azure DevOps deployment #129

{{title}}

Replies: 5 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Azure DevOps deployment #129

Nouneds Apr 18, 2023

Replies: 5 comments · 1 reply

Micke-K Apr 18, 2023 Maintainer

Nouneds Apr 19, 2023 Author

Micke-K Apr 19, 2023 Maintainer

Nouneds Apr 20, 2023 Author

Micke-K Apr 20, 2023 Maintainer

Nouneds Apr 20, 2023 Author

Nouneds
Apr 18, 2023

Replies: 5 comments 1 reply

Micke-K
Apr 18, 2023
Maintainer

Nouneds
Apr 19, 2023
Author

Micke-K
Apr 19, 2023
Maintainer

Nouneds
Apr 20, 2023
Author

Micke-K Apr 20, 2023
Maintainer

Nouneds
Apr 20, 2023
Author