DSXchange

Wasn't talking about the Windows scheduler or what user it uses to run the task but rather something you probably need to add to the dscmdexport command line:

dscmdexport /H=%Host% /U=%User% /P=%Password% /D=????

chulett wrote:Wasn't talking about the Windows scheduler or what user it uses to run the task but rather something you probably need to add to the dscmdexport command line:

dscmdexport /H=%Host% /U=%User% /P=%Password% /D=????

I tried to add the /D command, but it gave me the error below:

dscmdexport aborted:
Failed to attach to the project

And you are certain you used the correct value? Unfortunately, I've got nothing else to add except to suggest contacting your official support provider for help.

I know they're not supposed to be positional, but try it with the domain switch first. For example:

brownnt wrote:I tried to add the /D command, but it gave me the error below:

dscmdexport aborted:
Failed to attach to the project

And you say that exactly the same batch works fine when you run it manually?

ray.wurlod wrote:I know they're not supposed to be positional, but try it with the domain switch first. For example:

Code: Select all

dscmdexport  /D=%Domain% /U=%User% /P=%Password% /H=%Server% %ProjectName%

Thanks, but I tried it that way.

PhilHibbs wrote:

brownnt wrote:I tried to add the /D command, but it gave me the error below:

dscmdexport aborted:
Failed to attach to the project

And you say that exactly the same batch works fine when you run it manually?

Yes, sir. Run just fine when I kick off the batch file manually via command line. Will not run via windows task scheduler.

Can you have the scheduler script ECHO the command so you know exactly how the variables are being passed?

brownnt wrote:

chulett wrote:Wasn't talking about the Windows scheduler or what user it uses to run the task but rather something you probably need to add to the dscmdexport command line:

dscmdexport /H=%Host% /U=%User% /P=%Password% /D=????

I tried to add the /D command, but it gave me the error below:

dscmdexport aborted:
Failed to attach to the project

I just encountered the same issue. I tried /O it did not complain but did not work. I tried /NODEPENDENTS which also did not work. These all did not bring up a dialog box. When I ran under cmd directly then I get a dialog box when I leave off /O and /NODEPENDENTS. If all I do is reselect the project it outputs a DSX file. Not cool. Need a patch.

Does the box just ask for a default (e.g. OK) response? If so you can try the old trick of redirecting stdin from /dev/null (or .\NUL).

No, it shows the login screen.

That suggests that the username/password in the command is incorrect, or that the login/security service (in the services tier - the machine where WAS is installed) is not running/inaccessible.

All you have to do is select a project, so user and password are correct.