The error "Access is denied" is being frequent on Visual Cron.
It's a huge problem to me because I need to put the process to execute manually.
Sometimes the task works well and sometimes not.

I really don't know the reason but after 2 or 3 times the task works well.
I guess it's not a credential problem.

Task type = Execute
I'm using an executable in the server A that connect to another server B (sql server).
I'm only receiving the message Access is Denied.
Any thoughts about this problem?

There isn't any other information in VC (only Access is Denied.).
Is there a path in the VC that log what exactly is happenning?


Best Regards,
Fernando

The question is where the access denied come from. Is it from logging on to the SQL server or other?

Do you have the source for the exe so you can verify this?

Can't you use the SQL Task?

---

The question is where the access denied come from. Is it from logging on to the SQL server or other?

Do you have the source for the exe so you can verify this?

Can't you use the SQL Task?

I don't have the source for the exe.
I can't use the SQL task because it's an executable.
I was reviewing a log generated by Visual Cron and I've seen the following error:
12/29/2010 5:32:38 AM Debug Saving Jobs
12/29/2010 5:39:09 AM Err Task "IMPORT_DAILY" exited with code: 5(Access is denied.)
12/29/2010 5:39:09 AM Err Task "IMPORT_DAILY" exited with code: 5(Access is denied.)
12/29/2010 5:39:09 AM Debug Process status - About to raise TaskCompleted (192)
12/29/2010 5:39:09 AM Info Task completed: IMPORT_DAILY
12/29/2010 5:39:10 AM Info Task started: Error Import WalMart Sul
12/29/2010 5:39:13 AM Info Task completed: Error Import WalMart Sul
12/29/2010 5:39:13 AM Info Job completed: Import Files - Daily
12/29/2010 5:39:43 AM Debug Saving Jobs

I don't know what the Executable does but you said it connected to an SQL server. That is why I suggested using the SQL Task - to do the same thing as the executable but with less problems - and faster.

The problem according to the log is not logging on using the Credential but something that the code does. I guess it does not do it every time as you don't get the problem every time.

Try changing "Run with managed" instead of "Run with API".

---

I don't know what the Executable does but you said it connected to an SQL server. That is why I suggested using the SQL Task - to do the same thing as the executable but with less problems - and faster.

The problem according to the log is not logging on using the Credential but something that the code does. I guess it does not do it every time as you don't get the problem every time.

Try changing "Run with managed" instead of "Run with API".

Hi Henrik,
Unfortunatelly, I only have the executable. I don't what i have to put to the Sql task.
I will try the option "Run with managed" and I'll let you know.....
Thanks
Fernando

I don't know what the Executable does but you said it connected to an SQL server. That is why I suggested using the SQL Task - to do the same thing as the executable but with less problems - and faster.

The problem according to the log is not logging on using the Credential but something that the code does. I guess it does not do it every time as you don't get the problem every time.

Try changing "Run with managed" instead of "Run with API".

Hi Henrik,
Unfortunatelly, I only have the executable. I don't what i have to put to the Sql task.
I will try the option "Run with managed" and I'll let you know.....
Thanks
Fernando

Hi Henrik,
I've tried the idea "Run with managed" without success. Do you have any other idea?

Regard,
Fernando

Last option would be to run the Task as a Foreground Task - to see if that works. You control this on the main settings of the Task.

---