FSARunNow cannot process FileServerEntryId as determining parameter

Article:TECH202124  |  Created: 2013-01-28  |  Updated: 2014-10-06  |  Article URL http://www.symantec.com/docs/TECH202124
Article Type
Technical Solution


Issue



When using FSARunNow from CMD or within a batch if FileServerEntryId is used as the determining parameter, the execution of the Task will not be successful

 


Error



No volumes found for file server 10C1D3D52D0994E47A1A811D7F66A99E01z10000Evserver and volume 1

 


Cause



Workaround:

 

Use TaskName or TaskEntryId instead


Solution



This issue has been addressed in the following release:
 
Enterprise Vault 10.0.4 - Release Details
http://www.symantec.com/docs/DOC6317

Supplemental Materials

SourceETrack
Value3064854
Description

FSARunNow cannot process FileServerEntryId as determining parameter



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


Terms of use for this information are found in Legal Notices