Call exe file in AX 2009 batch job

(0) Share

Report

Posted on by Community Member

I have a job calling external exe file for C# console application and this is working fine on the client side. I scheduled this job to run over night on the server and AX job is running correctly as per the resulted log but the exe is not called and I guess that because there is no user logged in at that time. Please help how can I make it called successfully to complete the required task?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

You most likely have used WinAPI::shellExecute to run the file, and that is a client-bound process. Batch jobs are running server-side, for which you have the WinAPIServer class.

This has already been documented, along with the solution:

blogs.msdn.microsoft.com/.../how-to-execute-an-external-process-from-a-batch

Please mark the answer with the checkbox to verify and resolve the topic.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Unfortunately, it doesn't work.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (1)

Report

Explain what you did and what does not work, since my remote mind-reading capabilities are very limited :)

Also explain what did you try to make it work, i.e. following the instructions on the error messages, debugging and stepping through the code to identify which part of the process might be incorrect, etc.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Here is the code to be run on the batch running on the server over night

public void run()

{

int i = 0, j =0;

System.Diagnostics.Process process;

System.Diagnostics.ProcessStartInfo processStartInfo;

;

info("Export has been completed!");

if(ConsumeAXWS::write2eCODA())

info("Entries has been moved to eCODA!");

i = WinAPI::shellExecute("C:\\AX2eCODA\\AX2eCODA\\bin\\Debug\\AX2eCODA.exe");

if(i == 0)

{

//info("Exe didn't run");

new InteropPermission(InteropKind::ClrInterop).assert();

process = new System.Diagnostics.Process();

processStartInfo = new System.Diagnostics.ProcessStartInfo();

processStartInfo.set_FileName("C:\\AX2eCODA\\AX2eCODA\\bin\\Debug\\AX2eCODA.exe");

process.set_StartInfo(processStartInfo);

process.Start();

process.WaitForExit();

info("Exe ran server side");

}

else

info("Exe ran client side");

}

The program to be called is configured to write a log whenever it is called but here the program is not called with the batch.

I hope I'm clear now :)

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

I think execution stops at WinAPI since you are still calling a client-bound process server side. Comment that out and do CIL.

Also, do you have that executable available in the folder on the AX AOS instance that is acting as batch server? You could simply verify that https://community.dynamics.com/ax/b/faisalfareedaxlibrary/archive/2016/01/10/ax-2012-file-existance-check

Using a try-catch block to catch any errors would be useful too:

[View:https://msdn.microsoft.com/en-us/library/ee677495.aspx:750:50]

Was this reply helpful? Yes No
Martin Dráb 237,817 Most Valuable Professional on at

Like (0)

Report

You're still using WinAPI::shellExecute(), even after Vilmos explained why it can't work. Get rid of it.

Was this reply helpful? Yes No
Suggested answer

Chaitanya Golla 17,225 on at

Like (0)

Report

Hi,

Please refer the following:

(How to execute an external process from a batch)

blogs.msdn.microsoft.com/.../how-to-execute-an-external-process-from-a-batch

Community Discussion thread:

(Shell execute in server)

community.dynamics.com/.../143239

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I did what all of you advised and it didn't give errors but also the exe seems like not running; it doesn't take the usual action of its execution.

Was this reply helpful? Yes No