Supposedly this fix was implemented on 5.1.5.4, see below info taken from readme. We are still experiencing this problem after upgrading to this level.
Has anyone else noticed this? * IC34619 WINDOWS SCHEDULER SERVICE FAILS ON STARTUP WITH EVENT LOG ENTRIES * * 7022 AND/OR 7031. * * * * IC34630 5.1 WINDOWS TSM CLIENT SCHEDULER SERVICE HANGS (SOMETIMES) * * AFTERREBOOTING THE SERVER (EVENT ID: 7022) Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
