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.
Related
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 am trying to set up an environment for Component Pascal.
I chose the JVM option. I set a new system variable JROOT and added to the Path variable.
I try to run a new file I created via command line and got this error:
Error: Could not find or load main class CP.gpcp.gpcp
You must set a CPROOT environment variable to the instalation path of GPCP, something like
CPROOT=$HOME/gpcp;export CPROOT;
then add the bin directory to the GPCP executables to the PATH,
PATH=$CPROOT/bin:$PATH;export PATH;
both, in your .bashrc
Compile your CP program with
cprun gpcp <program>.cp
and execute with
cprun <program>
I am trying to use Jenkins to install a versioned msi on a target machine like this:
wmic /node:"[HOST]" /user:"[USER]" /password:"[PASS]" product call install true ,"", "\\[HOST]\D$\WebsitesDirectory\Product.*.msi"
The file name will contain the version number so I can't hard-code this into the wmic command. But wmic doesn't seem to be able to install a file using a wildcard and quietly fails to install when I run this command. It appears that it has to have the exact path and filename of the file to install it. Does anyone know a way of using wildcards within file names or perhaps a better workaround?
Another possibility is this - Is it possible to get the exact name of the file that Jenkins pulled in via the copy artifact plugin?
So apparently this is not a wmic issue but a windows cmd one. I found that this solves the problem:
for %%f in (*.msi) do (
wmic /node:"[host]" /user:"[user]" /password:"[pass]" product call install true, "", "\\[host]\D$\WebsitesDirectory\%%f"
)
I have performed a load test using JMETER.
But now not able to generate reports for the test.
To generate report I have followed these steps:
Create a new variable JAVA_HOME in the environment variable and set the path for the JDK.
Create another variable ANT_HOME and set the path for the Apache-ant.
Create another variable PATH and set the path for apache-ant up to BIN folder.
Place the ant-jmeter-1.0.9.jar file in side ‘Extras’ folder. Which is located in the path jakarta-jmeter-2.3.2->extras
Navigate to the ‘build.xml’ folder of the jmeter which is located in the path jakarta-jmeter-2.3.2->extras->build.xml.
Set the classpathref = “D:\loadtest\jakarta-jmeter-2.4\extras\ant-jmeter-1.0.9.jar “
Set jmeterhome=”D:\loadtest\jakarta-jmeter-2.4″
Set style=”D:\loadtest\jakarta-jmeter-2.4\jmeter-results-detail-report${style_version}.xsl” and save it.
Now copy jmx file and the build.xml file put it in a folder (Loadtest) where ever you want to generate the report.
Open command prompt and navigate to the folder where jmx and build file is located.
To run a test and create the output report:
Type the command “ant -Dtest=script”(for eg. I have my test.jms file and the command is ant -Dtest=test)
By following above steps Reports are not generated but I got following error:
BUILD FAILED
D:\Loadtest\result\build.xml:85: Reference D:/Loadtest/jakarta-jmeter-2.4/
extras/ant-jmeter.jar not found.
Can you help me find the solution?
Check jMeter version. The error says you're using 2.4, but your Jmeter home points to 2.3.2.
Did you include ant-jmeter-1.1.1.jar in your Ant classpath ? Adding the jar to $ANT_HOME/lib will make this happen automatically.
See:
http://www.programmerplanet.org/pages/projects/jmeter-ant-task.php
ant-jmeter-1.1.1.jar is in jmeter/extras folder.
Furthermore I suggest you upgrade to last JMeter 2.7 version as it contains enhancements of the report.
Regards
Philippe M.
http://www.ubik-ingenierie.com/-Solutions-
I have installed SenchaSDKTools-2.0.0-beta3-windows on my windows Xp 32-bit.
following is the command I am running on command prompt.
C:\Program Files\SenchaSDKTools-2.0.0-beta3>sencha app create MyApp c:\xampp\htdocs\sencha\myapp\
Giving following error
[ERROR] the current workind directory (C:\Program
Files\SenchaSDKTools-2.0.0-beta3>) is not valid SDK directory. Please
'cd' in to a SDK directory before executing this command.
environment variable has been set following way.
Variable name : Path
Value : C:\Program Files\SenchaSDKTools-2.0.0-beta3
can anyone figure out what exactly wrong in this process ?
*****Sencha Touch setup Guide steps(in Window)******
Download Sencha Touch SDK Tool. (http://www.sencha.com/products/touch/download/ -->SDK Tools Beta for Developers). Run .exe file. It will install tool to default path. (i.e. C:\Program Files\SenchaSDKTools-2.0.0-beta3)
Download Sencha Touch SDK. (Download openSource version file licensed under GPL.).
Extract SDK you just download in step 2.
Open Command line terminal (start->Run->type cmd). Change directory path to SDK path as you just extracted in step3.
Verify that Sencha Command is working properly on your machine. So Type Sencha.
E.g. sdkPath>sencha
you will see "Sencha Command v2.0.2" message with other sencha command detail.
Create app in your web directory by typing following.
E.g. sdkpath> sencha app create firstSenchaApp "path/ to/ www"
(If you have tomcat 7 installed in your computer, give path to \apache-tomcat-7.0.30-windows-x86\apache-tomcat-7.0.30\webapps)
Note: There must not be space in directory path name. _(underscore),- (desk) are allowed.
If app is not generated in step 6. There might be an error. There are as follow:
If error message appear is "sencha' is not recognized as an internal or external command, operable program or batch file.”, follow these steps to troubleshoot:
The path to SDK Tools directory is prepended to your system's PATH environment variable.
From the terminal, run
echo $PATH or echo %PATH% .
The SDK Tools directory should be displayed in part of the output. If this is not the case, add it to your PATH manually.
The environment variable SENCHA_SDK_TOOLS_{version} is set, with the value being the absolute path to the installation directory mentioned above.
For example: If the installed version is '2.0.0-beta2', a SENCHA_SDK_TOOLS_2_0_0_BETA2 must be set.
From the terminal, run
echo $SENCHA_SDK_TOOLS_2_0_0_BETA2 or echo %SENCHA_SDK_TOOLS_2_0_0_BETA2% on Windows.
If the output is empty, set the environment variable manually.
Wrong Current Working Directory
A common mistake is not running Sencha Command within either a valid SDK directory or an application directory. If the current directory is not a SDK or application directory, "sencha" command will fallback to backwards-compatible mode. As of SDK Tools release "2.0.0-beta2", you should see a clear warning in such case:
"The current working directory (...) is not a recognized Sencha SDK or application folder. Running in backwards compatible mode." So in this case follow proper step as mentioned above.
Reference:
http://www.sencha.com/forum/showthread.php?192169-Important-SDK-Tools-Sencha-Command-Update
There is an invisible file that you need to copy, called .senchasdk. Make sure it is in the folder.
I think you're having the same problem I had; I had attempted to run 'sencha app create...' from the folder containing sencha.bat. Instead, you need to run 'sencha app create...' from the sencha-touch-2.0.1.1 folder (which contains the .senchasdk file).
See this previous SO question!
Save my days.
By the way, if you can't extract the sencha-cmd to sdk tools, try to extract on other location and copy the folder [3.0.0.250] to your sdk tools > [bin] folder.
hope this helps.