You have accepted all cookies. You can change your cookie settings at any time.
This is a new service – your
feedback will help us to improve it.
Created 06 October 2020 12:07
I've been having issues with versions of of the FIS after 1.2.24 (2019/20) not exporting Access MDBs:
When you tick 'Export to Access and CSV' in Settings, then import a file, the reports are produced correctly, but as soon as it tries to export the MDB file you get the following error.
I did follow this up with the help desk (including multiple copies of log files) and it is showing as fixed in the known issues. However I have confirmed this with another College.
Does anyone else have this issue?
20/21 works fine.
No one has replied to this post.
Are there any files and mdb in the Sandbox, could it be a problem with your connection string, and have you checked the test button on FIS setup?
06 October 2020 12:25
I think you are thinking of export to SQL, rather than export to Access. Fresh copy each time and delete all previous files.
I'm really after someone to test on their version of the FIS. That would actually be very helpful.
06 October 2020 13:24 (Edited)
Hi Peter, have just run an ILR through 1.2.30 and got the same error message.
I can see an error message in the Event Viewer for this. I'll forward it to the Service Desk.
06 October 2020 19:17
Thank you Dan, that is most helpful.
My original helpdesk ticket is CRM:0033031. I'm afraid I got asked so many questions (we must have exchanged over 30 emails), I eventually reluctantly had to give up due to lack of time.
Hoping you have more luck than I did.
07 October 2020 08:04
As I normally export to SQL I turned this off to test only using the export to mdb but all work ok excepting that when I opened the mdb in my output directory it automatically had to repair the file
In the FIS Sandbox, Export directory you should find the file ESFA.DC.ILR.DataStore.Database.mdb which should have been copied to your output directory.
I also checked the log file but this showed only that the process had created the mdb in the above directory and then copied it my output directory.
I could not replicate the error you have.
07 October 2020 08:44
Don't worry Martin. Dan has replicated it. Did you check which version you were on? Remember it works fine for 20/21 and earlier versions of 19/20.
Task Execution Unhandled Failure - Step 8
System.Exception: Export Access process failed with error
07 October 2020 09:13 (Edited)
1.2.30 with R14
I expect it is a bug for them to resolve
07 October 2020 09:27
That's exactly the same as I get when running the 20/21 FIS (or 2019/20 1.2.24):
40:33.1 INFO Finished Export40:33.2 DEBUG Persisted to Mdb in: 2106640:33.2 DEBUG Completed Mdb callback
Dan has replicated so there is no need to repeat.
07 October 2020 09:48 (Edited)
The FIS team have had a look at this but are not able to recreate the issue. I'm afraid they can't investigate further without a detailed log file. If anyone having this issue can send the log file to the Service Desk, that would be much appreciated.
07 October 2020 13:47
Please can you ask the FIS team to look under call number CRM:0033031? I sent everything they requested including the logs.
07 October 2020 14:48
Thanks Peter, I've asked them to look at the info on that call number.
07 October 2020 16:11
I'm still on 1.2.21 which exports fine but the Rulebase_DV tables are blank. Have they moved the Derived Values?
17 November 2020 16:45
I do not think the DV have been populated since 2018.
17 November 2020 17:11
It was populated in 18/19, it seems they stopped it for the 19/20 academic year.
18 November 2020 08:30