FSARunNow cannot process FileServerEntryId as determining parameter

Problem

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 Message

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

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)