We are currently running Symantec DLP v11.1 for the following products: Network Monitor, Network Discover, Network Protect and Network Prevent for E-mail on Win Server 2003 R2 Standard Ed (x86). I recently added five (5) new Exact Data profiles. The source files column separators are a combination of tab and comma delimiters. The indexing is scheduled to kick-off early in the morning, outside of production hours. All five (5) jobs blew off as a result of the error. I have reviewed the source files, with either .txt or .csv file types, and find nothing out of the ordinary. In the initial field mappings, I added several custom fields that are conducive to said source files. Since the source files are staged on a seperate server than the Exact Data profile, does the error potentially reflect a comm issue between both servers? If not, then is this related to the data structure in the source files? After reviewing the log files, I see that in one of the EDM jobs that blew off, I received the following entry for one of the jobs that I was trying to run, and this is consistent with the other four (4):
30 Sep 2011 04:00:02,809- Thread: 25 INFO [com.vontu.profiles.manager.InfoSourceIndexJob] Indexing InfoSource Job begin executing
30 Sep 2011 04:00:02,914- Thread: 25 SEVERE [com.vontu.profiles.manager.InfoSourceIndexCreator] Data file for exact data profile "MK Dept Import FB User names and Emails " version 1 could not be found.
Can someone explain the "version 1" and how it relates to the Version 1 in the error above? Could this be why it's not running?
Thanks in advance
venetian_jigsaw