ADSM-L

Re: 'Skipping Invalid filename...'

1997-09-09 17:22:57
Subject: Re: 'Skipping Invalid filename...'
From: "Booher, Joelle M" <jmbooher AT AMP DOT COM>
Date: Tue, 9 Sep 1997 17:22:57 -0400
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\Registryø?'
>09/08/1997 19:20:14  FioGetOneDirEntry(): *** Skipping Invalid filename:
>'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\RECYCLED\desktop.ø?'
>09/08/1997 19:20:14  FioGetOneDirEntry(): *** Skipping Invalid filename:
>'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\utility\scanfragø?'
>09/08/1997 19:20:16  FioGetOneDirEntry(): *** Skipping Invalid filename:
>'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\WINDOWS\CONFIG\GENERAL.
>ø?'
>09/08/1997 19:20:18  FioGetOneDirEntry(): *** Skipping Invalid filename:
>'E:\data\ATI\LANAdmin\Clone\MONSOON_OSR2_clone.0\WINDOWS\INF\OTHER\SHUTT
>LESø?
>
>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
>----------
<Prev in Thread] Current Thread [Next in Thread>