event id 7024

[dnlwilson]

Getting the following messages in our Windows (2000 server) clients:



The TSM Scheduler service terminated with service-specific error 4.

The TSM Scheduler service terminated with service-specific error 8.



We are running 5.3, the backups seem to be running (we have done restores) but these are showing as a critical error in the event logs. So are they critical and something is wrong, or is this just the scheduler shutting down after a normal backup?



All of our clients are being backed up via the schedule on the TSM server. If this is a normal thing, is there a way to make them non-critical so that our MOM server won't go nuts getting all the critical errors.



Thanks for any insight.

 

[BC@SHS]

did you ever get an answer? we are receiving the same with error 4 and error 12. from looking at the logs it looks like my 12 is when the node tries to check in with the server for a schedule and there's no sessions available. but i can't see what's causing the 4. mom is starting to drive me nuts with these alerts.

thanks,

BC

 

[Rick111]

try using the CAD to manage the scheduling service

 

[BC@SHS]

yep...

here's my dsmsched

12/28/2005 04:31:21 Scheduler has been started by Dsmcad.

12/28/2005 04:31:21 Querying server for next scheduled event.

12/28/2005 04:31:21 Node Name: SHSEX03

12/28/2005 04:31:21 Session established with server SHSTSM01: Windows

12/28/2005 04:31:21 Server Version 5, Release 3, Level 1.6

12/28/2005 04:31:21 Server date/time: 12/28/2005 04:31:21 Last access: 12/28/2005 04:31:17



12/28/2005 04:31:21 --- SCHEDULEREC QUERY BEGIN

12/28/2005 04:31:21 --- SCHEDULEREC QUERY END

12/28/2005 04:31:21 Next operation scheduled:

12/28/2005 04:31:21 ------------------------------------------------------------

12/28/2005 04:31:21 Schedule Name: EXCH_OS

12/28/2005 04:31:21 Action: Incremental

12/28/2005 04:31:21 Objects:

12/28/2005 04:31:21 Options:

12/28/2005 04:31:21 Server Window Start: 16:00:00 on 12/28/2005

12/28/2005 04:31:21 ------------------------------------------------------------

12/28/2005 04:31:21 Scheduler has been stopped.



now here's the system event viewer back to back entries, the 2nd of which triggers the MOM alert (multilple servers sending multiple alerts to my pager)



Event Type: Information

Event Source: Service Control Manager

Event Category: None

Event ID: 7036

Date: 12/27/2005

Time: 4:31:01 PM

User: N/A

Computer: SHSEX03

Description:

The TSM scheduler service entered the stopped state.



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

Date: 12/27/2005

Time: 4:31:01 PM

User: N/A

Computer: SHSEX03

Description:

The TSM scheduler service terminated with service-specific error 4 (0x4).



For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.







all looks ok and i get backups, just get lots of pages... any ideas?

BC

 

[BC@SHS]

bump...



anyone?



thanks,

BC

 

[BC@SHS]

Still looking for an answer, anyone? Is there a way the MOM guys can add just add a filter to ignore these? If so, how, what should I tell them

thanks,

BC

 

[mayberce]

Does anyone know if this has been resolved?

"The TSM Scheduler service terminated with service-specific error 4"

 

[Z60453]

"The TSM Scheduler service terminated with service-specific error 4"

For "The TSM Scheduler service terminated with service-specific error 4"

The reason is very simple.
Error occured when backup completed and the dsamcad service normally interrupted the tsm scheduler service.
This is a usual error message when "dsamcad" service that manages the "tsm scheduler" service is closing the completed schedule,
And if tsm could not backup some opened files/files that are in use at the time of backup, than the service is ended with error 4.
Install open file support for TSM Client or exclude the failed files from dsm.opt file.

It will be better a comparison (check the time when it happened).

In windows:

Event Type: Error
Event Source: AdsmClientService
Event Category: None
Event ID: 4099
Date: 9/13/2007
Time: 6:16:31 AM
User: NT AUTHORITY\SYSTEM
Computer: XXXXX
Description:
Scheduler exited with a result code of 4.

In dsmsched.log :

09/13/2007 06:16:30 ANS4987E Error processing '\\xxxxxx\c$\Documents and Settings\sshwebp\NTUSER.DAT': the object is in use by another process
..........................
09/13/2007 06:16:30 Schedule Name: IBM_INCR_ANYDAY_0600
09/13/2007 06:16:30 Action: Incremental
09/13/2007 06:16:30 Objects:
09/13/2007 06:16:30 Options:
09/13/2007 06:16:30 Server Window Start: 06:00:00 on 09/14/2007
..................................
09/13/2007 06:16:30 Scheduler has been stopped.

 

[eavesrb]

TSM scheduler and rc=4.

I was hoping to validate on this site, but still not certain. I was kind of the opinion that since I am using the CAD to manage the scheduler that it doesn't know how to send a normal shutdown of the TSM scheduler. After reading the comments, perhaps it is related to open files. We don't exclude every open file from our servers and we don't have open file support enabled.

I am going to write a script to see if any of my 77+ Windows servers ever stop the scheduler without the error.