#188664 - 2008-07-10 05:06 PM
Simply can't seem to get a RUN command to work.
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
I purchased EZAudit software to get a weekly audit of PC's and software titles for compliance, and their user's guide says to enter this command in my KiXtart login script:
RUN "\\your_server_name\ezaudit\ezstart.exe /auto"
When I put that in, nothing happens. When run from a RUN command on an individual PC, the command is "\\server_name\ezaudit\ezstart.exe" /auto, and that works fine. If I try to enter it as above in the login script, the login fails with an error. Finally, when I try to encase the above command in single quotes, ('"\\server_name\ezaudit\ezstart.exe" /auto') nothing happens.
Any ideas?
|
Top
|
|
|
|
#188665 - 2008-07-10 05:16 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Rick_Folsom]
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Welcome,
What is "an error"? You need to tell us what "an error" is. It is like saying my car has a problem.. What is "a problem"?
What you can do is the following:
Do your users have the ability to access \\your_server_name\ezaudit if they run it from a command-line?
You need to make sure they have have execute permissions to that share called "ezaudit"..
If you are able to get there, then you may need to throw a couple of macros in your script like @ERROR and @SERROR to have it pipe back what the problem is.
HTH,
Kent
|
Top
|
|
|
|
#188667 - 2008-07-10 05:47 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Kdyer]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
Pop-up Box
KiXtart ERROR: Error in expression.! Script: C:\WINNT\System32\yupo.kix Line: 98
That's what happens when the command entered in the script looks exactly like this: Run "\\yuponas\ezaudit\ezstart.exe" /auto
Yes, all users can run the command from their own PC's and have explicit modify etc. permission to the folders.
|
Top
|
|
|
|
#188671 - 2008-07-10 06:18 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Les]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
I've tried the COMSPEC shell routine and that fails (sorry, don't remember the message and probably won't retry it), and I've tried creating it as a CMD and running the CMD, all to no avail. Clueless on the "pushing the command to the RunOnce reg key instead" comment. The command works in quotes without the /auto, but then requests them to save the file on their own PC, which really does me no good.
I undestand that this is probably a failure on the EZAudit side, but I was hoping someone could tell me why
Run '"\\yuponas\ezaudit\ezstart.exe" /auto'
isn't a valid command in KiXtart, or how to turn
run "\\yuponas\ezaudit\ezstart.exe" /auto
into a command that will run through KiXtart.
|
Top
|
|
|
|
#188676 - 2008-07-10 08:05 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Allen]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
Thanks for your assistance all. After adding the compspec part, I get a message when the script runs telling me the command ran, but it still doesn't run the actual program. Strange stuff. I'll just continue walking to the PC's I guess.
|
Top
|
|
|
|
#188677 - 2008-07-10 08:13 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Rick_Folsom]
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
Did you try the options?
run '%comspec% /c "\\yuponas\ezaudit\ezstart.exe" /auto'
?@ERROR
?@SERROR
Or..
SHELL '%comspec% /c "\\yuponas\ezaudit\ezstart.exe" /auto'
?@ERROR
?@SERROR
Or..
SHELL '%comspec% /c \\yuponas\ezaudit\ezstart.exe /auto'
?@ERROR
?@SERROR
Or..
RUN '%comspec% /c \\yuponas\ezaudit\ezstart.exe /auto'
?@ERROR
?@SERROR
Or..
RUN '%comspec% /c /e:on \\yuponas\ezaudit\ezstart.exe /auto'
?@ERROR
?@SERROR
Or..
$EXEPATH="\\yuponas\ezaudit\ezstart.exe"
RUN '%comspec% /c '++' /auto'
?@ERROR
?@SERROR
HTH,
Kent
|
Top
|
|
|
|
#188678 - 2008-07-10 09:45 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Kdyer]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
run '%comspec% /c "\\yuponas\ezaudit\ezstart.exe" /auto' No error messages, no audit.
SHELL '%comspec% /c "\\yuponas\ezaudit\ezstart.exe" /auto' CMD.EXE was started as the above path in current directory, UNC not supported
SHELL '%comspec% /c \\yuponas\ezaudit\ezstart.exe /auto' Same as above
RUN '%comspec% /c \\yuponas\ezaudit\ezstart.exe /auto' No error, no audit.
RUN '%comspec% /c /e:on \\yuponas\ezaudit\ezstart.exe /auto' No error, no audit.\
$EXEPATH="\\yuponas\ezaudit\ezstart.exe" RUN '%comspec% /c '++' /auto' Flashed by too fast to see, but there was some type of memory error.
|
Top
|
|
|
|
#188705 - 2008-07-11 02:41 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Glenn Barnas]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
First to Kent. I have tried those two forms, with the first one being copied directly from their site, with modification to your_server_name, of course, with no luck. And on my system, SHELL in the logon script always causes an error.
To Glenn, I did something very similar to what you show. I found it in one of the forums (fori, fora?) but I don't think I tried the comspec peice, just created the CMD to be '"\\yuponas\ezaudit\ezstart.exe" /auto' and ran the command. The message "about to run \\yuponas\...." shows up fine, but again, the actual program never runs.
Some explanation of the environment: the logon script runs on our domain controller, and just before the attempt to run ezaudit, the script adds yuponas as a mapped drive. The messages saying yuponas has been added always show up. The next command is the run.
Question about the KiXtart script: could the issue be about where the two objects reside? I am assuming that the script basically runs locally on the PC that's logging on, which has access to yuponas by the time the run command is supposed to be executed. Nothing in the ezaudit literature says I have to have any executable on the PC's themselves. Just kind of rambling here, but ezaudit folks say they've got 10,000 users and have very few calls to their support desk, so I'm missing something here.
|
Top
|
|
|
|
#188710 - 2008-07-11 09:03 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Glenn Barnas]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
Glenn:
Basically the same result. Using the SHELL causes the error listed previously about CMD.exe executed, UNC not supported. The error and result log files were created, but empty. I'll try to execute it from the mapped drive vs. the UNC.
|
Top
|
|
|
|
#188711 - 2008-07-11 09:31 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Rick_Folsom]
|
Rick_Folsom
Fresh Scripter
Registered: 2008-04-01
Posts: 8
|
Used the command y:\ezaudit\ezstart.exe annd the error log said path not found.
I'd like to find someone that uses ez-audit and KiXtart and see what they do, because this just isn't worth the struggle.
|
Top
|
|
|
|
#188714 - 2008-07-11 11:52 PM
Re: Simply can't seem to get a RUN command to work.
[Re: NTDOC]
|
Glenn Barnas
KiX Supporter
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
|
The error message is very helpful, actually.
When you say "Y:\folder\file.exe", you tell the O/S to run "file.exe", which is found in the path "Y:\folder". Just because you tell the O/S where the file that you want to run is , it doesn't mean it will go there and then run the file, it just means it will run that file while sitting right where it is (in it's favorite easy chai - um - folder.
The message is most likely coming from the installer, not the OS. So - get a little more complex - Create a batch file to run the installer - EasyStart.BAT. It should look something like
@Echo Off
Y:
CD \EasyAudit
.\EasyStart.exe (plus any needed args) >C:/temp/install.log 2>C:\Temp\error.log
This assumes that you mapped the drive to Y: in Kix before running this command via Shell "Y:\EasyAudit\EasyStart.bat"
If that works, you can think about doing these commands in Kix if you wish, but using the bat file will let you test outside of kix. That's important when debugging and you're not sure if the problem is Kix, the environment, or the application you're launching.
I had an issue this past Tuesday where an install failed because there was a space in the path defined by %TEMP%. Spent a while looking at my Kix script before I started running the commands manually. Really tough, because no error wass generated, the process just exited silently. Basically, it pays to break your logic into managable chunks, even outside of your core process.
Glenn
_________________________
Actually I am a Rocket Scientist!
|
Top
|
|
|
|
#188723 - 2008-07-13 01:42 PM
Re: Simply can't seem to get a RUN command to work.
[Re: Les]
|
Arend_
MM club member
Registered: 2005-01-17
Posts: 1894
Loc: Hilversum, The Netherlands
|
How About:
$objShell = CreateObject("WScript.Shell")
$objShell.Run("\\yuponas\ezaudit\ezstart.exe /auto")
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 557 anonymous users online.
|
|
|