We had a similar problem with a series files named \flow\nul
This is a file created in the users directory when they use a flow chart
program. On one of our two network file servers, all instances of this
file gave us an error like the one you wrote about, while the other
server had no problems with the file. We're not really sure what
corrected it, but the system administrator reset the permissions on the
first occurance of the file, to see if it made a difference (If I
remember right, all he did was grant access to our backup operators
group). The other failing files we're not changed, but the next time we
backed up the server, all instances of the file were sucessfully backed
up. We're still trying to figure out what caused the problem. You might
try looking and resetting the permissions on the first file to give you
an error to see if you get the same results we did.


Booher, Joelle M wrote:
>
> Dan,
>
> Thanks for the information!  Excluding the internet cache files will
> take us down to ONE problem!
>
> However, on the 'Invalid filename' thing...
>
> These files were backing up perfectly before.  The filenames didn't
> change, and they don't look like strange filenames in either explorer or
> a command prompt dir.  The errors only began two nights ago, and they
> are occurring on HUNDREDS of files - not just a few that were recently
> generated.  This client is a production NT file/print server with over
> 80Gb of data, and the files in question have extensions like .WK4, .TXT,
> .XLS, etc., etc.  These are not uncommon names, nor do they contain
> unrecognizable characters.  Only ADSM thinks they contain these
> characters.  I can open the spreadsheets with Excel, I can open the text
> files with Notepad, I can copy, rename and delete these files.  Also, if
> I open the ADSM GUI client, it sees the files with no problem - no funny
> names there....
>
> I don't know if it makes sense to me, but since the problem is occurring
> only in scheduled sessions, and not in the GUI client, I stopped and
> started the service.  Kind of a really stupid shot in the dark, but
> maybe worth a try?
>
> Thanks again for your help, and any other suggestions would be
> appreciated.
>
> Joelle Booher
> Amp Incorporated
> (717)810-2816
> jmbooher AT amp DOT com
>
> >-----Original Message-----
> >From:  Daniel Thompson [SMTP:thompsod AT USAA DOT COM]
> >Sent:  Tuesday, September 09, 1997 4:39 PM
> >To:    ADSM-L AT VM.MARIST DOT EDU
> >Subject:       Re: 'Skipping Invalid filename...'
> >
> >Joelle,
> >
> >  You seem to have 2 problems (as you probably already know).  The second I
> >see quite commonly.  The cache/history files used by web browsers commonly
> >generate filenames that ADSM cannot handle.  The only solution is to delete
> >these files when you see them.
> >
> >The problem you seem to have with the files with invalid filenames seems
> >valid.  The files in your error messages below seem to use some special
> >characters that I did not believe were valid.  I have experienced problems
> >where even the NT explorer and NT command line reported different levels of
> >success with oddly named files.
> >
> >I do not know if IBM is addressing these issues in the next fix/version.
> >
> >Good luck,
> >  Dan T.
> >
> >----------
> >From: Booher, Joelle M <jmbooher AT AMP DOT COM>
> >To: ADSM-L AT VM.MARIST DOT EDU
> >Subject: 'Skipping Invalid filename...'
> >Date: Tuesday, September 09, 1997 2:03 PM
> >
> >Hi Everyone.
> >
> >Thanks for the information on my previous questions about ANS4253E error
> >messages - I assumed that the answer would be to run chkdsk, just wanted
> >to make sure!
> >
> >NOW....we have an NT server that is getting the following error messages
> >on hundreds of files:
> >
> >09/08/1997 19:20:13  FioGetOneDirEntry(): *** Skipping Invalid filename:
> >'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\Program Files\Steven J.
> >Hoek Software Development\Registryx? '
> >09/08/1997 19:20:14  FioGetOneDirEntry(): *** Skipping Invalid filename:
> >'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\RECYCLED\desktop.x? '
> >09/08/1997 19:20:14  FioGetOneDirEntry(): *** Skipping Invalid filename:
> >'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\utility\scanfragx? '
> >09/08/1997 19:20:16  FioGetOneDirEntry(): *** Skipping Invalid filename:
> >'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\WINDOWS\CONFIG\GENERAL.
> >x? '
> >09/08/1997 19:20:18  FioGetOneDirEntry(): *** Skipping Invalid filename:
> >'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\WINDOWS\INF\OTHER\SHUTT
> >LESx?
> >
> >Later on we get:
> >
> >09/08/1997 19:41:10  TransWin32RC(): Win32 RC 234 from
> >FioGetOneDirEntry(): getFileSecuritySize
> >09/08/1997 19:41:10  PrivIncrFileSpace: Received rc=131 from
> >fioGetDirEntries:  E:  \data\WIS\WIS\PATCHES\TEST\Plus!\Microsoft
> >Internet\cache
> >09/08/1997 19:41:12  ANS4031S Internal program error.  Please see your
> >service representative.
> >09/08/1997 19:41:12  ANS4031S Internal program error.  Please see your
> >service representative.
> >09/08/1997 19:55:12  ANS4847E Scheduled event 'MONSOON' failed.  Return
> >code = 4.
> >
> >When I go out to look at the files, I can access them with no problem.
> >I can copy them, rename them, move them, access them through
> >applications, etc.  Does anyone have any idea why ADSM seems to see
> >their filenames as invalid????
> >
> >Thanks
> >Joelle Booher J
> >Amp Incorporated
> >(717)810-2816
> >jmbooher AT amp DOT com
> >----------