APAR IC34619 has been opened for this: APAR= IC34619 SER= IN INCORROUT WINDOWS SCHEDULER SERVICE FAILS ON STARTUP WITH EVENT LOG ENTRIES 7022 AND/OR 7031.
Status: OPEN Closed: Apar Information: RCOMP= 5698ISMCL TSM CLIENT 5.1 RREL= R51W FCOMP= PFREL= F TREL= T Return Codes: Applicable Component Level/SU: Error Description: Up reboot of a client machine, the TSM scheduler service It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds . It has been seen that you may only see the 7022 in the logs and still witness this apar. . In a registry trace of the scheduler service, you can see a large time gap from when we request the password from the registry, and when we actually get it passed back. . 5/16 12:51:19 dsmcsvc.c(1006): GetRegistryEntries(): Opened RegistryKey 'SYSTEM\CurrentControlSet\Services\Backup \Parameters' 5/16 12:51:19 dsmcsvc.c(1087): GetRegistryEntries(): Locating Registry Entires for Node 'NODENAME' ... !!! timeout 2:06 !!! 5/16 12:53:25 dsmcsvc.c(1171): GetRegistryEntries(): Found Registry Password for node 'NODENAME'. . Service trace: 05/16/2002 12:51:20.0042 [79] : session.cpp (1837): sessInit: Session initialized. 05/16/2002 12:51:20.0042 [79] : session.cpp (1919): sessOpen: Attempting to open communications 05/16/2002 12:51:20.0042 [79] : commtcp.cpp (1179): TcpOpen: Internet socket defined. 05/16/2002 12:51:20.0042 [79] : commtcp.cpp (1298): TcpOpen: Socket window size set to 64512 bytes. !!!!time out 2:04 !!!!! 05/16/2002 12:53:24.0820 [79] : pscomtcp.cpp (1175): Attempt connection was rc = 0. . Although customer receive this error on startup, they are able to start there scheduler service manually after receiving these errors. . This problem has also been witnessed at 4.2.2.x and 5.1.x.x as well. . Local Fix: Start your scheduler service manually -----Original Message----- From: Eliza Lau [mailto:[EMAIL PROTECTED]] Sent: August 22, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: Re: 5.1.1 Windows 2000 scheduler won't start Tim, I haven't heard back from Level 2. I don't even know what APAR it is given. The scheduler fails to start the first time after we installed the 5.1.1 client on a Windows 2000 server (not Professional). The event number in the event log is 7031 The TSM scheduler service terminated unexpectedly After the machine reboots, the scheduler doesn't start even though it is set to auto. The event number is 7022 The TSM scheduler service hung on starting Starting it manually then after works. We can recreate it every time the machine boots. This is a new Windows box with a new w2k server installed on it. Eliza