Access violation after Update to V14.0.5/6 with some macros

[migro]

Hi,

After Macro Scheduler was updated from 14.0.2 to 14.0.5 or 14.0.6, Macro Scheduler causes an Access violation directly when starting some of our macros.

Message: Access violation at address 00872DBD in module 'msched.exe'. Read of address FFFFFFFE.

There is no possibility to debug these macros, because the crash appears instantly when I run the first line with F8 (// COMPILE_OPTS|H:.....)

Even if I comment out all the lines in the macro the crash still occurs.

Any ideas?

[Marcus Tettmar]

Has anyone else seen this? Not surprisingly I can't reproduce. If there were a general issue with any version not running macros in debug then it would fail our most basic tests and wouldn't be released.

[migro]

Got some new findings inbetween. When I copy the code into a new macro it will run. When I delete now the original macro an rename the new one to the name of the original macro, I get again the access violation again.

[CyberCitizen]

Corrupt Macro.DAT?

I did get alot of those at the start when testing the earlier releases, however they were resolved. I don't get them anymore. It could have something to do with the macros looking in the wrong location. If you install MS to a different computer or location & import the macros, do you still get the issue?

[migro]

I got the same behavior on all of my PCs in the Office. All the macros are stored central and access is over an mapped network share. I'm working this way with Macro Scheduler now for 5 or 6 years without having problems with access violations.

OK, got one with the V14.0.2, when using the "OnChange" event in an dialoghandler for a radiogroup. But this was quickly detected an solved.
I think this access violations are not a problem within the code (see my previous mail).

I found several files with macro.dat (.001/002/e.g) in the filename.
But no idea if this files are OK or corrupt.

[Marcus Tettmar]

So is the problem when renaming a macro which is stored on a network share? Is that what I need to do to reproduce?

[migro]

Hi Marcus,

not really.

I only explained to cyber in wich way I'm working for all the years with Macro Scheduler.

The problem is that macros working still wit V14.0.2 generating an access violation when opened after an update to 14.05 or 14.06.

So what I've testet is to copy the content of one of these macros into the macro editor and run it from there - it does. When i save it it will run still. when I now delete the original macro, related in the same directory as the new one, and rename the new one to the original name, it will crash again.

[Marcus Tettmar]

I think I follow. However, if I do as you describe I do not experience any error. I have tried with the group mapped to a local folder and also a network folder. Am I missing some other step or requirement?

[migro]

The Problem didn't show up with all of the macros. Can I send You one which rises the error?

[Marcus Tettmar]

Yes, please send to support at mjtnet.com

[migro]

Note: In the actual Version 14.0.7 the behavior can't be reptroduced any more. Thanks

[Liberty]

I get the same error when using ver 13 in windows 8.1 It also appears directly when I try editing any macro.
For all macros tried.

WHAT TO DO?

[Marcus Tettmar]

I am unable to reproduce. I have installed Macro Scheduler 13 into Windows 8.1 and it is working fine. I can run and edit macros.

Can you check that the macro folder exists and is writeable. Check that there is a folder called "Macro Scheduler 13" in your My Documents folder. Check that this is not read only. If it doesn't exist please create.

Check that Macro Scheduler is looking at this folder. You can do that under Tools/Options -> Change Macro/Group Settings Path button, or check in the registry under:

HKEY_CURRENT_USER\MJTNET\MSched13 -> DataDir

This should point to the full path of the Macro Scheduler 13 folder under My Documents.

[JRL]

...using ver 13 in windows 8.1...WHAT TO DO?

What to do? The obvious answer is: Don't run old versions under operating systems they were not designed to work with. Can't believe Marcus didn't simply tell you to upgrade your Macro Scheduler. The last update to Version 13 was in December of 2012. Microsoft windows 8.1 wasn't released for public consumption until mid October 2013. That's 10 months later. Also, Windows 8.1 will continue to change while older versions of Macro Scheduler will not. Every Windows 8.1 update provides new opportunities for old un-updated versions of any software to fail.

At the very least hopefully you are using the last Macro Scheduler 13 update, version 13.2.4

[Liberty]

Dear Marcus,

As said I can start MS and edit all my macros and see the code in MS.
The path is correct.
However when I try edit or run the macro, I directly get the access violation - the code can be seen for a short moment

What to do? I would like to use 13 for a while as you also say it is working. Urgent

Waiting for reply I would like to add:
I have MS installed directly in C:\MacroScheduler and the macros in D:\MacroData (DataDir) as before.