Without the errorlog, it is difficult to diagnose. Try starting it in the foreground first. Open a windows command line, and run "dsmc sched". This will give you a good idea of what is going wrong. Also, look at the dsmwebcl.log and dsmsched.log. It could be a simple password issue.
To answer your question, I have not had any problems with upgrades of clients after applying the 5.5.2.2 fix patch. I have on occasion seen some issues where a registry setting was lost, and the TSM services had to be removed and readded, if that helps at all. Gary On Aug 10, 2009, at 12:17 PM, TSM wrote:
Hello, windows client-schedules do not start. We use dsmcad and schedmode=prompt. There is no special error message. With client version 5.5.2.1 the schedules are working succesfull. I'm wondering, if there is a problem with the tsm client 5.5.2.2 ? Has anybody else the same problem? with best regards andreas