ADSM-L

Re: Unable to open timer file

2005-05-16 12:45:36
Subject: Re: Unable to open timer file
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 16 May 2005 12:42:45 -0400
Shannon -

I don't have enough context on your environment, but it should like your site is not using the TSM Scheduler directly, but instead via the Client Acceptor Daemon. Per the client manual: "the CAD serves as an external timer for the scheduler. When the scheduler is started, it queries the server for the next scheduled event. The event is either executed immediately or the scheduler exits. The CAD restarts the scheduler when it is time to execute the scheduled event."

It may be that, if your backups have been running fine until now, that something was recently implemented on that W2K system that interferes with the creation of the timer file or removes it from under TSM. It might also be that CAD is not running with sufficient privs to create the timer file in the first place, but I'd expect you to see more messages.

See what's changed on that system (perhaps a more aggressive virus scanner). Look into the Windows Event Log for indications of odd stuff going on. Run the scheduler directly if need be.

   Richard Sims

On May 16, 2005, at 12:12 PM, Shannon Bach wrote:


One of the client admins here installed Windows TSM Client Version 5, Release 2, Level 4.0  on a Win2000 machine. All is okay for about 5 seconds then the TSM Scheduler service just stops.  The client dsmerror.log shows the following message;

UseExternalTimer:  Unable to open timer file '\s4l8.', errno=2, error:No such file or directory

That is the only error message that shows up anywhere.  The dsmsched.log only says that the scheduler was stopped. I've searched the IBM Information Center and Richard Sims ADSM/TSM QuickFacts but neither came up with any hits.  Has anyone else run accross this type of error before?  

Thanks in advance if any can help :~)
Shannon

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