ADSM-L

Re: TSM Journal Service communication failure

2005-11-28 14:57:32
Subject: Re: TSM Journal Service communication failure
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 28 Nov 2005 14:56:11 -0500
Uwe -

Those messages are helpful...
Windows error 233 is ERROR_PIPE_NOT_CONNECTED, which says
      "No process is on the other end of the pipe".
Assuming that the dsmerror.log message was written by the B/A client,
it means that the Journal Service disappeared (died).  Perhaps the
Windows Event Log tells why (possibly a space issue?).  In any case,
restart it, and keep an eye on it to see if it consistently fails
under similar conditions.

   Richard Sims, not a Windows expert

On Nov 28, 2005, at 2:37 PM, Uwe Koch wrote:

Hello Richard,

thanks for the fast answer. But in the dsmerror.log only these entries
appear very fast repeating :
...
11/25/2005 18:34:08 win32NpWrite(): Error 233 writing to named pipe
11/25/2005 18:34:08 win32NpWrite(): Error 233 writing to named pipe
11/25/2005 18:34:08 win32NpWrite(): Error 233 writing to named pipe
...

I just don't know what this means. Is there a TSM config setting or a
windows registry parameter to avoid this ?

Life should have an EncounterNoProblems option, but...

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