Execute Arguments Length - VisualCron

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

Welcome Guest! To enable all features please Login or Register.

mholthouse
Paid support Topic Starter

2010-10-04T15:07:17Z

Is there a maximum length of arguments when using the execute task? I have a reporting program that is completely command line driven. The arguments for the particular task are pretty long. Arguments below. I can get it to run if I cut down the arguments, otherwise it gives me Error 1783 Bad Data received by stub. I am on version 5.6.9.

Edited by user 2011-02-15T00:10:32Z | Reason: Not specified

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Support
Official support

2010-10-04T20:26:41Z

The maximum length supported is 2080 characters. But perhaps there is something wrong with the argument. Try writing it to a file with File Write Task to see that you get the correct values.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

mholthouse
Paid support Topic Starter

2010-10-04T21:07:09Z

Enumerated out, the command seems to only be 1232 characters. I am able to run it fine if I run:

Is the error I am getting the error I would get if it is too long? Also, is "File Write Task to" a function of visualcron?

Support wrote:
The maximum length supported is 2080 characters. But perhaps there is something wrong with the argument. Try writing it to a file with File Write Task to see that you get the correct values.

Edited by user 2011-02-15T00:12:05Z | Reason: Not specified

Support
Official support

2010-10-04T21:09:42Z

mholthouse wrote:

Is the error I am getting the error I would get if it is too long?

Probably not. I believe the error is from your exe because something is wrong in the argument.

mholthouse wrote:
Also, is "File Write Task to" a function of visualcron?

It is a Task. Just paste in the output in a the value of File write Task in a new Job and run it.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

mholthouse
Paid support Topic Starter

2010-10-04T21:22:54Z

I like Write Task to File..nice for troubleshooting.

The task runs fine in command line. Here it is written out:

VisualCron acts as though its not even attempting to launch the application. I will attach a screenshot of the error message.

Support wrote:

mholthouse wrote:

Is the error I am getting the error I would get if it is too long?

Probably not. I believe the error is from your exe because something is wrong in the argument.

mholthouse wrote:
Also, is "File Write Task to" a function of visualcron?

It is a Task. Just paste in the output in a the value of File write Task in a new Job and run it.

Edited by user 2011-02-15T00:12:32Z | Reason: Not specified

mholthouse attached the following image(s):

Support
Official support

2010-10-04T21:28:55Z

I see that I get the same error when running it with Credentials. Do you need to run with Credentials?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

mholthouse
Paid support Topic Starter

2010-10-04T21:34:38Z

I would need to run with credential because the report scheduler would need access to the location it is exporting to (not on the same server). Just for grins, I tried it without credentials and it said it could not find the specified file.

Support wrote:
I see that I get the same error when running it with Credentials. Do you need to run with Credentials?

Support
Official support

2010-10-04T22:43:26Z

I think the problem might be that the Credentials that you use does not have access to that export folder (or other folder used)

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

mholthouse
Paid support Topic Starter

2010-10-04T22:54:23Z

The credentials do have access to the folders. The export runs fine in command line under those credentials. I also am able to run it fine if I exclude 2 of the attachments in the command line. It doesn't matter which 2 and it runs fine. To me, it really acts like the arguments are too long.

Support wrote:
I think the problem might be that the Credentials that you use does not have access to that export folder (or other folder used)

Support
Official support

2010-10-04T23:24:00Z

#10

Yes, you may be right here. We will investigate if there is any limit here.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!