Discover scan errors out during PST file scans “Unknown Error -- System error 64 has occurred."

book

Article ID: 160114

calendar_today

Updated On:

Products

Data Loss Prevention Network Discover

Issue/Introduction

While performing scans on PST files, the Filereader (FR) times out when scanning some PSTs, restarts, tries again, restarts, then gets the error when mounting to the same drive letter “Unknown Error -- System error 64 has occurred. The specified network name is no longer available”. After getting the error 64, the scan moves on to the next share in the scan target.

 

 Jul 12, 2011 12:08:41 PM com.vontu.directorycrawler.sharepointmapper.GenericSharePointMapper mapDrive

WARNING: Command Standard Output: status:2

 

Command Standard Error: System error 64 has occurred.

 

The specified network name is no longer available.

 

Jul 12, 2011 12:08:41 PM com.vontu.directorycrawler.AbstractFileSystemCrawler processContentRoot

WARNING: error processing content root

java.lang.Throwable: Unknown Error -- System error 64 has occurred.    The specified network name is no longer available.

 at com.vontu.directorycrawler.VontuFileException.<init>(VontuFileException.java:121)

 at com.vontu.directorycrawler.sharepointmapper.GenericSharePointMapper.mapDrive(GenericSharePointMapper.java:282)

 at com.vontu.directorycrawler.sharepointmapper.SharePointMapper.mount(SharePointMapper.java:58)

 at com.vontu.directorycrawler.AbstractFileSystemCrawler.mountShareIfNecessary(AbstractFileSystemCrawler.java:613)

 at com.vontu.directorycrawler.AbstractFileSystemCrawler.processContentRoot(AbstractFileSystemCrawler.java:447)

 at com.vontu.directorycrawler.AbstractFileSystemCrawler.processContentRoots(AbstractFileSystemCrawler.java:268)

 at com.vontu.directorycrawler.AbstractFileSystemCrawler.crawl(AbstractFileSystemCrawler.java:207)

 at com.vontu.directorycrawler.FileSystemCrawler.crawl(FileSystemCrawler.java:82)

 at com.vontu.discover.crawler.AbstractCrawler$1.run(AbstractCrawler.java:158)

 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

 at java.util.concurrent.FutureTask.run(FutureTask.java:138)

 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

 

 at java.lang.Thread.run(Thread.java:619)

Resolution

 

Solution:

 This seems to occur due to timing issues. The scan in fact finishes the scan process but fails to communicate the information back  in a timely manner.

In order to let the process properly handle the scanning, the follownig modifications may address the issue

 

 

0.      In the UII under the Advanced Settings set BoxMonitor.HeartbeatGapBeforeRestart to 180,000

1.       Add “crawler.maxstartrecount=0” to Vontu/Protect/config/crawler.properties

2.       Restart the VontuMonitor service on the discover server.

3.       Run the scan.