Look for Dr. Watson errors. I found that changing backupregistry to no in
the dsm.opt file made the program go away. Not a fix but a working
band-aid.
Jim Murray
Senior Systems Engineer
Liberty Bank
[EMAIL PROTECTED]
(860)638-2919
"Never trust a computer you can't throw out
a window." - Apple co-founder Steve Wozniak
-----Original Message-----
From: Selva, Perpetua [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:52 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
Hi
Thanks for all the responses.. However, i have tried everything that has
been suggested.
I'm puzzled... Could it be something to do with the Version i'm running..
Server 3.1.2.20 and
Client 3.1.08
Thanks in Advance
-----Original Message-----
From: Palmadesso Jack [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
You may want to try removing and reinstalling the service with the dsmcutil
command.
As to why it stopped in the first place look in the nt event viewer also
review your activity log on the server. Also look in the dsmsched.log and
dsmerror.log if you have not.
Jack
-----Original Message-----
From: Selva, Perpetua [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:34 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
There is no specific errors that seem to point to anything unusual.. One day
it will work, the other day, it won't.. Sometimes 'it says client severed',
at other times, it has missed schedules. Whatever the case maybe, the
client server's adsm scheduler would have stopped by itself..
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 10:27 AM
To: [EMAIL PROTECTED]
Subject: Re: ADSM SCHEDULER
>Can someone please let me know why the 'adsm scheduler' would stop for no
>reason .. especially on an NT4.0 running metaframe/winframe applications..
I don't have a specific answer for you, but would seek out any dsmerror.log
indications that may be left behind. Richard
