File Event based schedule delayed....on Thursday!

scheduling XI Scheduler
1

BI 4.1 SP6 on Redhat.
We have a daily WebI schedule set to run 00:30 every day. It is reliant upon a file event. That event typically arrives 01:30. When the report finishes, whether successful or not, it triggers a schedule event which a whole bunch of other reports wait on.

If the file event arrives between about 1:40 and 2:15 and it is Thursday, the schedule is created immediately (no other reports run on the box at this time) but it is then delayed anywhere between 1 and 4 hours before the schedule actually starts. The report finishes fine, the schedule event is triggered and the other reports kick off. All is fine - other than this mystery delay.

Our server guy has taken a look at the box and can see no evidence of anything going on at that point in time. We see the following in the logs:

2016 01 07 01:43:46:836|+0000|Error| |>>|E| |cms_SIAxxx.CentralManagementServer|30068|1149491520|| |44
3|
0|7|0|BIlaunchpad.WebApp|servername:4335:60670.1511982:1|webiserver_SIAxxx.WIPS6.openSession|localhost:7448:1116956992.1263418:1|
cms_SIAxxx.CentralManagementServer.LogonWithTokenEx5|localhost:30068:1149491520.19249316:1|
CqdIeP543UgQkgHjLnDltE81709aa|||||||||||assert failure: (sessionmgr.cpp:3536). 
(0 : CSessionMgr::ValidateApplicationCUID: 
Attempt to login when specifying an invalid application CUID session. The specified id is = ).^^
sessionmgr.cpp:3536:-: TraceLog message 9938

2016 01 07 03:15:06:115|+0000|Error| |>>|E| |cms_SIAxxxx.CentralManagementServer|30068|1138964800|| |443|
0|7|0|BIlaunchpad.WebApp|servername:4335:60670.1511982:1|webiserver_SIAxxx.WIPS1.openSession|localhost:11765:1100482880.157349:1|
cms_SIAxxx.CentralManagementServer.LogonWithTokenEx5|localhost:30068:1138964800.19292386:1|
CqdIeP543UgQkgHjLnDltE81709aa|||||||||||assert failure: (sessionmgr.cpp:3536).
 (0 : CSessionMgr::ValidateApplicationCUID: 
Attempt to login when specifying an invalid application CUID session. The specified id is = ).^^
sessionmgr.cpp:3536:-: TraceLog message 9939

The times of those two entries match the time the schedule was created and then the time it actually started on that day. The WIPS used changes between those two times.

Nick Daniels :uk: (BOB member since 2002-08-15)