Michael,
thanks for your mail. There was actually a file with an unreadable
filename.
After deleting this file the backup runs just fine.
Thanks again!

Thomas Rupp

> -----Ursprüngliche Nachricht-----
> Von:  Michael Bartl [SMTP:michael.bartl AT ZENTRALE.ADAC DOT DE]
> Gesendet am:  Dienstag, 25. August 1998 20:21
> An:   ADSM-L AT VM.MARIST DOT EDU
> Betreff:      AW: "ANS1256E Cannot make file/directory" during backup
> 
> Thomas,
> sounds like you're using the NT V3 PTF3 Client...
> This client has a problem with corrupted filenames.
> When you issue a DIR on the directory WINNTT01 the you likely will see
> a
> file containing a "?" in the filename.
> After you delete or rename this file, ADSM will work fine again.
> Unfortunately the PTF3 client does not just skip the file but skippes
> the
> whole rest of the filespace...
> So you probably better do a "DIR /a /s" on your filespace and "GREP"
> for all
> "?" to get all those corrupted filenames in one session.
> 
> In PTF5 this problem is fixed, but there are a few new bug
> implemented. So
> you better wait until this or next week a fix for PTF5 gets released.
> To get
> more information, read the latest messages titled "Win32 client bug"
> in this
> list.
> 
> Regards,
> Michael
> --
> Michael H. Bartl
> ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
> Tel.: (089) 7676-4063, Fax: (089) 7676-8161
> EMail: Michael.Bartl AT Zentrale.ADAC DOT de
> 
> > ----------
> > Von:  Rupp Thomas (Illwerke)[SMTP:thomas.rupp AT ILLWERKE.CO DOT AT]
> > Gesendet:     Dienstag, 25. August 1998 20:07
> > An:   ADSM-L AT VM.MARIST DOT EDU
> > Betreff:      "ANS1256E Cannot make file/directory" during backup
> >
> > Hi to all,
> >
> > One of my scheduled backups (client: WIndows NT) returns the
> following
> > messages in DSMERROR.LOG
> >
> > TransWin32RC(): Win32 RC 123 from fioScanDirEntry():
> getFileSecurityInfo
> >
> > PrivIncrFileSpace: Received rc=167 from fioGetDirEntries:  C:
> \WINNTT01
> >
> > ANS1256E Cannot make file/directory.
> >
> > Returncode 123 means:
> > The filename, directory name, or volume label syntax is incorrect
> >
> > Returncode 167 means:
> > Unable to lock a region of a file.
> >
> > The scheduler is running under the system account. The text
> > "getFileSecurityInfo" makes me feel that some kind of authorization
> is
> > missing.
> > Should I talk to our Windows NT guru's?
> >
> > Kind regards
> > Thomas Rupp
> > Vorarlberger Illwerke AG
> > MAIL:   thomas.rupp AT illwerke.co DOT at
> > TEL:    ++43/5574/4991-251
> > FAX:    ++43/5574/4991-820-8251
> >