Hi,

I'm evaluating VisualCron for a client. I've found it pretty easy to set up, but it errors on running a task which calls an access macro via 'office Macro'.

I've added credentials. The macro runs fine manually.

It's on a Windows 2012 r2 box. It generates the following errors (In event viewer).

Faulting application name: conhost.exe, version: 6.3.9600.17415, time stamp: 0x5450410b
Faulting module name: USER32.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000142
Fault offset: 0x00000000000ecdd0
Faulting process id: 0x9a4
Faulting application start time: 0x01d24b29bd0933b0
Faulting application path: C:\Windows\system32\conhost.exe
Faulting module path: USER32.dll
Report Id: fab5bfd8-b71c-11e6-8148-12cfe79d097b
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: TaskOfficeMacro.exe, version: 1.0.0.0, time stamp: 0x58185332
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000142
Fault offset: 0x00000000000ecdd0
Faulting process id: 0xdb0
Faulting application start time: 0x01d24b29bd0933b0
Faulting application path: D:\VisualCron\TaskOfficeMacro.exe
Faulting module path: KERNELBASE.dll
Report Id: fabf4902-b71c-11e6-8148-12cfe79d097b
Faulting package full name:
Faulting package-relative application ID:

Any information or ideas would be great. Thank you.

Regards, Ed.

Please add screenshot of Task settings.

---

Hi Henrik,

Thanks for your reply. Here are the screens.







Ed.

1. have you install Access locally on the same machine?
2. have you installed 32 or 64 bit version of access?
3. I noticed there is a blank space in the macro name. Please open the macro from the document. Normally it is written like document/class.macroname.

---

Hi Henrik,

Thanks for your reply

1. Yes, access is installed on the same machine.
2. It is 64bit. I have tried both 64 & 32 bit settings (I know the 32 bit was checked).
3. the macro is named with a space. I've added it [to VisualCron] as I think VBA wants it. I'll read up about macro naming, but if you have a link available to any resource for VisualCron and macr names, that would be very helpful.

Thanks.

Ed.

Please try the following:

1. enable Extended debugging in server settings
2. Edit the Credential that you use and change to "CreateProcessAsUserW"
3. try again

---

Thanks Henrik. I'll give it a try and let you know what happens.

Regards, Ed.

Hi Henrik,
Setting credentials to "CreateProcessAsUserW" has resolved the errors reported earlier.
The job runs, I get positive impersonation stuff in the event security audit logs, but the process in the macro isn't carried out. If I run the macro from the Access UI, it all works ok.
I'll continue to try things but if you have any further ideas of suggestions or need me to try anything, please let me know.
Regards, Ed.

Hi Henrik,
Setting credentials to "CreateProcessAsUserW" has resolved the errors reported earlier.
The job runs, I get positive impersonation stuff in the event security audit logs, but the process in the macro isn't carried out. If I run the macro from the Access UI, it all works ok.
I'll continue to try things but if you have any further ideas of suggestions or need me to try anything, please let me know.
Regards, Ed.

Yes, I think you need to add line by line debugging in the access macro to see which line is causing the problem.

---