I had somewhat of a similar problem on an NT 4.0 client with TSm 3.7 or 4.1 but
not Domino. Just regular File INC. The dsmsched.log file was real big and an
error occured one night. After that the backup wouldn't run. I would get
(it's been a few months) some kind of access violation or similar errors.
Tried several things even with out NT admin , even he couldn't delete
dsmsched.log. Final solution was to reboot machine and delete dsmsched.log and
restart schedule service. Problem solved.
David Longo
>>> vint.maggs AT SRS DOT GOV 06/13/01 01:44PM >>>
Hello All,
We have been troubleshooting problems with three of our Domino servers
without luck. At one point all was well but gradually the backups began
failing. Nothing has changed on the TSM server side so the thinking is it
must be a client problem. Various schedules are failing with no apparent
reason. We are running TSM 3.7.3.0 on Solaris 2.7. The clients are
running NT 4.0, Lotus Domino R5, and Domino TDP 1.0.
Prior to this morning, schedules were failing, though not the same
schedules. On one server the daily incremental schedule is failing while
on others the hourly archive is failing. As a work around we could run a
backup from the gui and it worked.
This morning, we broke down what occurs when the scheduled backup runs and
realized that it kicks off the domarc.cmd at the required interval. All
commands (domarc, dominc, domina) use the same .cfg and .opt file for the
specific node. I executed the domarc.cmd file for SERVER A from a DOS
window and the Dr. Watson appeared. I then tried just the statement that
runs the job (start /B domdsmc archivelog... excluding the log locations)
and it ran fine. So this backed me into the log files. I changed the log
file name and paths and when executing the domarc.cmd file it ran as
expected. I duplicated this scenario on SERVER B (which has also been a
problem child) and again it fixed the problem as well. I then went to
SERVER C and did the same for the dominc.cmd that has been failing. Before
making the changes the Dr. Watson appeared. After making the changes and
executing the command in a DOS window it ran without the error on all
three servers.
So with all of that discourse, what gives with the .log files? The Dr
Watson is usually an access violation error. Is the log file in an open
state from an earlier failure, thus since it can't write it just stops
goes no further? If this were the case, why does it right some of the
information (i.e. Valid License File....) before the Dr. Watson error
occurs?
Anyone else experience this?
Thanks,
Vint
"MMS <health-first.org>" made the following
annotations on 06/13/01 14:23:16
------------------------------------------------------------------------------
---
This message is for the named person's use only. It may contain This message
is for the named person's use only. It may contain confidential, proprietary,
or legally privileged information. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this message in error, please
immediately delete it and all copies of it from your system, destroy any hard
copies of it, and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient. Health First reserves the right to monitor all
e-mail communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where the
message states such views or opinions are on behalf of a particular entity;
and (2) the sender is authorized by the entity to give such views or opinions.
==============================================================================
|
