Peter,

As instructed, I changed the "Mercury.ini" entry to "# MercuryX" so that the module doesn't load when I start M/32, but how does that help..? I need the scheduler to be working.

So, I enabled the MercuryX module and restart M/32... Guess what..? Nothing works again.

M/32 is not loading in "Off-line mode". It is already in "On-line mode", so I selected "Off-line" and On-line", but it makes no difference.

I'm going back to v4.62... Sorry.

Regards. SJS. 

I have upgraded from v4.62 to v4.72, but when M/32 is restarted it will not run. I simply upgrade and did not install the native service option.

I have modules C, D and X loaded. The Task Scheduler X simply says "Waiting for processes to", but does nothing.

HELP..!

Regards. SJS.
 

Put a comment in front of MercuryX in Mercury.ini, like this:

[Protocols]
MERCURYS.DLL
MERCURYP.DLL
MERCURYE.DLL
# MERCURYC.DLL
# MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
MERCURYI.DLL
# MERCURYB.DLL

I assume that there is a bug with the v4.72 installer and I have to remove M/32 X module.

I also assume that I have to add it back and re-enter the schedule times, or does M/32 X no longer work properly..? 

Thanks. SJS
 

No there is nothing wrong with the installer - but there are reports here that suggest that MercuryX in 4.72 loads the entire Mercury in Off-Line mode, and you have to uncheck the off-line, http://community.pmail.com/forums/thread/18404.aspx - but I haven't checked this myself.