cancel
Showing results for 
Search instead for 
Did you mean: 

EV Placeholder Service not available

Roger_Goult
Level 3

Hi , I'm having a bit of an issue with our EV FSA archiving tasks .

Scenario :

EV Server :

Windows server 2008, EV 11.0.0

Target Server :

Windows Server 2012, Basic File Shares, running EV Placeholder server ver 11.0.0

Issue :

End users are having no issues at all recalling archived files, but when the archiving tasks run the logs are showing " the place holder service is not available "

Snippet from log file :

"image002.jpg cannot be made a placeholder as the placeholder service for file server: xxxxxxxxxxxxxx is not available "

The placeholder service itself is running fine, and like I said , end users have no issue opening archived files ...

I have reinstalled the EV agent on the target server and rebooted it .

I have recreated the tasks on the EV Server .

But no change ...

Any thoughts ?

 

Cheers

1 ACCEPTED SOLUTION

Accepted Solutions

Ben_Watts
Level 6
Employee Accredited

Looks like you are facing the issue discussed in the below technote:-

http://www.symantec.com/docs/TECH230048

 

Solution
This issue has been addressed in the following release:
Enterprise Vault 11.0.1 Cumulative Hotfix 2 Release

View solution in original post

5 REPLIES 5

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

So obviously this worked at one time.  Can you do a dtrace of a run now against the file system?

Roger_Goult
Level 3

Hi Tony , yep definitley was working ...

Here is a snippet fron the dtrace :


Enabled Trace options

Id    Name                                     Detail     Include Events
4   - EvPlaceholderService                     Verbose    Yes        


198 10:17:41.330  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeName: Trying to get the .exe name for pid: 4
199 10:17:41.330  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeNameUsingPHHelper: entry - PID:4
200 10:17:41.346  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeNameUsingPHHelper: Failed to get .exe name for pid [4] using IPlaceholderSvcHelper, error: 0x80070005
201 10:17:41.346  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeNameUsingPHHelper: exit - PID:4, exe name:
202 10:17:41.346  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeNameUsingEnumProcessModules: The .exe name for for pid: 4 is
203 10:17:41.346  [3232] (EvPlaceholderService) <2908> EV:M WorkItem::GetExeName: The .exe name for for pid: 4 is

There seems to be this recuring pattern for each file it trys to process that ends with the snippet above ...

There is also a mention of :

885 10:33:45.676  [3232] (EvPlaceholderService) <2908> EV:M FilterGetMessage() returned [800703e5] : Overlapped I/O operation is in progress.

I'm a bit perplexed ...

 

 

 

 

 

 

 

 

 

Roger_Goult
Level 3

Oh , just noticed this right at the top of the DTrace ...

 

2 10:09:54.423  [3232] (EvPlaceholderService) <5060> EV:H {CWmiMsftDedupVolume::CWmiMsftDedupVolume:#30} Error while connecting to WMI namespace. Error [0x8004100e]

That could be an issue , but doesnt explain why some functions of the placeholder service work fine ...

 

 

 

Ben_Watts
Level 6
Employee Accredited

Looks like you are facing the issue discussed in the below technote:-

http://www.symantec.com/docs/TECH230048

 

Solution
This issue has been addressed in the following release:
Enterprise Vault 11.0.1 Cumulative Hotfix 2 Release

Roger_Goult
Level 3

Thanks guys ...

I have a change veto at the moment , but come September Have to deploy that Hotfix for ather reasons too !

Thanks so much for the help !

Cheers