oh crap: I split the posts (can't undo) but somehow your last reply stayed here... - Glen could you re-post the above to the newly created thread?

When I restart Mercury, the Core and two modules (MercuryI and MercuryX) load and run normally, but MercuryS and MercuryE start up in Offline mode. To get them working, I need to cycle the whole of Mercury Offline and back on again (ie, File > Enter Offline Mode, File > Leave Offline Mode). I can't find any settings which control it.

This didn't happen before - has anyone else seen it?

Thanks

Chris

Yes! The same thing happens to me, ever since I upgraded to the latest version.  I've also noticed that the latest version is a little less stable, with a crash every couple weeks or so.  I haven't found a reason for the crash yet; once I restart Mercury and cycle it offline/online, it picks up where it left off.

-=Glen

Thanks, Glen. I should have said, so far I remember this has only happened with 4.7 - I've now installed 4.72 and it's still doing it.

 I should also have said I'm running under Windows XP, SP3, running as a service through NT Wrapper

Chris

Chris: Does this happen when running Mercury as a program as well or only when using NT Wrapper? Did you try using the new native service mode?

Glen: Could you give some more details about your environment please so we can see if there is some common factor that triggers this.

/Rolf 

Rolf, I've now tried running Mercury as a program, and the same thing happens, whether I use loader.exe or straight into mercury.exe
I'm a home user (donation rather than licence) so I can't run native service mode.

However, I've discovered it only happens if MercuryX is loaded, so the short term workaround is to not load it.

I have to actually not load Mercury X, rather then just setting its options. I've never set it to do anything other than run continuously - I normally use it to run a batch file on start up, but even if I remove that, it still causes the problem.When I've upgraded, I've kept my settings, so maybe there's something residual in mercury.ini

- extract from mercury.ini:

    [MercuryX]
    Cmd_Wait: 0
    IE4_Dialling: 0
    Use_ETRN: 0
    Clients_only: 0
    Drain_queues: 1
    Sunday: 0000,0000,0,0,0,0
    Monday: 0000,0000,0,0,0,0
    Tuesday: 0000,0000,0,0,0,0
    Wednesday: 0000,0000,0,0,0,0
    Thursday: 0000,0000,0,0,0,0
    Friday: 0000,0000,0,0,0,0
    Saturday: 0000,0000,0,0,0,0

I'm planning to find a spare machine and do a fresh install of 4.7 with the default options, to see what a clean mercury.ini looks like.

Chris

Thanks for the new info, I've forwarded the matter to the Beta group.

/Rolf 

Some debugging data:

The MercuryX section of mercury.ini on a clean install (same workstation separate location) has all but one line hashed out:

    [MercuryX]
    Drain_queues: 1
    # Cmd_Delay: 10
    # Cmd_Wait: 1
    # IE4_Dialling: 0
    # Use_ETRN: 1
    # Clients_only: 1
    # Sunday: 0800,1800,3,15,30,60
    # Monday: 0830,2100,5,15,60,60
    # Tuesday: 0830,2100,5,15,60,60
    # Wednesday: 1500,1900,2,30,5,30
    # Thursday: 0900,1900,2,30,0,0
    # Friday: 0830,2100,5,15,60,60
    # Saturday: 1031,1035,2,45,-1,0

That clean install behaves similarly to my current installation, although only MercuryE is affected, not MercuryS. That is:

    If MercuryX is loaded, Mercury starts with MercuryE offline, with core and other modules (including MercuryE) on line;
    if MercuryX is not loaded, everything starts online

I've tried applying the MercuryX section from the clean mercury.ini  to my installation, and using my current settings hashing out the lines for the days of the week; neither makes any difference, MercuryS and MercuryE still load offline.

I'm out of ideas!

Chris

Peter:

I had initially tried running Mercury as a service, but

could not figure out how to monitor it this way and generally like

leaving the monitor screen on, so I went back to just running it ther

old way.  I disabled the SMTP server in IIS many years ago when I first

set up Mercury, and it is also disabled in WinGate (also running on

that server), so there should not be any port conflicts.  I will shut

down Mercury and test that port this weekend when nobody is emailing. Thanks for the tip!

This has gotten a little off-topic from the "offline modules" discussion so let me know if I should move the stability discussion to a new thread.

-=Glen