msnet.exe remote macro launcher issue

[ruchi]

Hi,

When I need to run a macro remotely into second system, I run the command:
==>msnet.exe 192.168.1.10 6666 732_task.scp

This works fine most of the time... but when I keep running all my tests remotely, notice the error "specified macro does not exist"

Now, I have to run macro using command
==>msnet.exe 192.168.1.10 6666 732_task

notice, above script file without ".scp" extension!

This has become so difficult because, I have to keep changing my automation suite test parameter file to remove the extension at times and put back the extension.

Help required badly pls help

Ruchi

[Marcus Tettmar]

Which version of Macro Scheduler are you using? This was (should have been) fixed in 12.0.3

[ruchi]

I am using 11.1.10

I also have a 12.0.4 with me, can I use the same old msnet that came with 11.1.10 or do I need a new one? In addition, can 12.0.4 installation do an automatic upgrade or I need to uninstall previous one? I am asking all this becoz I am afraid my scripts will not work anymore after I mess with this new one.

could you pls let me know the latest completely tested and stable version?

Also, now for the 12.x version what should I run the script using ".scp" or no extension? If you pls let me know, meanwhile I can modify all my scripts.

Thanks,
Ruchi

[Marcus Tettmar]

If you install v12 it will NOT alter your existing v11 scripts. v12 installs into a separate folder with a separate macro profile. You would need to import your v11 scripts or point v12 at your v11 scripts in order to use/modify them. If you are worried about breaking them then I would recommend importing them so that you have a second copy - the original in v11 and a new copy in v12.

The existing msNet will work with v12 but you will need to reinstall the server component after installing v12 and point it at the v12 program folder so that it installs the server into the correct Macro Scheduler installation.

You should specify just the macro name. The macro you specify in an msNet call must be a macro existing inside the Macro Scheduler installation (showing in the Macro Scheduler window).

If you have problems it may be a connection - network/firewall - issue. I always recommend running a script via msNet LOCALLY first to test that the setup is working and only THEN try to run the script via msNet from another machine. If it works when running msNetGui locally but not from another machine then you need to talk to your network administrator.