Skip to Content
author's profile photo Former Member
Former Member

MII scheduler stops during clock change

3 weeks ago during the clock change from British Summer time to GMT, MII scheduled transactions seemingly did not run for 1 hour.

We have transactions that upload IDocs into SAP.

At 01:00, SAP clock starts to run at half speed. (This is the work-round alternative to taking down SAP system)

At 02:00 windows server on which MII runs goes back to 01:00

There is a 1 hour time window (which appears as half an hour in SAP because its clock is running at half speed) during which data is not received by SAP

MES system shows 2 lots of data between 01:00 and 02:00, but..

MII scheduler only seems to have submitted jobs for 1 hour out of 2 hours at this time.

Can anyone explain why please?

Many thanks


Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Best Answer
    Posted on Nov 19, 2012 at 12:45 PM

    Hi Ben,

    There are several issues with Daylight Saving Time that seem to crop up every year around this time. First check to see if whether your Java installation is up to snuff on DST for your timezone. Then check to see if the timezone is set correctly in NW/MII (which versions, SP, etc. are you using?). There are a number of threads posted over the last few years which address how people have fixed issues with DST, so search back in this community for all time periods for additional solution suggestions.

    Regards, Mike

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Michael Appleby


      Well, a year went by before I updated this question .. during that time we waited for SAP to give us a fix.. and they still haven't.

      This year, overnight I monitored the behaviour of 2 MII servers, one 12.1, the other 12.2, each had a transaction scheduled to run every 20 seconds.

      At the end of DST 00.59 ticked over to 01:00 (no clock change on the server yet).. the 12.1 scheduler froze, stopped kicking off transactions. I stopped and restarted the scheduler but it made no difference. I created a brand new entry in the scheduler and enabled it .. but it didn't run.

      As a work-round we used repeating web service calls to trigger the transaction, which then read OK.

      At 01:59, the servers then went back to 01:00. At this point the 12.2 scheduler froze! Again, no action in the scheduler could get it to run... until 1 hour later, after which time both schedulers worked OK.

      So we are still waiting for a fix, for 2014. I still don't understand why we alone have these issues. does everybody else take their systems down at the end of DST?