I reinstalled VisualCron after replacing my computer. I get an "Unhandled error ... the specified executable is not a valid Win32 application" message when trying to start an Excel(.xlsm) file with some visual basic code in it, using the c:\Execute command.

It used to work. I also tried to start a .xls version of the Excel file and got the same error What's wrong?

1. What is the c:\Execute command?
2. is your system 32 or 64 bit?
3. have you tried the Office Macro Task?

---

1. What is the c:\Execute command?
2. is your system 32 or 64 bit?
3. have you tried the Office Macro Task?

1. By "c:\Execute" I mean the task type you choose when you add a task.
2. I'm testing on a 32 bit system (but I get the same msg on a Win7 64bit).
3. I looked at the office Macro Task, but didn't test it. It wants me to specify a specific macro. I suppose I could try that, but I't seems like I should be able to start an excel file.

Thanks for responding.

George

While the error is a bit unknown I must clarify some things:

1. Excel is an application that requires desktop interaction unless specified else or using Tasks that perform background operations - like the Office Macro Task
2. As Excel by itself needs the desktop it will probably act strange when it is launched by the SYSTEM user (which VisualCron uses) on a desktop (0) where no one is logged in at
3. if you don't want to use the background Tasks for Excel you could try to set the Task to run in foreground (main settings of Task). Please try that.

---

While the error is a bit unknown I must clarify some things:

1. Excel is an application that requires desktop interaction unless specified else or using Tasks that perform background operations - like the Office Macro Task
2. As Excel by itself needs the desktop it will probably act strange when it is launched by the SYSTEM user (which VisualCron uses) on a desktop (0) where no one is logged in at
3. if you don't want to use the background Tasks for Excel you could try to set the Task to run in foreground (main settings of Task). Please try that.

I changed the execution environment to foreground, and the error message went away, but Cron's popup messages tell me that the task completed immediately after it started. No excel window appeared.

A task set up the same way to run notepad.exe seemed and the notepad window opened, so that worked. I didn't try to open a specific .txt file with the notepad, so the test is not quite the same as trying to open a specific .xls or .xlsx file.

I can type excel.exe as a "run..." windows menu item, and it starts excel, but if I put excel.exe in as a chron task to run in the foreground, no excel window opens.

Thanks for your continuing help,
George Wolfe

We recently installed version 6.2.2 and now getting this error on all Office macro tasks. Error message is: Unhandled error when trying to start process: %1 is not a valid Win32 application.

These are MS Access macros that used to work just fine being called from VisualCron.

Help!! 🤬

We recently installed version 6.2.2 and now getting this error on all Office macro tasks. Error message is: Unhandled error when trying to start process: %1 is not a valid Win32 application.

These are MS Access macros that used to work just fine being called from VisualCron.

Help!! 🤬

When you say you recently installed 6.2.2, I assume you mean upgraded a previous version to 6.2.2 ?

I'm curious, was your VisualCron service set to run as a different user previously and now after upgrading its defaulted back to 'SYSTEM'? Just reading through this old post, that could be a likely cause.

Verify that the service is running as the same ID it was running as before(unless of course it was SYSTEM), assuming you upgraded and this wasn't a fresh install.

Brian

As bbusse says I think it has something to do with either the user that runs the VisualCron service or that no Credential is selected.

---