I have also seen something similar when there was real damage in the
Windows directory.
If you don't see a file exceeding 255 chars as Andy suggested, try
running the Windows SCANDISK utility against that drive to check for
disk errors.

Also, sometimes when you get to this point, it is easier to find out
exactly which file is causing the problem by starting the GUI interface
and clicking down the file tree doing some selective backups until you
find what fails.

Good luck!


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================


> ----------
> From:         Andrew Raibeck[SMTP:storman AT us.ibm DOT com]
> Sent:         Friday, March 13, 1998 8:01 PM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Re: Strange error message
>
> My guess is that you have a file exceeding 255 characters in length.
> Check the
> "D:\people\brian_squillace" directory and see if this might be the
> case.
> Historically, I've seen these internet history or cache directories.
>
> One solution is to rename the file to something that is 255 characters
> or less.
> This file name includes the entire path, by the way.
>
> Another alternative is to install the V3 client (if you're not already
> there),
> then use EXCLUDE.DIR statements like this:
>
>      EXCLUDE.DIR "*:\...\Microsoft Internet\cache"
>      EXCLUDE.DIR "*:\...\Microsoft Internet\history"
>
> (note that these are examples where internet cache and history files
> cause
> problems; these files typically don't need to be backed up, anyway.)
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
>
>  ADSM-L AT VM.MARIST DOT EDU
>  03/13/98 01:04 PM
> Please respond to ADSM-L AT VM.MARIST DOT EDU @ internet
>
> To: ADSM-L AT VM.MARIST DOT EDU @ internet
> cc:
> Subject: Strange error message
>
> Marita Gonsalves
> Information Systems Consultant - CA
> 919-677-1946 x4555
>
>         Our ADSM Daily Incremental backups have failed for the last
> couple of days - here's an excerpt from the dsmerror.log:
>
>         03/13/1998 02:54:10 TransWin32RC(): Win32 RC 234 from
> FioGetOneDirEntry(): getFileSecuritySize
>         03/13/1998 02:54:10  PrivIncrFileSpace: Received rc=131 from
> fioGetDirEntries:  D:\people\brian_squillace
>         03/13/1998 02:54:10  ANS4031S Internal program error.  Please
> see your service representative.
>         03/13/1998 02:54:10  ANS4031S Internal program error.  Please
> see your service representative.
>         03/13/1998 02:54:12  ANS4847E Scheduled event 'DAILY_INCR'
> failed.  Return code = 4.
>         03/13/1998 08:45:24  TcpFlush: Error 10054 sending data on
> Tcp/Ip socket 116.
>         03/13/1998 08:45:24  sessRecvVerb: Error -50 from call to
> 'readRtn'.
>         03/13/1998 08:45:24  TcpFlush: Error 10054 sending data on
> Tcp/Ip socket 116.
>
>         What does this error message mean?
>
>         I tried doing a manual backup and just before it gets to
> D:\people\brian_squillace, I get an ADSM
>         Error message that says "Internal system error. Report how you
> got this."  The dsmerror log for the manual backup is as follows:
>
>         03/13/1998 10:15:40  TransWin32RC(): Win32 RC 33 from
> FileRead(): ReadFile
>         03/13/1998 10:15:54  TransWin32RC(): Win32 RC 234 from
> FioGetOneDirEntry(): getFileSecuritySize
>         03/13/1998 10:15:54  PrivIncrFileSpace: Received rc=131 from
> fioGetDirEntries:  D:  \people\brian_squillace
>         03/13/1998 10:32:37  TcpFlush: Error 10054 sending data on
> Tcp/Ip socket 140.
>         03/13/1998 10:32:37  sessRecvVerb: Error -50 from call to
> 'readRtn'.
>         03/13/1998 10:32:37  TcpFlush: Error 10054 sending data on
> Tcp/Ip socket 140
>
>         Any help would be greatly appreciated.
>
>         Thanks,
>         Marita
>
>
>
>