On Jul 16, 2008, at 11:31 AM, Matthew Large wrote:
Thanks Richard,
If I had left the number off the search string QuickFacts would have
appeared!..
The crashes seem to be happening at the same time those erroneous
files were written, so they want to eliminate TSM as a cause.
Although I totally
Thanks Richard,
If I had left the number off the search string QuickFacts would have appeared!..
The crashes seem to be happening at the same time those erroneous files were
written, so they want to eliminate TSM as a cause. Although I totally agree
with you - how can a few tiny file writes cau
In the Windows application log, is there any evidence of the acceptor
daemon crashing, and possibly orphaning the files? What version of TSM
is the client?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: 16 July 2008 14:37
To: ADSM
On Jul 16, 2008, at 9:18 AM, Matthew Large wrote:
... I can't figure out why these files are lying around here -
having checked their contents they contain messages like:
EXECUTE PROMPTED 1116
And
EXECUTE PROMPTED 1179
What are they? MS return codes?
Matthew -
See Client Acceptor Dae
Hi Ian,
(what happened on Sunday??)
Nothing of the sort - no traces, full privileges - I should have stated that it
is a W2K3 client.
If you watch a windows log directory after starting the dsmcad, you will see
these files get created and deleted very quickly..
Cheers,
Matthew
--
Matthew
Is there a schedlogmax defined, or any trace flag that may be configured
on the client?
What ID is the client running under, does it have the privileges to
remove temp files it may be able to create?
Ian
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behal
