Hi,

Right after I restart the 24x7 scheduler, I get
this log entry as follows:

"System configuration discrepancy detected.
The default date format differs from the
format specified for the current user.
You should correct "HKEY_USERS\DEFAULT\Control Panel\International\sShortDate"
value in the system registry."

I looked at the registry key and it has the
value: "M/d/yyyy".

Why am I getting this? I've never changed it, and
I also get this log error on my test 24x7 server as
well. What should the value be?

In a different timing matter, I looked at the stat.log
file and all my entries are 4 hours into the future.

Example:

Job No: 119 Job Name: 0008-Futures Transfer Process ID: 764
Creation Time: 5-Aug-2003 19:40:26:0004 Exit Time: 5-Aug-2003 19:40:30:0008
Duration: 4 seconds
.
.
.

My system time is 3:40 pm (15:40), and yes, I double
checked the system time and its correct. The
schedule.log file shows execution times for these same
jobs correctly. I have been having problems where some jobs
have not launced in the evening and I am wondering
if this is related.

Any ideas?

Thanks,
Robert

A fix for this erroneous warning will be available in version 3.4.12

For more info please see another message thread starting at http://www.softtreetech.com/cgi_bin/config.cgi?read=4224

: Hi,

: Right after I restart the 24x7 scheduler, I get
: this log entry as follows: "System configuration discrepancy detected.
: The default date format differs from the
: format specified for the current user.
: You should correct "HKEY_USERS\DEFAULT\Control
: Panel\International\sShortDate"
: value in the system registry."

: I looked at the registry key and it has the
: value: "M/d/yyyy".

: Why am I getting this? I've never changed it, and
: I also get this log error on my test 24x7 server as
: well. What should the value be?

: In a different timing matter, I looked at the stat.log
: file and all my entries are 4 hours into the future.

: Example: Job No: 119 Job Name: 0008-Futures Transfer Process ID: 764
: Creation Time: 5-Aug-2003 19:40:26:0004 Exit Time: 5-Aug-2003 19:40:30:0008
: Duration: 4 seconds
: .
: .
: .

: My system time is 3:40 pm (15:40), and yes, I double
: checked the system time and its correct. The
: schedule.log file shows execution times for these same
: jobs correctly. I have been having problems where some jobs
: have not launced in the evening and I am wondering
: if this is related.

: Any ideas?

: Thanks,
: Robert

Okay, my formats are the same for the HKEY_USERS\.DEFAULT user
and the HKEY_CURRENT_USER, so I'll just wait for the fix to remove the message.

Reading the other message thread, I take it that job behavior may
be different if the formats are different for these registry keys while
running the software in service mode. However, my registry keys are the same and I
still have jobs not run in the evening. What about the difference
between my system time and the times logged for jobs in the stat.log file
(my other question in my previous post)? Is this caused by this registry problem?
Should I run this in standalone mode until the new fix comes out?
FYI, my system time and time zone are set correctly.

Thanks,
Robert

: A fix for this erroneous warning will be available in version 3.4.12

: For more info please see another message thread starting at
: http://www.softtreetech.com/cgi_bin/config.cgi?read=4224

Are you using different time zones for the system (default) account and your interactive account? If you are not sure please check the registry for the .DEFAULT account.

: Okay, my formats are the same for the HKEY_USERS\.DEFAULT user
: and the HKEY_CURRENT_USER, so I'll just wait for the fix to remove the
: message.

: Reading the other message thread, I take it that job behavior may
: be different if the formats are different for these registry keys while
: running the software in service mode. However, my registry keys are the same
: and I
: still have jobs not run in the evening. What about the difference
: between my system time and the times logged for jobs in the stat.log file
: (my other question in my previous post)? Is this caused by this registry
: problem?
: Should I run this in standalone mode until the new fix comes out?
: FYI, my system time and time zone are set correctly.

: Thanks,
: Robert

: Are you using different time zones for the system (default) account and your
: interactive account? If you are not sure please check the registry for the
: .DEFAULT account.

Okay, I checked the time zone info and there are no registry keys that have
time zone information in either the

\HKEY_CURRENT_USER\Control Panel\International

or the

\HKEY_USERS\.DEFAULT\Control Panel\International

registry areas. The only place I can find timezone info are in the registry items:

\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation
\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\TimeZoneInformation
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

and still they don't seem have anything pertinent that I can change.

Anyway, the scheduler service stopped launching jobs AGAIN about 7:40pm last night.
I'm now really at a loss as to why this is happening and this software is basically
useless right now. To remedy, I have to stop and restart the service from home so
my jobs will run. This is not making me look good!

Any other ideas? Should I reinstall an earlier stable version?

Robert

Please describe the problem one more time.
Please correct me if I am wrong, you have jobs that do not run at certain times do run fine at other times.
How these jobs are scheduled? daily, weekly? recursion intervals? other dependencies?
Do they resume running after some time?
Are they tied to the same job queue? Are their other jobs that do run during these "block out" times?

By the way, if you want to restart the service periodically you do not need to I have to do that manually. You can use Tools/Options menu to schedule periodic restarts.

: Okay, I checked the time zone info and there are no registry keys that have
: time zone information in either the

: \HKEY_CURRENT_USER\Control Panel\International

: or the

: \HKEY_USERS\.DEFAULT\Control Panel\International

: registry areas. The only place I can find timezone info are in the registry
: items:
: \HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation
: \HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\TimeZoneInformation
: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

: and still they don't seem have anything pertinent that I can change.

: Anyway, the scheduler service stopped launching jobs AGAIN about 7:40pm last
: night.
: I'm now really at a loss as to why this is happening and this software is
: basically
: useless right now. To remedy, I have to stop and restart the service from
: home so
: my jobs will run. This is not making me look good!

: Any other ideas? Should I reinstall an earlier stable version?

: Robert

I have jobs scheduled to run at certain times and jobs at intervals.
It seems that within the window of 6:45 pm and 8:30 pm, the scheduler
halts running ANY job. The service is still running but it seems like
the timer becomes disabled. This has happened everyday since July 30th
at which time the problem was first noticed. The problem persists until
I restart the service (not the computer), then everything runs fine after
that.

When I saw my stat.log file entering job times 4 hours ahead of when they
actually ran, I thought maybe this was the source of the problem since the problems always
happen near the end of the day. I have a test server that logs entries 4 hours
ahead too, but that seems to run fine. Both servers are running v.3.4.11.

Also, I wrote a job that writes a file with a date/time stamp in the filename every
3 minutes. In this file, I write the amount of free memory (so I can see what the amount
is as time goes along), and if the MemoryGetFree() and MemoryGetFreeEx() functions
work correctly, then I have plenty of memory. Example:

Virtual Memory Free (megabytes) = 1445.9453125
Physical Memory Free (megabytes) = 1110.57421875

About starting the service periodically, I wrote another job to do this
instead of restarting the server as you suggested in the 24x7 options. Restarting
the service takes only a few seconds, while restarting the server takes several
minutes. I don't want to miss launching a job. To restart the service, I wrote a
batch file, fired once an hour, with the following contents:

d:
cd \24x7*
net stop "24x7 Scheduler"
net start "24x7 Scheduler"
exit

Hopefully, this will keep me until I figure out what the problem is. And by the way,
does your log entries in stat.log reflect the current time or a future time?

Sorry for the long winded explanation, but that's it in a nutshell.

Robert

: Please describe the problem one more time.
: Please correct me if I am wrong, you have jobs that do not run at certain
: times do run fine at other times.
: How these jobs are scheduled? daily, weekly? recursion intervals? other
: dependencies?
: Do they resume running after some time?
: Are they tied to the same job queue? Are their other jobs that do run during
: these "block out" times?

: By the way, if you want to restart the service periodically you do not need
: to I have to do that manually. You can use Tools/Options menu to schedule
: periodic restarts.

Thank you. This is a pretty good description of the problem.

Here is what you need to do:
1. Find jobs that start/around around 6:45 pm. Set these jobs to run detached.
Use the schedule.log file or Log Viewer in 24x7 to find these jobs.

2. When the processing stops use the Windows Task Manager to check if both 24x7.exe and 24x7srv.exe processes are running. If you find only 24x7srv.exe this would indicate problems with the scheduling engine. The solution to this is described in step 1.

3. If detaching does not help check that you do not have job queue congestion. If all jobs are assigned to a single queue and you have a hanging job it will cause all other jobs to hang as well. If this is the case assign long running and potentially hanging jobs" to a separate job queue. If necessary, configure additional job queues using Tools/Job Queues menu.

Please keep us posted on the status of your problem.

: I have jobs scheduled to run at certain times and jobs at intervals.
: It seems that within the window of 6:45 pm and 8:30 pm, the scheduler
: halts running ANY job. The service is still running but it seems like
: the timer becomes disabled. This has happened everyday since July 30th
: at which time the problem was first noticed. The problem persists until
: I restart the service (not the computer), then everything runs fine after
: that.

: When I saw my stat.log file entering job times 4 hours ahead of when they
: actually ran, I thought maybe this was the source of the problem since the
: problems always
: happen near the end of the day. I have a test server that logs entries 4
: hours
: ahead too, but that seems to run fine. Both servers are running v.3.4.11.

: Also, I wrote a job that writes a file with a date/time stamp in the filename
: every
: 3 minutes. In this file, I write the amount of free memory (so I can see what
: the amount
: is as time goes along), and if the MemoryGetFree() and MemoryGetFreeEx()
: functions
: work correctly, then I have plenty of memory. Example: Virtual Memory Free
: (megabytes) = 1445.9453125
: Physical Memory Free (megabytes) = 1110.57421875

: About starting the service periodically, I wrote another job to do this
: instead of restarting the server as you suggested in the 24x7 options.
: Restarting
: the service takes only a few seconds, while restarting the server takes
: several
: minutes. I don't want to miss launching a job. To restart the service, I
: wrote a
: batch file, fired once an hour, with the following contents: d: cd \24x7*
: net stop "24x7 Scheduler"
: net start "24x7 Scheduler"
: exit

: Hopefully, this will keep me until I figure out what the problem is. And by
: the way,
: does your log entries in stat.log reflect the current time or a future time?

: Sorry for the long winded explanation, but that's it in a nutshell.

: Robert