Re: ADSM v3 client with NT

Andy,

I checked the three things you mentioned and they all are ok.

As far as number 4, here is a snippet from the server log:
07/31/1998 16:18:55 ANR0400I Session 6776 started for node LSBURKE
(WinNT).
07/31/1998 16:20:19 ANR0400I Session 6777 started for node LSBURKE
(WinNT).
07/31/1998 16:22:29 ANR0400I Session 6778 started for node LSBURKE
(WinNT).
07/31/1998 16:24:40 ANR0400I Session 6779 started for node LSBURKE
(WinNT).
07/31/1998 16:28:34 ANR0400I Session 6781 started for node LSBURKE
(WinNT).
07/31/1998 16:30:32 ANR0400I Session 6783 started for node LSBURKE
(WinNT).
07/31/1998 16:32:41 ANR0400I Session 6784 started for node LSBURKE
(WinNT).
07/31/1998 16:34:21 ANR0482W Session 6776 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:34:50 ANR0400I Session 6785 started for node LSBURKE
(WinNT).
07/31/1998 16:35:21 ANR0482W Session 6777 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:36:51 ANR0400I Session 6786 started for node LSBURKE
(WinNT).
07/31/1998 16:37:56 ANR0482W Session 6778 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:38:50 ANR0400I Session 6787 started for node LSBURKE
(WinNT).
07/31/1998 16:40:02 ANR0482W Session 6779 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:41:05 ANR0400I Session 6790 started for node LSBURKE
(WinNT).
07/31/1998 16:42:02 ANR0482W Session 6780 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:43:15 ANR0400I Session 6792 started for node LSBURKE
(WinNT).
07/31/1998 16:44:04 ANR0482W Session 6781 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:45:30 ANR0400I Session 6797 started for node LSBURKE
(WinNT).
07/31/1998 16:45:34 ANR0482W Session 6783 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.
07/31/1998 16:48:05 ANR0482W Session 6784 for node LSBURKE (WinNT)
terminated - idle for more than 15 minutes.

Don't know if that'll help give any leads or not.  Thanks again for
looking into it.

-Chad
Andrew Raibeck wrote:
Andrew Raibeck wrote:
>
> Hi Chad,
>
> I'm not exactly sure what is going on here, but please check a few things:
>
> 1) Verify that the user ID you are logged in as has these rights:
>
> Backup files and directories
> Restore files and directories
> Manage auditing and security logs
>
> 2) Make sure the ID has access to the root of the C: drive.
>
> 3) Try using the Administrator ID and see if that works (assuming that you
> aren't using Administrator).
>
> 4) You still should see what is going on on the ADSM server when this
> problem occurs.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
> ADSM-L AT VM.MARIST DOT EDU on 07/30/98 11:10:19 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Re: ADSM v3 client with NT
>
> Thanks for the response Andy,
>
> Here is a sample of what is in the dsmerror.log, there seem to be two
> sets of errors:
>
> 07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
> 07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
> 07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
> 07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
> 07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
> 07/30/1998 11:25:11 TcpRead: Error reading data, rc: 10054
> 07/30/1998 11:25:11 sessRecvVerb: Error -50 from call to 'readRtn'.
> 07/30/1998 11:25:11 ANS1809E Session is lost; initializing session
> reopen procedure.
> 07/30/1998 11:25:11 ANS1809E Session is lost; initializing session
> reopen procedure.
> 07/30/1998 11:25:26 ANS1810E ADSM session has been reestablished.
>
> ...
>
> And then:
>
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\adsm.sys' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\HPFonts' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Internet Explorer 4.0
> Setup' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Multimedia Files'
> failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\NTRESKIT' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Program Files' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\RECYCLER' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\SQLLIB' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\TEMP' failed
> 07/30/1998 12:06:11 ANS1228E Sending of object 'C:\WIN32APP' failed
>
> I'm not sure about the server logs, versions, etc.  I'm trying to get in
> contact with the person in charge of that...
>
> As far as other NT clients, we have other clients that do not get this
> error.  However,  we have one NT client that is failing with a different
> error.  That one recieves "ANS1030E System ran out of memory. Process
> ended."  I'm not sure if that's related or not.
>
> Thanks for the ideas and help,
> Chad
>
> Andrew Raibeck wrote:
> >
> > Hi Chad,
> >
> > You should check a couple of items:
> >
> > 1) dsmerror.log - what messages are in here that accompany the failure?
> >
> > 2) ADSM server activity log - what messages accompany the failure? Typically
> > I'd expect to see some kind of ANR04xxx message, i.e. ANR0480W, ANR0481W,
> > ANR0482W, etc.
> >
> > Also, make sure your TCP/IP maintenance on MVS is up to date, as there are
> > several APARs that impact ADSM.
> >
> > Does this happen on other NT clients as well?
> >
> > Regards,
> >
> > Andy
> >
> > Andy Raibeck
> > IBM Storage Systems Division
> > ADSM Client Development
> > e-mail: storman AT us.ibm DOT com