-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Configuring Availability Group failed: The term 'Get-DbaAvailabilityGroup' 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."} #269
Comments
This indicates that dbatools is not actually available on the host you're running against. Try adding some basic pwsh debug tasks to ensure that you can execute dbatools functions on the host. Please also include your playbook and inventory sample for a MVP. |
Its also worth noting that if you are intending to execute this on the controller, you'll need to use a connection hack (https://github.com/lowlydba/lowlydba.sqlserver/blob/main/tests/integration/targets/setup_sqlserver_test_plugins/connection_plugins/local_pwsh.py) like we do in the testing pipelines in order to get pwsh to execute correctly. |
Below is the inventory
Below is the main.yml playbook
|
How to use this in my playbook? |
I already installled the dbatools powershell module in the target windows machine. |
Please check how it is used in the |
not Recognized as the name of a cmdlet
I am trying configure SQAON in azure VMs. I installed dbatools in windows target machine. In the source i installed pymssql, it is the mandatory pre-req to install py packages and ps modules
To Reproduce
Expected behavior
Once i import he ansible collection in my playbook . It should be able to create ag and ag listener. But i am facing like error as below:-
fatal: [sqlnode2.accit.com]: FAILED! => {"changed": false, "msg": "Configuring Availability Group failed: The term 'Get-DbaAvailabilityGroup' 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."}
Versions(please complete the following information):
**Please attached the screenshots
**
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: