The key text in the error message is "IndexWriter is closed". This usually indicates you have run out of disk space on the drive/partition that is used to store the temporary execution data generated when running data flows.
You can configure the application to automatically purge temporary execution data for ad hoc runs, see the Help documentation
https://d3sa-preview.infogixsaas.com/docs/dist/help/Default.htm#j-admin/managing-run-data.htmThe purging of temporary data for scheduled runs was also covered in this post:
https://community.precisely.com/communities/community-home/digestviewer/viewthread?GroupId=319&MID=33541&CommunityKey=9c9ad6f1-42e5-4b69-98e5-b7e7fcf2738fYou may have to manually free up space on the disk/partition. You can determine where the temporary execution data is being stored by navigating to the <Analyze_Installation_Directory>/conf directory e.g. by default for a Desktop instance = C:\Program Files\Data360Analyze\conf
Open the site.prop file in notepad. Identify the value for the 'ls.brain.tempDir' attribute for example if the application was installed for Alll Users this may be "C:\Users\<username<\AppData\Local\Data360Analyze\site\data\executions\admin".
The temporary data for the user is in a subdirectory e.g. 'admin' and the temporary data flow for each data flow is then in a subdirectory of the user's directory.
Note: do NOT delete the 'cache' sub-directory of the 'executions' directory.
------------------------------
Adrian Williams
Precisely Software Inc.
Naperville IL
------------------------------
Original Message:
Sent: 06-01-2022 02:05
From: Jaycee Ikani
Subject: Error Code: util.factory.factoryMethodInvocationError
Hii Team,
Has anyone come across this error message and how to fix it.
Regards,
Jaycee Ikani
------------------------------
Jaycee Ikani
Knowledge Community Shared Account
------------------------------