I need to create Greengrass group and core in aws iot(windows).
I have referred with the document https://docs.aws.amazon.com/cli/latest/reference/greengrass/create-group.html
I have tried with powershell script aws greengrass create-group \ --name ggawsgreen
Gets error when executing above powershell script . error => aws : The term 'aws' 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
How to create Greengrass group and core(aws iot) in windows powershell
the error appears because you haven't installed the AWS Command Line Interface or aws cli for short.
Or ´aws cli´ is not in your path.
download here
Related
I have read the documentation and followed the steps to run mongodump on windows machine, but still getting this error.
I tried to set the path using this command set path="C:\Program Files\MongoDB\Server\4.4\bin" and added the path in environmental variables but still getting the error. What should I do ?
I'm trying to create a new environment from file, when i run conda env export > environment.yml the file is created but when running vim environment.yml i get this error
vim : The term 'vim' 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.
when trying to run conda env create --prefix .\env -f ..\environment.yml on my new project directory i get An unexpected error has occurred.
I have a powershell script that I developed and can run fine manually. However when I put the script into a sql server job and attempt to run the following line...
SET-LOCATION "$NewTargetPath\"
TortoiseProc /command:update /path:$SVNRepository /closeonend:3
I get the following error:
Executed as user: myserviceaccount. A job step received an error at line 146 in a PowerShell script. The corresponding line is 'TortoiseProc /command:update /path:$SVNRepository /closeonend:3'. Correct the script and reschedule the job. The error information returned by PowerShell is: 'The term 'TortoiseProc' 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. '. Process Exit Code -1. The step failed.
I've checked the paths they all look good and I can even run the command from a powershell command line on the server. Any ideas on where to look for why this error may be occurring?
I tried to install Posh-Git to use ssh with Powershell.
I followed the instructions here
The file here was not digitally signed so I changed the Execution Policy to install it. I then (for whatever reason) decided not to use this so I removed the file.
Now whenever I start Powershell I get an error similar to the below:
The term 'C:\xxx\xxx\profile.example.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program.
How do I stop this error message from appearing each time I start Powershell?
You need to edit your PowerShell profile and remove that line from there. The easiest way would be (from within your PowerShell):
notepad $profile
or alternatively you can look up your profile with $profile and edit the file there.
Consult this for further reading: https://blogs.technet.microsoft.com/heyscriptingguy/2012/05/21/understanding-the-six-powershell-profiles/
I'm using PowerShell to set up a test instance that is running on Windows. When the instance is up and running it will then run a few commands to get Hadoop set up and will then run a Spark job.
This all works fine when done manually from within the instance itself. I'm now trying to translate those commands into powershell.
These two for example are failing with the message that it is not a recognised cmdlet or function etc:
& $env:HADOOP_HOME + "\bin\winutils.exe" chmod 777 /tmp/hive
& $env:HADOOP_HOME + "\bin" hadoop namenode -format -force
The error I receive is:
& : The term 'c:\hadoop\bin' 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 line:1 char:3
I've then tried various combinations of wrapping in quotes, using iex, assigning it to a variable, but all fail.
PowerShell interprets the expanded value of $env:HADOOP_HOME as the command to execute, which fails, because a folder isn't a cmdlet, function, script file, or operable program. Do the concatenation in a subexpression:
& ($env:HADOOP_HOME + "\winutils.exe") chmod 777 /tmp/hive
or put the environment variable directly in the command string:
& "$env:HADOOP_HOME\winutils.exe" chmod 777 /tmp/hive