FSARunNow cannot process FileServerEntryId as determining parameter
| Article:TECH202124 | | | Created: 2013-01-28 | | | Updated: 2013-01-28 | | | Article URL http://www.symantec.com/docs/TECH202124 |
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
No volumes found for file server 10C1D3D52D0994E47A1A811D7F66A99E01z10000Evserver and volume 1
Cause
It's a bug
Solution
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Workaround:
Use TaskName or TaskEntryId instead
|
|
| Source | ETrack |
| Value | 3064854 |
| 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









Thank you.