I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4 Servers. I noticed that both the ADSM Remote Client Agent and ADSM Scheduler services stop by themselves. Their Startup option is A
Author: Gary Ison <Gary.Ison AT MAIL.STATE.KY DOT US>
Date: Thu, 24 Feb 2000 08:56:28 -0500
Check the dsmerror.log and dsmsched.log files for error messages about scheduler being stopped. They may also contain additional information about the condition causing the stoppage. Did you use the
Author: Tony Jules [SMTP:JULEST AT OLYMPUS DOT COM]
Date: Sun, 04 Oct 2015 17:33:44 -0500
I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4 Servers. I noticed that both the ADSM Remote Client Agent and ADSM Scheduler services stop by themselves. Their Startup option is A
Author: "Louie, James" <LouieJ AT NABISCO DOT COM>
Date: Thu, 24 Feb 2000 10:02:45 -0500
Check the logs in the adsm/baclient directory for clues. Usually it's problems with the node not defined on the ADSM server or a password problem. Good luck. James Louie Nabisco
What does the NT event log say about the ADSM scheduler service stopping? Larry Way SL09/100D 408-743-4242 voice 408-743-4201 fax I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4 S
Tony, The ADSM Scheduler service stopping, sounds like a problem. As others have stated, the logs may give you some insight as to what the problem is. The ADSM Remote Client Agent stopping is "workin
Author: "Mann, Joseph" <mannjo AT FOSTERFARMS DOT COM>
Date: Thu, 24 Feb 2000 09:01:32 -0800
There is a new client out that has fixed this problem for us. Also you might try reloading the service pack after you install the client. These are all lessons learned from our installation.
Author: Gary Ison [mailto:Gary.Ison AT MAIL.STATE.KY DOT US]
Date: Sun, 04 Oct 2015 17:33:44 -0500
Check the dsmerror.log and dsmsched.log files for error messages about scheduler being stopped. They may also contain additional information about the condition causing the stoppage. Did you use the
Hi Tony I had a similiar problem recently. If you run "dsmcutil query /name:'service name'" and verify that the services are starting with the correct nodename and password. My "scheduler" was starti
Author: Alessio Prodon <aprodon AT CENTROGESTIONE.G-NET DOT IT>
Date: Mon, 28 Feb 2000 13:29:26 +0100
You can try reinstall the Central Scheduler Service on NT using this form: From Prompt MS-DOS : dsmcutil install /name:"Central Scheduler Service" /name:namemachine /password:passwd /autostart:yes By
Author: Randy Fenrick <R.Fenrick AT LABSAFETY DOT COM>
Date: Tue, 29 Feb 2000 08:28:24 -0600
Also make sure that the NT account you have set up for the service has the ability to "Logon As Service". Did you ever get the SQL setup info you were looking for?
Author: Tony Jules [mailto:JULEST AT OLYMPUS DOT COM]
Date: Sun, 04 Oct 2015 17:33:44 -0500
I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4 Servers. I noticed that both the ADSM Remote Client Agent and ADSM Scheduler services stop by themselves. Their Startup option is A
I thank you for your reply. I found out that I had to install the Agent Scheduler manually using the DSMCUTIL uitlity, and that seems to work. As for the SQL, a Tivoli representative contact me yeste
Author: Tony Jules [mailto:JULEST AT OLYMPUS DOT COM]=20
Date: Sun, 04 Oct 2015 17:33:44 -0500
I recently installed ADSM Client ver3 release 1 level 0.7 on 2 NT 4 = Servers. I noticed that both the ADSM Remote Client Agent and ADSM Scheduler = services stop by themselves. Their Startup option