Hi Henrik.

I'm happy to say that it seems to be working.

Thank you very much for your efforts.

Approximatly when can I expect version 6.0.7 to be properly released?

Thanks for the feedback. It will probably be another week before that.

---

Hello again.

I'm sorry to say that further testing has proven that our Access macros still doesn't work when executing them from Visualcron Office macro function.

We have also tried to execute them from the task Execute with the same result.

When we run them from Access or execute them from the command line it works perfectly fine.

Have you managed to fix the problem with the quit command in Access macros?
Or do you have any suggestions on an alternative way of enfing the macros?

Regards.

/Jesse

Hello again.

I'm sorry to say that further testing has proven that our Access macros still doesn't work when executing them from Visualcron Office macro function.

We have also tried to execute them from the task Execute with the same result.

When we run them from Access or execute them from the command line it works perfectly fine.

Have you managed to fix the problem with the quit command in Access macros?
Or do you have any suggestions on an alternative way of enfing the macros?

Regards.

/Jesse

Are you still running macros with the quit command? Quit will never return a positive value. Did you try just to output a value in the macro?

---

I just tried to run a macro that is just opening a table and it doesn't work.
I can run it from a cmd line but not from Visualcron.
That test might not be trustworthy since I'm not an expert on Access to say the least.

My collegue though is working with Access a lot and he set up a macro that is importing a table and it gets the same result as before. It works from the command line but not from visualcron.

I just tried to run a macro that is just opening a table and it doesn't work.
I can run it from a cmd line but not from Visualcron.
That test might not be trustworthy since I'm not an expert on Access to say the least.

My collegue though is working with Access a lot and he set up a macro that is importing a table and it gets the same result as before. It works from the command line but not from visualcron.

I think you should start with the most simple example - that is not using quit. Many errors can occur if you work against a table. For example, finding the file.

---

Both tests that I mentioned earlier is local actions without quit command.
It cannot be much more simple than that.

I have gone through the trusted settings in Access.
The user that runs the Visualcron job can run the macro iteractive in Access, and is local administrator.

I get the folowing Output (stderror):
System.Runtime.InteropServices.COMException (0x800A07D1): You canceled the previous operation.
at Microsoft.Office.Interop.Access.DoCmd.RunMacro(Object MacroName, Object RepeatCount, Object RepeatExpression)
at TaskOfficeMacro.Main.RunAccessMacro() - maybe Microsoft Office is not installed? This Task requires Microsoft Office being installed.
Exception in Task: Non zero exit code
Exception in Task: System.Runtime.InteropServices.COMException (0x800A07D1): You canceled the previous operation.
at Microsoft.Office.Interop.Access.DoCmd.RunMacro(Object MacroName, Object RepeatCount, Object RepeatExpression)
at TaskOfficeMacro.Main.RunAccessMacro() - maybe Microsoft Office is not installed? This Task requires Microsoft Office being installed.
Exception in Task: Non zero exit code

Thanks for the feedback. We did some changes regarding Credentials. Download this version:

http://www.visualcron.co....aspx?g=posts&t=2225 

The Access Task requires a local user (or domain user). Create one and make sure that "Local user" and "Load profile" is checked. Select that user.

Please let us know if this works better.

---

It seems to work.

Lets wait for my developer to test it, before we celebrate.

I'm hopeful though.

Thanks for now, I will get back to you with more feedback after further tests.

/Jesse

It seems to work.

Lets wait for my developer to test it, before we celebrate.

I'm hopeful though.

Thanks for now, I will get back to you with more feedback after further tests.

/Jesse

Thanks for your patience - we will await feedback from you.

---

Hi Jesse,

just wanted to check if you were able to confirm if the new version works better. Thanks!

---

Hi Henrik.

From my perspective it works just fine.
But I have to wait until the beginning of next week for my developer to have a look at it.

I hope for your patience and wish you a nice weekend.

/Jesse

Hello again.

I can now tell you that the fix for Office macros works just fine.

Thank you for your help.

/Jesse

Thanks for the feedback and patience in this case.

---

Hello again.

I'm sorry to say that during the weekend we have installed Microsoft security patches according to Microsofts recommendations.
And after that the Access macro task doesn't work anymore. We got the same problem as we got before installing Visualcron 6.0.7.

I tried to reinstall the VC 6.0.7 patch but it didn't help.

The Microsoft patches we installed was KB2597170 and KB2597091.


Regards

/Jesse

1. What error do you get?
2. have you made sure that you run the Task with a Credential with setting "Local logon" and "Load profile"?

---

Thank you. You are a star.

For some reason those check boxes had been unchecked.
I checked them and it worked again.

/Jesse

Glad it was resolved!

---

Hello again.

What settings am I supposed to use when running Access macros in Visualcron 6.0.8?

I get the same problem as before after upgrading.

I get Exception in task: Non zero exit code.
And after that I get
Task exited with code :-1073741502 (Error description was not found)

In credentials I have both "Local" and "Load profile" ticked.
I have tried other combinations but with the same result.

Regards

/Jesse

Hi again.

I managed to sort it out.

Thanks.

/Jesse

We did some research about exit code -1073741502 and we found 2 possible solutions:

1. Go to administrative tools->Local security policy. Set SYSTEM user with Logon as batch Job. Reboot. Try Task again.
2. Disable UAC. Reboot computer. Try Task again.

---

We have modified this Task for 8.1.2 so there is no need for UAC disabling. So if you encounter this again please test this beta or official when released: http://www.visualcron.co....aspx?g=posts&t=6721 

---