Perl Error 65280

PerlNews Q&A Tutorials Poetry RecentThreads NewestNodes Donate What'sNew on May 22, 2013 at 14:02UTC ( #1034752=perlquestion: print w/replies, xml ) Need Help?? Prakash Babu has asked for the wisdom of the Perl Monks concerning the following question: I have perl script exit code 65280 in unix that is executed from a Application server using java on Windows 2003. my $zipExec='C:/zip.exe'; exit code 65280 in informatica my @cmd = ($zipExec, "-rq", $destinationPath, "."); print "Executing command @cmd\n"; $syscode = system(@cmd); my $error = $!; print "Return code = exit code 65280 linux $syscode \n"; print "Error = $error\n"; [download] It fails with the following error message. Return code = 65280 Error = No such file or directory I have ensured that C:/zip.exe files exists and is executable.

Error Code 65280 In Unix

I tried executing other system binaries like cmd.exe but ran into the same issue. My question is what could be causing this issue like i. some environment setting is wrong and interfering with the system api and hence it is not able to load the binary. ii. The $PATH variable in this environment is greater than 1024 characters. Is the length of this variable a concern or some paths set in this sftp error code 65280 variable is causing this issue thanks, PrakashComment on system perl api fails with exit code 65280 on Win 2003Download Code Replies are listed 'Best First'. Re: system perl api fails with exit code 65280 on Win 2003 by BrowserUk (Pope) on May 22, 2013 at 14:18UTC I have ensured that C:/zip.exe The system code simply means that the program did not run. The error code tells you that the command could not be found. The reason is that the command shell expects forward slashes (\) not backslashes (/) in paths. The reason is that the command shell expects backslashes (\) not forward slashes (/) in paths. Change my $zipExec='C:/zip.exe'; to my $zipExec='C:\\zip.exe'; and your command will probably work. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. [reply][d/l][select] Re^2: system perl api fails with exit code 65280 on Win 2003 by karlgoethebier (Parson) on May 22, 2013 at 15:24UTC «The reason is that the command shell expects forward slashes (\) not backslashes (/) in paths.» But BrowserU

New? Today's Posts FAQ Rules Guidelines Search Advanced Search Forum :: Server side development Perl/ CGI "system" call fails in perl CGI script - error code 65280 If this is error code 65280 in informatica your first visit, be sure to check out the FAQ by clicking the link

65280 Cpt

above. You may have to register before you can post: click the register link above to proceed. To start viewing

Ssh Return Code 65280

messages, select the forum that you want to visit from the selection below. Enjoy an ad free experience by logging in. Not a member yet? Register. Results 1 to 7 of 7 Thread: "system" http://www.perlmonks.org/?node_id=1034752 call fails in perl CGI script - error code 65280 Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Rate This Thread Current Rating Excellent Good Average Bad Terrible 10-05-2005,08:44 PM #1 aquilon View Profile View Forum Posts New to the CF scene Join Date Oct 2005 Posts 3 Thanks 0 Thanked 0 Times in 0 Posts "system" call fails in perl CGI script http://www.codingforums.com/perl-cgi/69624-system-call-fails-perl-cgi-script-error-code-65280-a.html - error code 65280 It is the first time I am trying to use a Perl "system" call in a CGI script. The script is running on Windows XP. Here's the fragment of the code: sub errout { my $msg = $_[0]; print "Content-type: text/html\n\n"; print "\n"; print "Error: " . $msg . "\n"; print ""; } ... my $indir = '\Contracts\FieldData'; unless(chdir $indir) { errout("Cannot cd to $indir: $!"); exit; } my @comargs = ('COPY', '3617_CROSS_BEND_RD_PLANO.txt', '\Contracts\ContractFiles\test.txt'); system(@comargs) == 0 or errout("system @comargs failed: $?:$!"); When I run that script in a browser I receive the following error: Error: system COPY 3617_CROSS_BEND_RD_PLANO.txt \Contracts\ContractFiles\test.txt failed: 65280:No such file or directory Of course, all folders and the file to copy do exist, and the "copy" command works fine in the command prompt window. I looked for answers on the Net, but unfortunately didn't find any explanations. BTW, I have been using "system" calls in a number of my non-CGI Perl scripts, and never had a problem with them. Thanks in advance. Reply With Quote 10-05-2005,09:21 PM #2 FishMonger View Profile View Forum Posts Super Moderator Join Date May 2005 Location Southern tip of Silicon Valley Posts 3,329 Thanks 2 Thanked 232

code 65280. Posted on 2007-11-26 16:54:19 by lbo_user Hi all, I've had a look around but haven't managed to find any info on this particular problem. Maybe I was searching for the wrong stuff. Anyway, I have a script that runs the flac and lame tools to convert between http://board.issociate.de/thread/468485/Failed-with-exit-code-65280.html FLAC and MP3. Within the script the variable $convert_command contains the full piped command with file http://coding.derkeiler.com/Archive/Perl/comp.lang.perl.misc/2007-11/msg01144.html pathnames etc. This is called using system() but it always fails with exit code 65280 and the warning, "Can't init outfile 'my_outfile'". However, when I run the same command from the shell everything is fine and the file is written. The destination is writable by all. There don't seem to be any permissions problems. What am I missing? Thanks. Report this message #2: code 65280 Re: Failed with exit code 65280. Posted on 2007-11-26 17:48:43 by xhoster lbo_user wrote: > Hi all, > > I've had a look around but haven't managed to find any info on this > particular problem. Maybe I was searching for the wrong stuff. > Anyway, I have a script that runs the flac and lame tools to convert > between FLAC and MP3. > > Within the script the variable $convert_command contains the full > piped command code 65280 in with file pathnames etc. This is called using system() > but it always fails with exit code 65280 and the warning, "Can't init > outfile 'my_outfile'". However, when I run the same command from the > shell everything is fine and the file is written. The destination is > writable by all. There don't seem to be any permissions problems. > What am I missing? You are missing the Perl code that shows us what you are doing. Xho -- -------------------- http://NewsReader.Com/ -------------------- The costs of publication of this article were defrayed in part by the payment of page charges. This article must therefore be hereby marked advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate this fact. Report this message #3: Re: Failed with exit code 65280. Posted on 2007-11-26 18:44:29 by Sherm Pendley lbo_user writes: > Within the script the variable $convert_command contains the full > piped command with file pathnames etc. This is called using system() > but it always fails with exit code 65280 and the warning, "Can't init > outfile 'my_outfile'". However, when I run the same command from the > shell everything is fine and the file is written. The destination is > writable by all. There don't seem to be any permissions problems. > What am I missing? The error message isn't a Perl error - it's coming from the tools you're calling. Without s

piped command with file pathnames etc. This is called using system() but it always fails with exit code 65280 and the warning, "Can't init outfile 'my_outfile'". However, when I run the same command from the shell everything is fine and the file is written. The destination is writable by all. There don't seem to be any permissions problems. What am I missing? The error message isn't a Perl error - it's coming from the tools you're calling. Without seeing your code it's difficult to do more than guess, but one thing I would do is double-check the value of $convert_command, to make absolutely certain it's right. With Perl and shells interpolating variables into strings, and sharing many of the same escape sequences in quoted string constants, that's an easy place for bugs to sneak in. Also, the return value from system() isn't just the return value of the called command; it's that, plus some other stuff. You need to jump through a few hoops to get the actual exit status, as shown in "perldoc -f system": You can check all the failure possibilities by inspecting $? like this: if ($? == -1) { print "failed to execute: $!\n"; } elsif ($? & 127) { printf "child died with signal %d, %s coredump\n", ($? & 127), ($? & 128) ? 'with' : 'without'; } else { printf "child exited with value %d\n", $? >> 8; } Once you get the real exit code from the tool you're calling, then you can find the meaning of that code (and the accompanying "Can't init" message) in the tool's docs. sherm-- -- WV News, Blogging, and Discussion: http://wv-www.com Cocoa programming in Perl: http://camelbones.sourceforge.net . Follow-Ups: Re: Failed with exit code 65280. From: lbo_user References: Failed with exit code 65280. From: lbo_user Prev by Date: Re: Google bad, Yahoo good Next by Date: Re: Google bad, Yahoo good Previous by thread: Re: Failed with exit code 65280. Next by thread: Re: Failed with exit code 65280. Index(es): Date Thread Flag as inappropriate (AWS) Security UNIX Linux Coding Usenet ArchiveAboutPrivacyImprint coding.derkeiler.com >A