i!  I have gotten this message several times. We are at ADSM 3.1.1.3
on the server and 3.1.02 at the client. When I get this message, it seems to
keep recurring. And it is always the same file. It is not intermittent.  To
prevent it, I put in an EXCLUDE for the file referenced in the message.  My
theory is that the message is caused by the number of directories that ADSM
has to go through to get to the file. I think that there is some upper
limit.  A LAN Administrator theorized to me once, when we were talking about
this error message, that he thought there was limnit of 256 characters in
the path name that ADSM uses to read files. I'm not  certain what causes the
message, but the EXCLUDE definitely will work using the path and file name
referenced in the message.

        We will be upgrading very soon to server 3.1.2.20 and client 3.1.06.
I'll see if I can remove my EXCLUDEs.

        The message that I cannot do anything about (and that causes our
backup sessions to fail is
ANS1301E  Server detected system error.  IBM has this problem on their
database, but their only recommendation to prevent it is to upgrade to the
current server software. They also recommend that we upgrade to the most
current client software before we upgrade the server software.
John

John Morlier
Manager of Technical Services and Operations Support
, Integrated Product Data Environment

Avondale Industries, Inc.
IPDE Technology Division

%   Voice: (504) 436-5213
*  Fax:  (504) 437-5534
):    Email:  jmmorlier AT avondale DOT com <kgmyers AT avondale DOT com>


        -----Original Message-----
        From:   Robert Greig [SMTP:robert.greig AT NATPOWER DOT COM]
        Sent:   Tuesday, April 13, 1999 10:24
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        ANS1256E Cannot make file/directory

        Hi,

        I'm having a major problem when backing up my Users data.  ADSM gets
to
        the same point and stops the whole backups.  Therefore at the moment
it
        backs up all the users up to the point of stopping and NO others.  I
am
        in desperate need of help.

        Has anyone had this problem before ??? The messages I receive are
shown
        below, I am convinced it is a corrupt file but why does ADSM not
skip
        over it ???

        note: names/directories have been changed to protect the innocent !!


        13-04-1999 01:03:06 TransWin32RC(): Win32 RC 123 from
fioScanDirEntry():
        getFileSecurityInfo
        13-04-1999 01:03:06 PrivIncrFileSpace: Received rc=167 from
        fioGetDirEntries:  E:  \users\bees3\My
        Documents\Tons\Gen\1998_unit1_generator_build_october\cache
        13-04-1999 01:03:06 ANS1256E Cannot make file/directory
        13-04-1999 01:03:06 ANS4028E Error processing 'E:': cannot create
        file/directory entry
        13-04-1999 01:03:06 ANS1512E Scheduled event 'DAILY_INCR' failed.
        Return code = 4.


        Thanks,

        Rob

        Phone: 01793 - 894142
        E-mail: robert.greig AT natpower DOT com