These tasks worked fine prior to 5.7.2, but now I this error message: Illegal characters in path.

It is a Process Execute:

Command: "C:\Program Files\SQLyog\sja.exe"
Arguments: "C:\Documents and Settings\administrator\Desktop\Scripts\MySQLBackup.xml" -l"C:\Documents and Settings\administrator\Desktop\Scripts\MySQLBackup.log" -s"C:\Documents and Settings\keithdavis\Application Data\SQLyog\sjasession.xml"

It is probably a permission problem. That the user that runs the executable cannot find the paths in the arguments. Check the Credential - or the user that runs the service.

---

It is probably a permission problem. That the user that runs the executable cannot find the paths in the arguments. Check the Credential - or the user that runs the service.

Ok, but it worked just fine before the upgrade. We've got a couple like this. One I was using a UNC path, and just changed that, this one I don't know what to change. The user credential is a Domain Admin....so, I know it has permissions.

Was the service running as another user before - maybe?

---

Was the service running as another user before - maybe?

Nope. Beside, there are many other jobs like this one, not exactly the same, but close.

Ok, so, which one fails:

1. local restricted paths

and/or

2. network unc paths

By the way, are you using "With profile" or "Network credential" on this.

Are you using "managed" or "api" mode?

---

Oh, and it crashes on me on that task every time now when I hit the "browse" button next to Command to change that. I've submitted the report each time, and I've tried it three times now.

With profile
Local path AND UNC path
API mode

Oh, and it crashes on me on that task every time now when I hit the "browse" button next to Command to change that. I've submitted the report each time, and I've tried it three times now.

With profile
Local path AND UNC path
API mode

Ok, the client error is another one, it does not like the quotes.

What if you create similar execute Task with a local folder like "c:\yourexe.exe"

Does it fail then?


BTW, are you really sure that your service did not run as another user before?

---

Have you talked about the client problem the whole time or are you talking about the execution problem?

---

Have you talked about the client problem the whole time or are you talking about the execution problem?

I'm talking about both. The excecution error and when I go to change that path (of the task that is failing), I get the client error.

It seems from version to version, VC responds differently haveing quotes or not.

Anyway, I wrote a script (AutoIt) that VC can call as a workaround and it works fine. It's not the best, because my script could fail and I won't get notice, but I don't have time to mess with right now.