Error Statement Data File Name is Invalid when Exporting out Fund Statement in Azure Cloud
- 31 May 2023
- Contributors
- Print
- DarkLight
- PDF
Error Statement Data File Name is Invalid when Exporting out Fund Statement in Azure Cloud
- Updated on 31 May 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
When exporting out a fund statement the error, "Statement Data File Name is Invalid". This error occurs for clients on Azure Cloud who are still using the local N drive for their export files rather than the shared S drive on Azure Cloud. The local mapped N drive is a remnant from when FIMS was self-hosted on the client's own server. When client's move to Azure Cloud typically the S drive is used going forward.
This can also occur if a network drive is being used that can no longer be used in Azure Cloud. In Azure Cloud, you can only use the local C drive or the S drive.
How to Save Files and Documents in MyFiles
Steps To Duplicate:
1. Go to Reports\General Ledger\Fund Statements Export
2. Click Run Report to export out the desired statement
3. See error occur.
2. Click Run Report to export out the desired statement
3. See error occur.
Answer:
If you are hosted on Azure Cloud now but were previously self-hosted and still use your local N mapped drive for your exports, the issue is caused by Azure Cloud not being able to see the mapped N drive. You will need to change your export to use either the Azure Cloud S drive or a locally attached drive. We recommend using the S drive.
Please see the following article on setting up export paths in Azure Cloud:
Please see the following article on setting up export paths in Azure Cloud:
How can I tell if my Exports are set to Use my Local C drive?
Was this article helpful?
