Have you confirmed the batch file had run from sss? Where is the batch file?
Or, why do you use batch file instead of running fmsadmin in vbs?
For my curiosity, why don't you use Local System?
Problem faced so far
1. When running the VB script to generate a CSV file to any other directory (e.g. d:\temp\users.csv) the VB script generates the file successfully. However, when running from Schedule no file is generated under FM Server Documents Path.
Your overall approach is correct but this particular part is confusing. FMS can only import from its own documents folder and from the a temp folder created by a FM script. So that rules out the temp folder since your VBscript runs before the FM import script.
in your above explanation: why would you expect something to show up in the FMS docs folder if you make your VBscript output to a temp folder?
Make your VBscript output to the FMS docs folder directly and everything should be fine. If you are worried about leaving the CSV there then use an FMS script sequence schedule that:
- runs your VBscript
- runs the FM import script
- runs another VBscript or simple batch file to delete the CSV