msched.exe has stopped working

General Macro Scheduler discussion

Moderators: JRL, Dorian (MJT support)

Post Reply
MikeSr
Junior Coder
Posts: 20
Joined: Sun Feb 07, 2010 8:31 pm
Location: Fort Myers, FL
Contact:

msched.exe has stopped working

Post by MikeSr » Mon Feb 08, 2010 8:07 pm

Testing my script which is running a continuos loop, after a few minutes one of two errors are generated
- msched.exe has stopped working
or
-error initializing MSSCRIPT control.

Don't know where to begin! Is loop causing recursive errors?

Regards,

MikeSr

sarver311
Pro Scripter
Posts: 84
Joined: Tue Jun 17, 2008 6:37 pm

Post by sarver311 » Mon Feb 08, 2010 9:45 pm

Hi Mike

Well my first instinct would be you may have to reinstall MS but here are a few suggestions to see if its the script or possible the ms engine.

What happens if you create a simple script with nothing but a loop in it? Can you recreate the issue with just a loop running?

If that doesn't recreate the issue do you have any older revisions of this script you can test to see if it happens in those versions?

I have found 9 times out of 10 that crashes in MS are due to my scripts not the program but it certainly is possible it's MS.

If you want to paste your script I'd be happy to try it on my end and see if I get any issues.

-Josh

MikeSr
Junior Coder
Posts: 20
Joined: Sun Feb 07, 2010 8:31 pm
Location: Fort Myers, FL
Contact:

Post by MikeSr » Mon Feb 08, 2010 10:11 pm

Well, what I found out so far is this:
I am using two marco scripts. I have the first script calling the second.When the second is complete, it call the first and so on.
I commented out the call to the second script and so far it is running just fine.
I am using the "Macro" command to call each macro.
It appears that this might be recursion.

I will post more as run a few more tests.

gdyvig
Automation Wizard
Posts: 447
Joined: Fri Jun 27, 2008 7:57 pm
Location: Seattle, WA

Recursion not necessary.

Post by gdyvig » Tue Feb 09, 2010 12:37 am

Hi MikeSr,

There is no need for script2 to call script1.

When script2 is finished control will return to script1, next line.

So script1 can look like this:

Code: Select all

Macro>script2
Macro>script3
Macro>script4

Gale

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts