Hello all,
Trying to execute a program but I get the following error message:
...
On Win64 if trying to run a system proccess try bypassing file RP_WIN64PROCESS or referencing SYS_NATIVE
How can I do this? Allready tried
Let>RP_WIN64PROCESS=1
and
Let>RP_WIN64PROCESS=0
with no success.
Also tried running the program from a windows shell.
This works fine.
help
Can not execute a program
Moderators: JRL, Dorian (MJT support)
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
There is no error message in your post.
What program are you trying to run? You don't say? Can you provide your code? Can you tell us the name of the executable and its path?
What program are you trying to run? You don't say? Can you provide your code? Can you tell us the name of the executable and its path?
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
- Grovkillen
- Automation Wizard
- Posts: 1132
- Joined: Fri Aug 10, 2012 2:38 pm
- Location: Bräcke, Sweden
- Contact:
I just got this error as well... this morning I could run the below code with no issues. After I messed around with the script I got this error and I cannot make any Run> command pointing to a .EXE file to run. The RP_WIN64PROCESS will nto fix it either. Any ideas?

EDIT: I've done some testing and complied scripts from before this issue will fire up .EXE files with no problem so it must be something within MS causing it. Darn it, this is not the type of slow down I need... what did I do?
EDIT2: I've tested to run the .EXE file from D:\test.exe and it worked. My K: is a mapped user drive... could this be the problem? The weird part is that I DID run from my K-drive before. Anyway.. I may use this workaround for now. But it would be nice to get it back the way it was before.

EDIT: I've done some testing and complied scripts from before this issue will fire up .EXE files with no problem so it must be something within MS causing it. Darn it, this is not the type of slow down I need... what did I do?
EDIT2: I've tested to run the .EXE file from D:\test.exe and it worked. My K: is a mapped user drive... could this be the problem? The weird part is that I DID run from my K-drive before. Anyway.. I may use this workaround for now. But it would be nice to get it back the way it was before.
- CyberCitizen
- Automation Wizard
- Posts: 724
- Joined: Sun Jun 20, 2004 7:06 am
- Location: Adelaide, South Australia
- Grovkillen
- Automation Wizard
- Posts: 1132
- Joined: Fri Aug 10, 2012 2:38 pm
- Location: Bräcke, Sweden
- Contact:
-
- Newbie
- Posts: 3
- Joined: Wed Jan 06, 2021 11:12 am
Re: Can not execute a program
was having the same problem. app would not run from the g drive.
Let>RP_ADMIN=1
worked when i added the above code
Let>RP_ADMIN=1
worked when i added the above code