PowerShell / PowerShell/PSResourceGet
EXO module 3.2.0 fails with Beta release 3.0.19-beta19 in Azure Automation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
Once the module is updated to the beta one using Deploy to Azure Automation ( https://www.powershellgallery.com/packages/PowerShellGet/3.0.19-beta19) , it starts giving error on all EXO connections and cmdlets.
Expected behavior
EXO cmdlets to function as usual.
Connect-ExchangeOnline
Get-EXOMailbox
Actual behavior
Runbook job fails with error almost immediately.
Could not find file 'C:\Users\Client\Temp\d727d108-ef5f-4f03-ba69-3710bb36901f\tmpEXO_0gnprbg4.w0l.psd1'. (Could not find file 'C:\Users\Client\Temp\d727d108-ef5f-4f03-ba69-3710bb36901f\tmpEXO_0gnprbg4.w0l.psd1'.)
Click here for troubleshooting help
https://aka.ms/troubleshoot-runbooks
Error details
[exception=System.Management.Automation.RuntimeException: Could not find file 'C:\Users\Client\Temp\1ed07d87-5a75-48ab-9af8-d789d94da37b\tmpEXO_3v0dnrzt.icr.psd1'. ---> System.IO.FileNotFoundException: Could not find file 'C:\Users\Client\Temp\1ed07d87-5a75-48ab-9af8-d789d94da37b\tmpEXO_3v0dnrzt.icr.psd1'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost) at Microsoft.PowerShell.PowerShellGet.Cmdlets.UpdateModuleManifest.EndProcessing() at System.Management.Automation.CommandProcessorBase.Complete()
Environment data
PS Version 5.1.0
EXO Module 3.2.0
PowerShellGet 3.0.19-beta19
Works on 2.2.5 version
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in Azure Automation with EXO module 3.2.0 and PowerShellGet 3.0.19-beta19, using Connect-ExchangeOnline and Get-EXOMailbox. Trace the PowerShellGet.Cmdlets.UpdateModuleManifest failure involving the missing temporary .psd1 file, then compare the same run with version 2.2.5. Done means EXO cmdlets run successfully without the missing-file error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100