11-10-2010 05:32 AM
I've created an archive all policy for a folder structure with lots of files with no file extension. They appear to have archived but t would appear to me that EV cannot create placeholders for files with no file extension. Can anyone confirm if this is the case please.
11-10-2010 05:39 AM
11-10-2010 06:11 AM
Sigh, I've read the logs and dtraced the placeholder service. The logs don't appear to show anything and the dtrace shows lots of "Failed to get the .exe name for PID: 4" errors which is I think where it is trying to process these files but as there is never a file name in the log it is impossible to tell. I'll rephrase the question, has anyone successfully archived and created placeholders for files with no extension.
11-10-2010 08:25 AM
well what do the logs say for the items in question though? does it look like it thinks it has shortcutted them? because you said the error for PID is in the dtrace but not the logs right? but the logs must mention the file name and if theres an error associated with it, it should print it, unless it literally just isn't logging it full stop
Also after the Fail get PID error, it should give you an error number and not just the PID, what does it show? i think though its a red herring to be honest
11-10-2010 08:33 AM
for what its worth, i believe the Failed to get the name for PID is caused when the PlaceHolder Service tries to determine what application/executable is attempting to retrieve an item and determine whether its on the ignore executable list
For instance you may wish to stop the anti-virus from recalling placeholders, so you set AVScanner.exe or something to the exclude list, then when a recall is made it says "Are you AVScanner.exe because if you are then i'm not going to let you recall the file" etc, its basically to stop a process from mass recalling items
So what it sounds like to me is that the items are actually getting archived and turned in to placeholders but some other process is recalling them
PID 4 based on a couple of machines i checked with Process Explorer appears to be SYSTEM