in reply to 65280 returned on system ( )

I'd suggest making sure you call your vbs file via a fully qualified path - OR the user account your webserver runs as doesn't have permission to execute the file.



--chargrill 
$,=42;for(34,0,-3,9,-11,11,-17,7,-5){$*.=pack'c'=>$,+=$_}for(reverse s
+plit//=>$*
){$%++?$ %%2?push@C,$_,$":push@c,$_,$":(push@C,$_,$")&&push@c,$"}$C[$#
+C]=$/;($#C
>$#c)?($ c=\@C)&&($ C=\@c):($ c=\@c)&&($C=\@C);$%=$|;for(@$c){print$_^
+$$C[$%++]}

[download]

Replies are listed 'Best First'.
Re^2: 65280 returned on system ( )
by rhymejerky (Beadle) on Jun 07, 2006 at 18:45 UTC
    I put the statement if (-e "file.vbs") in the script to check for the file existence and the script didn't complain about not finding it. I even tried to call the vbs directly from a web browser (http://localhost/file.vbs) and the browser prompt me to open or save that file, so I think it is finding the vbs file.
[reply]

      Being able to see the file is not the same as having permission to be able to execute it, or to call all the system APIs that it calls.

      To verify if this is a permissions problem, log onto the machine as the IIS user id (usually IUSR_<servername>), and then try running the vbs script from the command line.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
      That doesn't mean that IWAM_YOUR-COMPUTER-GOES-HERE can execute the vbs. Check 'script' permission in IIS manager.
[reply]
        Thanks!! You guy pointed me to the right direction. I checked the IIS config and the web pages were under the IUSR_<host> context. Apparently, this user's has all kinds of limitation. I tried to configure those web pages to run under my context and all worked.
[reply]
        If that files is opened remotely or being executed by any other program is also leads to get this error....
[reply]

In Section Seekers of Perl Wisdom