How to stop Security Warning dialog

[agharib]

We are using

oWsh = CREATEOBJECT("wscript.shell")
oWsh.Run("BatchFile.Bat", 3, .T.)

to run a batch file from a .PRG. Works fine on 32 bit OS. On 64 bit, we get the Open File - Security Warning; with Run and Cancel buttons.
This process runs with a timer periodically; unattended. How can we disable this Security Warning screen from showing up.

Note:
We were using ShellExecute API, yet VFP does not wait until the batch run finishes; hence resorted to wscript.shell.

Adel

 

[Olaf Doschke]

I think the seurity warning is not from running wscrip.shell, but the bat file or what the bat file executes. And that must be solved in trusting what is run.

The two steps you can do are shown here:

http://www.sevenforums.com/tutorials/124367-open-file-security-warning-unblock-file.html

Bye, Olaf.

 

[Mike Lewis]

Adel,

I suggest you try running the file interactively, rather than through the scripting host. If the same security message appears, you can eliminate your call to oWsh.Run as the source of your problem (in which case the page referenced by Olaf will tell you how to deal with it).

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[agharib]

Thanks Mike and Olaf for your responses.
I should add that the batch file we're trying to run gets created on the fly by forming its content as a string, then do a

STRTOFILE(mCommandString, "\\somefolder\BatchFile.BAT")

The solutions at the URL Olaf mentioned is for Windows 7. We are runninig Windows Server 2008 R2 - on the Security Warning dialog
, there is no "Always ask before opening this file" check box! For Windows Server 2008 R2, we tried gpedit.msc, then Select
User Configuration | Administrative Templates | Windows Components | Attachment Manager, and added *.bat to the Inclusion
list for moderate risk file types setting. Did not work either.

Mike - Batch fie works fine without the security message showing up.


Adel

 

[JRB-Bldr]

the batch file we're trying to run gets created on the fly by forming its content as a string

BUT once you have created the BAT file, have you suspended your application with a SET STEP ON?

STRTOFILE(mCommandString, "\\somefolder\BatchFile.BAT")
SET STEP ON

And then executed the BAT file manually from your Windows CMD window?

As Olaf & Mike have suggested, if you were to do so you could test the validity of the BAT execution without involving VFP or Windows Scripting.

Then, if the warning message were still being generated, it would be coming from somewhere else.

Good Luck,
JRB-Bldr

 

[agharib]

JRB-Bldr
And then executed the BAT file manually from your Windows CMD window?


In the last line of my previous post I've indicated that the Batch file works fine without the security message showing up; when triggered from CMD window.


Adel

 

[JRB-Bldr]

Oops.

Sorry I missed that.

Good Luck,
JRB-Bldr

 

[Dan Freeman]

Instead of executing the bat file directly, have you tried using "RUNAS" to execute the command with elevated privileges?