ADSM-L

Re: [ADSM-L] TSM Scheduler Service in 'Stopping' state

2008-03-16 18:48:09
Subject: Re: [ADSM-L] TSM Scheduler Service in 'Stopping' state
From: "Pahari, Dinesh P" <dinesh.pahari AT EDS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 17 Mar 2008 09:47:09 +1100
Thank you for your swift response.
The server was rebooted intentionally after a regular maintenance. There
are no significant errors reported in the event viewer. Similarly, TSM
activity log has recorded nothing since the reboot and no errors are
reported for the error occurred.
FYI below
Event Viewer: 
        Source: AdsmClientServiceTSM 
        Message: Scheduler halter right after the reboot.
Dsmerror.log: 
03/02/2008 04:03:14 ConsoleEventHandler(): Caught Shutdown console event
.
03/02/2008 04:03:14 ConsoleEventHandler(): Cleaning up and terminating
Process ...
03/02/2008 05:09:46 ConsoleEventHandler(): Caught Shutdown console event
.
03/02/2008 05:09:46 ConsoleEventHandler(): Cleaning up and terminating
Process ...

Dsmsched.log:
>>>>>> Process Interrupted!!  Severing connection. <<<<<<


Regards,
Dinesh Pahari
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Monday, 17 March 2008 9:05 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Scheduler Service in 'Stopping' state
Importance: High

On Mar 16, 2008, at 5:59 PM, Pahari, Dinesh P wrote:

> Hi All,
> I had a Windows 2003 client (with TSM client 5.3.2)rebooted last week.
> Since the reboot, the TSM (client) stopped working. I tried to restart
> the service but it went on STOPPING state and wouldn't respond. Even
> the
> TSM GUI doesn't start.
> Due to the criticality of the client, I am not able to perform the
> reboot.
> Is there  anyway, I can make TSM work again with out a reboot ?
>
> Would really appreciate your help.

Tell us what diagnosis you've done...
What's in the dsmerror.log and dsmwebcl.log files. Any indications of
problems in the Windows Event Log? (There may be more wrong in the
system than just TSM executability after that reboot.) Evaluate the
circumstances of the reboot: if it was actually a crash, or forced
reboot after a hang, there can be prevailing issues.
Is the dsmerror.log writable, in a writable directory, as directed by
your options file?  (If not, you'll have problems.)

     Richard Sims

<Prev in Thread] Current Thread [Next in Thread>