avoid error in ssis package using winscpcommand - ssis

Hi I have doubt in ssis using winscp commands on excuteprocess task
I need download/move .zip file from remote server to local server machine.
Here I follow few steps:
step1:I install winscp software in local server .
step2: I configure winscp settings with hostnameand username and pwd it working fine.
step3: I tried to implement ssis package using executeprocess task
there I given like below seetings in execute process task
executable:
C:\Program Files (x86)\WinSCP\WinSCP.exe
Arguments:
WinSCP /command "open ""sftp://uesrname:pwdhostname""" "get ""remoterservrpath"" localpath" "exit"
after that I ran execute process task.then file is moved from remoteserver to localserver path location
then imedentaily package failed with below error message
[Execute Process Task] Error: In Executing "C:\Program Files (x86)\WinSCP\WinSCP.exe" "WinSCP /command "open ""
sftp://usernamepwdhostname""" "get ""test.zip""
C:\Users\test\Desktop\Test\test.zip" "exit"" at "",
The process exit code was "1" while the expected was "0".
here usernamepwdhostname I did not share orignal.I mention similay format.
zip file is moved from remote to local server location.its fine.but I am getting package error after move the .zip file
please tell me how to avoid this error in ssis package level

In the arguments field, remove the WinSCP part at the start
executable:
C:\Program Files (x86)\WinSCP\WinSCP.exe
Arguments:
/command "open ""sftp://uesrname:pwdhostname""" "get ""remoterservrpath"" localpath" "exit"

Related

Getting an error Unable to locate appender "jmeter-log" for logger config "root" while running and creating the html dashboard for my jmeter scripts

I am trying to create Jmeter HTML report through CSV with the help of command but getting below error in my CMD. Please help me what i need to change or enhance for getting the reults
2020-07-23 16:47:20,385 main ERROR Null object returned for File in Appenders.
2020-07-23 16:47:20,409 main ERROR Unable to locate appender "jmeter-log" for logger config "root"
An error occurred: Cannot read test results file : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
errorlevel=1
Press any key to continue . . .
The main problem is Cannot read test results file and it occurs when you point JMeter to not-existing file or the file cannot be read (you don't have permissions to open the file in that location)
The other problem is with JMeter logging configuration, either your log4j2.xml file is broken or again you don't have proper read/write permissions to the folder where JMeter is installed. Try running the terminal with elevated rights and both should go away
I solved this problem by installing the latest version of Jmeter, 5.3. After that, no more logging/summarizer errors.

Installing Yii 2 starter kit on Windows error: `'cp' is not recognized .. event returned with error code 1`

How to solve it when installing Yii 2 starter kit on Windows with the recommended command composer run-script docker:build, why this error happens?
'cp' is not recognized as an internal or external command,
operable program or batch file.
Script cp .env.dist .env handling the build:env event returned with error code 1
Script #build:env was called via docker:build```
it is because normally the command cp is not available at the Ms Windows operating system
It must be currently edited in the composer.json file in the root directory, the scripts->build.env part must have changed cp command to copy as a temporal workaround
scripts": {
"build:env": [
"cp .env.dist .env"
],
to
scripts": {
"build:env": [
"copy .env.dist .env"
],

Winscp batch file will not run from scheduler

I created a batch file to download a file from a client. I am running windows server 2012. I am using a execute process task in ssis 2014. Both the batch file and my package run fine manually. When I run via the ssis scheduler it gets the following error: Exeute Process Task Error- In Executing C:\Windows\System32\cmd.exe""/C E:\Scripts\Nationwidebatch.bat"at"". the process code was "1" while expected was "0".
#echo off
"C:\Program Files (x86)\WinSCP\WinSCP.com" ^
/log="C:\Users\jfrench\AppData\Local\Temp\4\!S.log" /ini=nul ^
/command ^
"open sftp://ecafxxxx:xxxxxxx#tower.nationwide.com/
-hostkey=""ssh-rsa 2048 a6:e9:1a:b0:0d:09:0f:2d:2b:92:82:00:d3:87:9b:36""" ^
"cd /FromNationwide/icafarmb" ^
"option transfer ascii" ^
"get allied.txt \\CFBF-SQL\Insurance\Download\AlliedNW\" ^
"exit"
set WINSCP_RESULT=%ERRORLEVEL%
if %WINSCP_RESULT% equ 0 (
echo Success
) else (
echo Error
)
exit /b %WINSCP_RESULT%
I have run it manually from a batch file, manually from visual studio , and manually from ssis catalog db and they all run successfully. As soon as you add it to the scheduler it dies.

Load new module in Kamailio

I would like to ask, how can I load new module in Kamailio 4.1.2?
Actually, I have an issue, when I tried to compile my kamaiio.cfg
I've got error:
root#kamailio:/usr/local/# kamailio -c kamailio.cfg
loading modules under /usr/local/lib64/kamailio/modules/
0(25392) ERROR: <core> [sr_module.c:587]: load_module(): ERROR: load_module: could not find module <websocket> in </usr/local/lib64/kamailio/modules/>
0(25392) : <core> [cfg.y:3408]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 323, column 12-25: failed to load module
0(25392) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find command ws_handle_handshake
0(25392) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 1083, column 27: unknown command, missing loadmodule?
ERROR: bad config file (2 errors)
when I look physically to the /usr/local/lib64/kamailio/modules/ there is some modules, but websocket.so is missing.
So, how can I get and load module in Kamailio?
Thank you for help!
You haven't installed the module websocket. Edit modules.lst file in the source code directory and add websocket to include_modules variable. If you don't have modules.lst, just do:
make cfg
Alternative is to do:
make cfg include_modules="websocket"
By default, the build system for kamailio compiles and install only the modules that have the same dependencies as the core of the application. For websocket you need to install libunistring and openssl (libssl) devel packages.
Steps to load new module to Kamailio server. (Try if above answer is not working for you)
Check the modules is exist in the default module directly /usr/local/lib64/kamailio/modules.
If found, add loadmodule "module_name.so" in load module section in kamailio.cfg file.
If the module is not found in default module directory, you can check for the source code of that module in the default module source code directory /usr/local/src/kamailio-4.4/kamailio/modules.
If source code found, enter to the module directory. Then create modules' shared object file(.so) by following commands.
./configure
make
make test
make install
Then you will get a shared object file(.so). Copy that file into the default module directory. and load this module from the kamailio.cfg file as mentioned in step 1.
If module source code does not exist in the default source code directory, You need to download the source code from the web. And follow step 3 and 4.

dtexec error "The connection xxx is not found" with Project deployment model

When running DTEXEC I am getting "The connection xxxx is not found".
I beleieve this is because the connection managers are located at Project level and not within the package itself.
When running DTEXECUI - these connection managers are not displayed.
Is the only way to move them into the package - seems a bit weird as what is the point of allowing them a project level if you then have to move them to use them with DTEXEC.
Thanks
Here is the command line syntax you asked for:
C:\Users\Administrator>dtexec /FILE "\"F:\SSIS Projects\HESA\HESA\01 - Upload Metadata Files To Oracle.dtsx\"" /SET "\Package.Variables[User::varYear.Properties
[Value]";"1999" /CHECKPOINTING OFF /REPORTING EW /CONSOLELOG SMT
Your assumption that
the connection managers are located at Project level and not within the package itself
is exactly the problem. But there is a solution:
build the project to get a .ispac file
instead of invoking dtexec with /FILE you have to invoke it with /Project and /Package, like this:
/Project "path to you .ispac file, resulting from building the project"
/Package "Name of your package.dtsx"
Please, be aware that if you provide the whole path to your .dtsx package the execution will fail with very criptic SQLDUMPER error messages.