However, an update to the database caused extremely high CPU/DTU utilization which tied up cloud service resources. Depending on the exact error message you got, either:1) The source needs to be trusted (see step 3)2) The SourceLocation is not accessible (see step 4)3) The SourceLocation URI needs to end with ‘/’ (see step 5), Run the following commandlet:Set-PSRepository -Name "PSGallery" -InstallationPolicy TrustedIf you get an error like this:Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable. Status: RESOLVED. You can get them automatically right as I post them! Here, expert and undiscovered voices alike dive into the … We apologize for the inconvenience. Check them out on Archive.org! Summary of Impact: Between 7/11/2016 and 7/13/2016, a subset of customers experienced issues downloading items from the PowerShell Gallery. Open source and radically transparent. The current workaround for users is to import the item from the PowerShell Gallery from inside Azure Automation. Summary of Impact: Between 8/5/2016 and 8/10/2016, customers were unable to send emails to cgadmin@microsoft.com, or use the Contact Us feature. Summary of Impact: The PowerShell Gallery experienced a period of very high latency, resulting in intermittent connection issues, beginning approximately 5pm (PDT) 10/10/17.
This was being reported across all the regions. I've been developing both classic server stuff, but also (and actually especially) more cloud-oriented stuff in the past 10 years. There's an occasional post about software issues other than on Microsoft's stack, and a rare post about hardware, too! The site was restored shortly before midnight 10/10/2017. Summary of Impact: Deploying items with dependencies to Azure Automation from the PowerShell Gallery is currently unavailable. The issue likely manifested itself in the following error message returned from Install-Module/Install-Script and Save-Module/Save-Script: Preliminary root cause: Engineers identified an issue with Azure Content Deliver Network (CDN), which was deployed to the PowerShell Gallery on 7/11/2016. The update will lock specific tables in the database and may potentially impact search requests made to the gallery. PackageManagement\Save-Package : Unable to save the module, Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1187 char:21 +, $null = PackageManagement\Save-Package @PSBoundParameters +, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +, CategoryInfo : InvalidOperation: (Microsoft.Power...ets.SavePackage:SavePackage). Root Cause: During an update to interact more securely with AAD, a setting change was missed. Started coding at the age of 13, now a professional software engineer creating and maintaining enterprise solutions.
That's definitely enough funny buzzwords! While resolving the issue, the site was taken offline for 2 hours starting approximately 10pm (PDT). Next Steps: Investigate the underlying root cause and developing a solution to prevent future occurrences. Root Cause: Work was happening to migrate data lost from the last outage to get the statistics up-to-date. PS C:\> Set-PSRepository -Name PSGallery -InstallationPolicy Trusted Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable. Summary of Impact: PowerShellGallery.com is experiencing an outage. During 2017 you could've run into me in the US of A as well (I was living in Wisconsin) and 2018-2019 in Montréal. Resolution: Changes have been made to the script and process used to roll out configuration changes to prevent this problem from recurring, and the service itself has also been made more robust against this kind of issue. Learn more. Learn more. Summary of Impact: PowerShellGallery.com is experiencing lags and low availability. Resolution: Engineers were able to resolve the authentication issue and restore connection to the SMTP server. We are actively monitoring the gallery to ensure it maintains proper operation across all regions. Users will be unable to access the gallery or download packages. Root Cause: A configuration change was applied to Azure Automation that corrected the issue.
A constructive and inclusive social network. I just tried, and didn't see the problem. This should not impact package downloads. We're a place where coders share, stay up-to-date and grow their careers.
Check out the tech & programming tips, often about ASP.NET MVC, Entity Framework, Microsoft SharePoint Server & Online, Azure, Active Directory, Office 365 or other parts of the Microsoft's stack. Antti Koskela is a proud digital native nomadic millennial full stack developer (is that enough funny buzzwords? Good, execute the migration command Microsoft provided in their announcement and you'll be good to go: This will change the security protocol to TLS 1.2. The error is something along the lines of: “System.InvalidOperationException: PowerShell Gallery is currently unavailable.