Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Tom23
  •  Tom23
  • No customer Topic Starter
2017-06-23T09:41:35Z
Hello,


I have multiple jobs set-up that involve running a office macro as one of the tasks (Access & Excel mostly) many of these have been running for over a year without issue - recently they have all failed on the step involving an office macro and return the same error message

08:00:58: Server->Execute path: C:\Program Files (x86)\VisualCron\\TaskOfficeMacrox86.exe
08:00:58: Server->Executing Task process
08:00:59: Server->Executing Task process exited with exit code: -1073741502

Does anyone know what this exit code means?

Cheers,
Tom
Sponsor
Forum information
Support
2017-06-23T15:33:23Z
This is a permissions error. Try the following;

1. enable Extended debugging in Server settings
2. edit the Credential that you use an select CreateProcessAsUserW
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Tom23
  •  Tom23
  • No customer Topic Starter
2017-06-26T08:52:36Z
Hi Henrik,

I have updated the credentials as suggested and made sure they are the credentials running on the job but still get the same error.

VC Credentials.png

I notice the server execute path contains a \\ for the office macro task which is not a valid file path - Is it possible to change this somewhere within VC?

Cheers,
Tom
Support
2017-06-26T09:20:54Z
Originally Posted by: Tom23 

Hi Henrik,

I have updated the credentials as suggested and made sure they are the credentials running on the job but still get the same error.

VC Credentials.png

I notice the server execute path contains a \\ for the office macro task which is not a valid file path - Is it possible to change this somewhere within VC?

Cheers,
Tom



What exact path did you see?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Tom23
  •  Tom23
  • No customer Topic Starter
2017-07-14T14:45:45Z
Hi Henrik,

Sorry for not replying - rebooting server and visual cron fixed the issue!

Cheers,
Tom
Support
2017-07-19T08:11:35Z
Thanks for the feedback!
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top