...
Iguana runs out of memory while building the configuration.xml
Bugs that empty configuration.xml
Solutions
Check the last update on the emptied IguanaConfiguration.xml
Restore a backed up IguanaMainRepo prior to the IguanaConfiguration.xml being emptied
Reinstall Iguana following these steps:
https://help.interfaceware.com/v6/backup-and-restore
If they do not have a back up
Iguana 6
Analyze their IguanaMainRepo from sourcetree:
/wiki/spaces/CSHC/pages/1032618281Find the commit that emptied the IguanaConfiguration.xml
Revert the commit until that point
Reinstall Iguana following these steps:
https://help.interfaceware.com/v6/backup-and-restore
Iguana 5
Obtain the customers IguanaConfiguration.xml and vcs_repo.sqlite
This will not work if the scripts are missing from vcs_repo.sqlite
IguanaConfiguration.xml must have some data in it
Modify the IguanaConfiguration.xml to be in a valid format, you will need to add and delete lines
You can compare it to the default Iguana 5 configruation.xml to get the correct format
Start Iguana with the modified configuration.xml and vcs_repo.sqlite file in the working directory
You should be able to get some configurations (not all)
Case Study
36283- User setting caused Configuration XML to empty
36279 - Webserver setting caused Configuration XML to empty
35067 - Webserver setting caused Configuration XML to empty https://interfaceware.atlassian.net/browse/IE-2531
36389 - Replacing special character caused configuration file corruption https://interfaceware.atlassian.net/jira/software/projects/CFRI/boards/12?selectedIssue=CFRI-44
36448 - Unclear root cause; Iguana identified an unknown/non-existing channel as a source channel in the From Que component of another channel. Observed multiple empty channel configuration commits in the MainRepo.
36362 - Sync manager imported a QUE channel but failed to import the source channel for that component
36479 - Iguana 5