Errors running imported jobs.

Hi!
Got two problems.

1.

"Job definition incomplete. Missing or invalid COMMAND property value."

This is the command property value:
"D:\application\path\app.exe altini=D:\application\path\supplier.ini provider=thomsondatastream action=uploadreqfile batchID=12345 enddate=-1 trigger="0930" loglevel=3"

2. On another job(and a little bit misspelled, too):

"Create process error. Extended error: RunAs error: Maximum supported encryptted value length is 260; you got 414."

The command line is similar to the first example, and the user name is only XX\Yyyyyyy long. I can't see were it gets 414 from. Is there some java-unicode issue? Anyway, what kind of limit would that be?

Anyway, in both cases the same code works on the windows version.

1. Weird, the error makes no sense to me. Do you get this error if you change the command line to Notepad? If yes, the problem is not with the command line, perhaps the job has some notification action enabled, but no command line specified for the notification action.

2. For jobs set to run under a different user account, it uses a special platform dependent utilities. It seems that you are running it on Windows, in which case it uses RunAs.exe. The command line passed to RunAs gets encrypted so that it cannot be read in clear text, and any passwords or other sensitive data specified on the command line cannot be seen in Vista Task Manager and other special task management utilities such Process Explorer and other. The encrypted command line in this particular case appears to be 414 bytes long, while the limit for your operation system is 260 bytes.

The second part of the message, which you didn't mention or didn't see, says that in such cases you should either wrap long command line into a batch file and schedule the batch file or better convert job type from Program Type to Script Type and for the type of script choose Shell/Batch Script.

Running these command as a batch scripts seems smarter anyway.
It seems to have solved both problems. Maybe a really long command was considered unset or something?

Thanks!

Also, those with a long command cannot be selected in the tree by either clicking or using the keyboard(they cant be previewed in the right pane).
They can be right-clicked and edited through properties though.

Sorry I don't get it "long command cannot be selected in the tree", which tree are you refering too? Do you mean descriptive job name or job command?