Files are seen as a 'non regular file' and skipped when scanning with Command Line Scanner

Article:TECH150661  |  Created: 2011-01-28  |  Updated: 2011-02-02  |  Article URL http://www.symantec.com/docs/TECH150661
Article Type
Technical Solution

Environment

Issue



When using the Command Line Scanner (CLS) for scanning files on a mapped drive, it is noticed that for some files an event ‘non regular file – skipped’ is generated.

 

 


Error



Using the ‘–verbose’ parameter when scanning with CLS, the ‘non regular file – skipped’ event  becomes visible:


\\192.168.40.22\design\security\package\archive\development\windows\templates\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\0123456789\LocalGroups.txt non regular file - skipped

 


Cause



The path to a file on a mapped drive consists of three parts, divided by back-slashes:
1. The IP address or the name of the computer (\\ip-address  or  \\computer- name\)
2. The list of folders and subfolders folder(\sub-folder\sub-folder\sub-folder …etc)
3. The file itself (file-name.extension)

The full path could look like this:
\\192.168.40.22\design\security\packages\archive\development\windows\templates\LocalGroups.txt

 

The ‘non regular file – skipped’ event happens when two conditions are fulfilled:

  1. The combined length of the computer name (or IP address) and folders excluding the file name is less than 256 characters.
  2. The combined length of the computer name (or IP address) and folders including the file name is more than 256 characters.

In those circumstances it is the file name that brings the total number of characters over, and that is when the error appears.


If the combined length of the computer name (IP address) and folders is more than 256 characters, Command Line Scanner will not 'see' the file, not scan the file and will report nothing.
 


Solution



The only solution is to make sure that the path is shorter. This can be done by:

  1. Shortening the path.
  2. Share a folder that is in the existing path ('closer' to the file), e.g. the folder that contains the file to be scanned, and map this folder instead of the main folder.

Supplemental Materials

Description

Command Line Scanner is a command driven tool that is part of the Symantec Scan Engine installation.



Article URL http://www.symantec.com/docs/TECH150661


Terms of use for this information are found in Legal Notices