Reload Task with Execute command in QMC

[punitpopli]

Hi Experts,

I am having a requirement where a .zip file will be placed on the shared drive along with a file which will be copied once the file (.zip) gets completed.

I have implemented a solution using a Execute command which will be calling cmd and extracting the .csv from the .zip file and placing the same on a different drive.

Also, deleting the status from shared drive using CMD post copying the file locally.

The application is reloading successfully on Desktop client, but the above functionality is not getting achieved on QMC. Would like to know if there is any setting needs to be done at QMC/application level to make this functional

App is getting reloaded and extractions of .zip is working and able to delete the flag file but receiving an error "Bad zip file":

Link referred

Reload Qlikview document using EXECUTE command ,

Authorizing the Script EXECUTE Statement | Qlikview Cookbook

Can anyone let me know if I am missing anything here

[punitpopli]

Hi Experts,

Can any one help me on this?

Regards,

Punit

[marcus_sommer]

Do I understand it right that the EXECUTION statement will be executed, the cmd runs but the extracting of the zip failed or is this successful, too and only the following load failed with the bad zip-file message?

- Marcus

[punitpopli]

The execution statement ran successfully with bad zip file erroe message on Desktop client.

The same is not working on QMC

To be precise QVW had a Macro code which is actually unzipping the file and placing on the local drive and CMD is deleting the flat file from the shared drive.

[marcus_sommer]

Is your desktop client running on the server machine and with the user-account from the server-services? If not try it in this way - with them you will exclude potential problems with the access rights from the user and also if there is anything which blocked the access from the server side (firewall or any other group policy stuff).

Another problem could occur if there is nobody (you or your server account) logged in on the server. This could lead to the situation that the qmc runs the execute statement but the following batches are executed with the windows default-user (because nobody is logged in) and this user might not have the appropriate access rights or licences.

Beside the options to log in with a certain user or to adjust the default user settings you could try to implement intermediate steps which call your batches with a RUNAS or you bypassed this by calling a windows task with the EXECUTE statement.

- Marcus