If the Error 137 ... is in the dsierror.log, this is normal and is documented in the readme.
I've opened a problem with Tivoli on the 4099 error message in the application event log. It doesn't really seem to be an error either - just an erroneous message. Is something actually not working for you or are you just getting these messages? I get these messages but all works fine for me. Tim Rushforth City of Winnipeg -----Original Message----- From: Bruce Kamp [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 6:38 AM To: [EMAIL PROTECTED] Subject: NT 4.1.2.20 Client I'm having problems upgrading my NT/2000 clients. Environment TSM ver 4.1.3.2 on AIX 4.3.3 Clients NT SP6a & Win2k SP1 & 2. In the app event logs I keep getting the following error: ID 4099 Scheduler exited unexpectedly with a result code of 0. In the error log I see this: 02/12/2002 06:07:29 sessOpen: Error 137 from signon authentication. This is the contents of my dsmsched.log: 02/12/2002 06:07:30 Scheduler has been started by Dsmcad. 02/12/2002 06:07:30 Querying server for next scheduled event. 02/12/2002 06:07:30 Node Name: PATHOLOGY-SQL 02/12/2002 06:07:30 Session established with server TSMSERV: AIX-RS/6000 02/12/2002 06:07:30 Server Version 4, Release 1, Level 3.2 02/12/2002 06:07:30 Server date/time: 02/12/2002 06:09:09 Last access: 02/12/2002 06:09:09 02/12/2002 06:07:30 --- SCHEDULEREC QUERY BEGIN 02/12/2002 06:07:30 --- SCHEDULEREC QUERY END 02/12/2002 06:07:30 Next operation scheduled: 02/12/2002 06:07:30 ------------------------------------------------------------ 02/12/2002 06:07:30 Schedule Name: PATHOLOGY-SQL 02/12/2002 06:07:30 Action: Incremental 02/12/2002 06:07:30 Objects: 02/12/2002 06:07:30 Options: -preschedulecmd=D:\wins\1\backup\bkuppre.cmd -postschedulecmd=D:\wins\1\backup\bkuppost.cmd 02/12/2002 06:07:30 Server Window Start: 01:00:00 on 02/13/2002 02/12/2002 06:07:30 ------------------------------------------------------------ 02/12/2002 06:07:30 Scheduler has been stopped. I have tried updating the node password on TSM then on the client. I have tried taking out the password generate option & updating then but nothing seems to be working...... Also on my Citrix farm the nodes keep contacting my TSM server about every 10min all day long (open incident with Tivoli)!!! Any help will be greatly appreciated!!! Thanks, ------------------------------------ Bruce Kamp Network Analyst II Memorial Healthcare System P: (954) 987-2020 x6008 E: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ------------------------------------
