I have got an error while deploying symphony/vue project on localhost.
I typed in cmd
php bin/console deploy
an error occurred:
"}" is not recognized as an internal or external command, operable program or batch file
I tried to disable clrf endings in git, but it did not help.
I tried to add path to project into Paths, but it did not help.
What is reason for that?
Please, help!
Thanks!
Related
This is one of the problems where I don't even know how to properly frame the question.
I'm trying to follow a React course on Lynda.com
The instructor says to type into my command window the following:
node_modules/.bin/webpack-dev-server
But when I enter it I get
'node_modules' is not recognized as an internal or external command,
operable program or batch file
The autocomplete will fill in "node_modules" but not ".bin". I've checked that webpack-dev-server.cmd is inside the .bin folder, and that npm is in my proper path. (yarn and npm both work as commands in this folder.)
I've tried several different command shells including ConEmu, but all throw the same error.
I'm really at a loss for how to proceed from here. Is the problem that the instructor is using a different operating system and I'm just missing a subtle difference in the way that I have to enter the command?
I have a .cmm file which helps in debugging of Qcomm chipsets.
This file has a line : cd ../../../../../modem_proc
When I run this same cmm file using T32 GUI, it runs fine and does the work. But when I am trying to run the same file using windows command line using,
C:\T32\bin\windows64>t32mqdsp6.exe -c C:\T32\config.t32 -s D:\path\to\xxx.cmm
Following error is thrown in T32: syntax error in B::cd ../../../../../modem_proc
What am I missing here? I have no hands-on experience with T32 what-so-ever.
The problem probably results from different working directories. Type
PRINT OS.PWD()
in the GUI and add it to the top of the script. I'd suspect they are different.
Don't use working directory relative paths, instead use paths relative to the script, e.g.
CD ~~~~/../../../../modem_proc
The four tilde (~) symbols mean "directory of the currently executed script". There's still a possible issue with this solution when using multiple GUIs and the intercom, but for most use-cases this should be OK.
When starting TRACE32 (up to build 99518) without option "-s", it starts a default script t32.cmm form your TRACE32 installation directory. But t32.cmm is not executed, when "-s" is used.
So probably your t32.cmm is changing your working directory. If so you can fix the issue by adding the line
DO ~~/t32.cmm
to the top of your script xxx.cmm.
See also https://www.lauterbach.com/frames.html?help_autostart.html
The default working path is also set by the TRACE32 configuration file. That is the file passed with "-c". So if your are using a different configuration file than C:\T32\config.t32 when starting your TRACE32 GUI the normal way, then you should use that configuration file also when starting TRACE32 from the command line.
To get the path of the configuration file usually used, start TRACE32, execute command AREAand then command PRINT OS.PCF()
Furthermore dev15 is probably right here https://stackoverflow.com/a/53671657/4727717:
Use paths relative to the PRACTICE script (cmm-file) by starting each path with four tildes.
I'm new to node js, I having a issue with express-gateway
I have installed node(V 10.0.0), express(V 4.16.3) & express-gateway.
I'm getting an error:
D:\User\Test\Express-Gateway>eg -version
'eg' is not recognized as an internal or external command,
operable program or batch file.
as I fire cmd: eg -version or eg express-gateway create
Thanks in advance.
In case of a valid installation, you can find a corresponding windows command script (named eg) residing in your node installation folder (e.g.: C:\Program Files\nodejs\eg).
Next the windows environment variable PATH has to contain the above mentioned path (in order to check this just run PATH in cmd shell => this will print out the value of PATH, which is a list of file paths seperated by semi colons). If the node.js entry is missing, you can add the path by updating the variable manually.
When i run grunt command through manually opening the cmd and write the command then it works nicely, but the same command is not working through batch file.It shows grunt is not recognized as internal or external command.
please help me to fix this.
Thanks in advance.
If I run a package from the Management Studio, and specify a configuration file, everything works as expected. I can also set the package to get it's config path from an environment variable, and that approach works as well.
However, if I try and run the package from the command prompt with DTExec I get the error:
Cannot load the XML configuration
file. The XML configuration file may
be malformed or not valid.
The command I'm using to execute the package is:
dtexec /conf ConfigurationDemo.dtsConfig /f Package.dtsx
I am running the dtexec from the folder where these two files reside. Is there an addtional switch or something that must used to get dtexec to behave the same was at the management Stduio in launching a package?
Have you checked the config file is a valid XML file? By the look of the error message there may be a problem with it. When you run it from SSMS is it using the same config file?