Hotkey script is in use - cannot run.

[email protected] · Post by **[email protected]** » Mon Dec 05, 2011 12:57 am

After installed MS 13.0.03 I created a simple macro to just send a string of text "This is a test" and assigned the macro to a hot key ALT + t.

However, when I press the hotkey all I got is the Message Box "Hotkey scrips is in use - cannot run". It turns out that every scrips cannot run after assigned a hotkey and all with this error message.

Have any one seen this error? What can I do to run a script using hetkey?

Thanks,
binhvu

Post by **Marcus Tettmar** » Mon Dec 05, 2011 10:42 am

You should only get this message if the macro is already running or open in the editor.

[email protected] · Post by **[email protected]** » Wed Dec 07, 2011 9:18 pm

Hi Marcus, I am very sure that none of the scripts were opened or edited at the time. Currently, I am switching back to Macro Scheduler version 8. Which is lacking a lot of latest stuffs in version 13, but at least my hot keys are working fine.

Thanks,
bvu

Post by **Marcus Tettmar** » Thu Dec 08, 2011 9:36 am

This was supposed to only happen if the script was in use but we found a case where it would be incorrectly reported. Please try 13.0.04 which is now available from the usual places.

[email protected] · Post by **[email protected]** » Fri Dec 09, 2011 10:54 pm

This is great 3.0.04 fixes the problem.

Thanks,

Dman · Post by **Dman** » Tue Jan 22, 2013 4:40 am

Sorry to dig up an old thread, but I'm having this problem right now when trying to use my keyboard shortcuts.

Msched Pro 13.2.4
Win7 Enterprise x64

Have rebooted multiple times, same after reboots

NB: PC has MS FEP installed

Any ideas??

Post by **Marcus Tettmar** » Tue Jan 22, 2013 7:28 am

Where are the scripts stored? Are you able to edit them? What happens if you try and open one of the associated .scp files in Notepad? The reason I ask is that if the files or folder is readonly or if the scripts were locked for some other reason you would get this message when trying to access them via hotkeys. But if so you should also get an error or warning when trying to edit them.

Dman · Post by **Dman** » Wed Jan 23, 2013 4:42 am

You nailed it, the scripts weren't accessible in the location that Msched thought they were because - they weren't there!

How did I get to this stage?

I migrated from one box to another,.. did an import. Then I went to move the files to another directory due to a bunch of folder redirects in this enterprise environment. Previously msched was failing to load at all because it had put the config and scp files in the mydocs but the mydocs was technically on a server - somehow it had installed and loaded ok, but it started refusing to load (unfortunately, i can't tell you what that error was, i didn't save it)

So I uninstalled, reinstalled, imported macro dir (it read the redirected folder ok) then went tools > options > change macro group/settings, chose the new path, ticked copy current settings.. but I realize now, this doesn't mean copy current macros.

I was getting errors when clicking on macro folders so I manually set them to the correct path, however in the correct path, no scp files existed, creating an epic fail.

I had a backup of the old SCP files so I copied them to the new central location and all is well.

My config has gone from Msched std to portable to pro to redirected folders to new directories, so, an unusual journey =)

Thanks for pointing me in the right direction Marcus.