Last week, when preparing for a deployment, I bumped into this error again. As from my previous post, it could be easily fixed with a PowerShell module install.
But this time, the script was already fixed. Nothing had changed, as far as I knew. The last build and publish was in September, no errors there.
So what happened that killed my build?
It couldn’t be the Az module updates, because we were forcing the version. There had been several updates, so could this be it?
I tried to force a newer version, like 2.0.0, but still failed to execute the command. I even restricted the script to use only the command I needed, that was the CallbackUrl.
After a few other failures, my thinking was, “this can’t be the problem, the script was executing without issues, so it has to be something else.”
So I took another look at my pipeline. It was the same as before… Azure Powershell task to remove AzureRM, install Az module and Azure CLI task to execute the scri… wait!
Could this be the problem?
I switched the tasks and re-queued the pipeline.
And success! No more errors.
Azure CLI has received some updates in the past weeks, and the build I had before was 2.0.16 (Core 2.11.0) compared to 2.1.0 (Core 2.18.0) was running in these failed pipeline runs.
I looked into the Azure CLI release notes, but found nothing referring the LogicApp commands or Az.LogicApps.
This time, I can’t find a proper explanation for this error, but I’m suspecting some update broke the ability to run these Az module commands with Azure CLI or the Az.LogicApps commands specifically.
3th Edition of 101 Talk Arena is here and now I’m joining forces with Nino Crudele to interview the one and the only Michael Stephenson!
Michael Stephenson is a highly experienced Cloud Architect who has many years working with large enterprise customers delivering integration solutions with Microsoft technologies on-premise, in the cloud, and with hybrid technologies. Not only he is a brilliant mind, and an unstoppable researcher, he is also a regular blogger and host of Integration Monday!
He is a good friend, and it will be an honor to have him with us on February 18th, 2021, at 2 PMUTC. Once again this will be an open conversation about Integration and Azure:
Cloud automation
Serverless patterns and practices
Today Integration landscape
BizTalk migration
and many more topics
I will invite all of you to join us it is free. This is a one to one talk without filters, no marketing, nothing planned, and where people can also jump in with any question.
Last February 4, the roles were reversed, and I had the pleasure to interview Nino Crudele on our series 101 Talk Arena on a talk about Azure Nightmares without any filters, and it was a blast!
Now I’m happy to announce that the record of the second edition of 101 Talk Arena is online and available for all of you to watch on youtube were address topics like Azure Subscription strategies, costs and security.
Implementation of Microsoft 365 went rocket high when Covid19 disrupted the entire world. People are more social through technology due to worldwide lockdowns. As we take advantage of new technology, the addons that follow can help grow your business, expand the capabilities, improve the processes and make your workers more efficient.
Webinar: PowerTalk by Atea is an event that will go through the tools Power Automate and Power Apps included in Microsoft365. From the basics to the more advanced scenarios. How to ensure that governance and security are taken into consideration and amended to create a secure way for your employees to become more digital and efficient.
I’m honored to be a guest speaker at this event on a session about Power Automation: Best practices, tips and tricks. My session will take place at 10:00 am according to GMT+1.
Power Automation: Best practices, tips and tricks
As I mentioned before, my session will be all about best practices and small tips and tricks that we can apply to our Power Automate flows. For those reasons, I would like to invite you to join me at the Webinar: PowerTalk by Atea virtual event on Thursday, February 25, 2021.
Session name: Power Automation: Best practices, tips and tricks
Abstract: In this session, we will do a reflection to your existing Power Automation flows and when thru a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective flows. At the same time, these will allow you to be more productive and document your flow’s from the beginning. I will be sharing 10 tips that you should know for being more productive and build epic flows!
Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?
Integration weekly updates can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.
It has been a long time since I go off-topic on my main blog topic: Enterprise Integration. Nevertheless, everything that I wrote is somehow related to my daily job, and if you keep an eye on my blog, you will know that I like using PowerShell for scripting and automate several tasks.
Today while I was implementing a PowerShell script that I use in several clients I was surprised by this error: Invoke-Sqlcmd : The term ‘Invoke-Sqlcmd’ is not recognized as the name of a cmdlet, function, script file, or operable program.
The full warning message would be:
Invoke-Sqlcmd : The term ‘Invoke-Sqlcmd’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:pathpowershellscript.ps1:7 char:14
The error message is very clear, and the problem is quite simple to solve… except if your machine doesn’t have connectivity to the internet. But let’s first explain the issue.
Cause
As I told you before, The error message is very clear, and the problem is quite simple to solve, the SQL Server PowerShell module is not installed on the machine.
Many may think that SQL Server Management Studio is a requirement or by installing it may solve this problem, but that is not true. In fact, SQL Server Management Studio (SSMS), doesn’t install the PowerShell module.
Solution 1: System with access to the Internet
If the machine where this issue is happening has access to the internet, then you just need to install the SQL Server PowerShell module by executing the following script:
Import-Module sqlserver
Note: You should run PowerShell as an Administrator
Solution 2: System without access to the Internet
However, if your machine doesn’t have access to the internet you will get the folowing error idf you try to execute the above script:
Unable to download from URI ‘https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409’ to ”. Unable to download the list of available providers. Check your internet connection. PackageManagementInstall-PackageProvider : No match was found for the specified search criteria for the provider ‘NuGet’. The package provider requires ‘PackageManagement’ and ‘Provider’ tags. Please check if the specified package has the tags. At C:Program FilesWindowsPowerShellModulesPowerShellGet1.0.0.1PSModule.psm1:7468 char:21 + … $null = PackageManagementInstall-PackageProvider -Name $script:N … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (Microsoft.Power…PackageProvider:InstallPackageProvider) [Install-PackageProvider], Exception + FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackageProvider PackageManagementImport-PackageProvider : No match was found for the specified search criteria and provider name ‘NuGet’. Try ‘Get-PackageProvider -ListAvailable’ to see if the provider exists on the system. At C:Program FilesWindowsPowerShellModulesPowerShellGet1.0.0.1PSModule.psm1:7474 char:21 + … $null = PackageManagementImport-PackageProvider -Name $script:Nu … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (NuGet:String) [Import-PackageProvider], Exception + FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.ImportPackageProvider Unable to download from URI ‘https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409’ to ”. Unable to download the list of available providers. Check your internet connection. PackageManagementGet-PackageProvider : Unable to find package provider ‘NuGet’. It may not be imported yet. Try ‘Get-PackageProvider -ListAvailable’. At C:Program FilesWindowsPowerShellModulesPowerShellGet1.0.0.1PSModule.psm1:7478 char:30 + … tProvider = PackageManagementGet-PackageProvider -Name $script:NuGet … + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Microsoft.Power…PackageProvider:GetPackageProvider) [Get-PackageProvider], Exception + FullyQualifiedErrorId : UnknownProviderFromActivatedList,Microsoft.PowerShell.PackageManagement.Cmdlets.GetPackageProvider
To solve this issue you need to:
From an Internet-connected computer, execute the following script
Save-Module sqlserver -path c:temp
Note: You can set a different path to save the module.
The above command will save the SQL Server PowerShell module to the directory you set on a folder called SqlServer
In my case, c:tempSqlServer
Then, copy that whole directory to your target computer(s) to the following folder:
C:Program FilesWindowsPowerShellModules
By coping to this folder it will make the module available to all users.
If you are not sure about the path, you can always check the paths by exxecuting the following script:
Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?
Integration weekly updates can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.
It was with great pleasure that I presented for the first time on January 29, 2020, a session at the Azure Lowlands event, this time about How to create robust monitor solutions with PowerShell, Azure Functions, and Logic Apps.
First of all, I want to congratulate the organizers on a very well organized event!
About the session
Session name: How to create robust monitor solutions with PowerShell, Azure Functions and Logic Apps
Abstract: Monitoring your systems or platforms is a crucial aspect of any organization. Based on my experience, all your clients will tell you that all the platforms or applications are being monitoring by external partners or internally. Nevertheless, when disasters occur or are in the process of happening, guess what? Your team will be the last to know. This session will address and present how you can easily and quickly create a robust monitoring solution on your platforms using PowerShell, Functions app, and Logic Apps or Power Automate Flows.
How to create robust monitor solutions with PowerShell, Azure Functions and Logic App Slides
How to create robust monitor solutions with PowerShell, Azure Functions and Logic App Video
For any reason, you could not be present at this online event, or if you want to review it again, you can now do it here: https://youtu.be/vf9cmfEb3Z8?t=10886