Hi Sebastian,
when this happens this means, that IntegrationServer/instances/default/config directory got corrupted during outage causing the IS to create a fresh set of config files.
Unfortunately these files are backed up to config/backup directory after IS startup completes overwriting the previously backed up files from earlier startups which might have contained your adjusted values.
When startup of IS fails due to corrupted config files you can just copy the affected files back from config/backup to config directory and restart IS.
Only thing which might help here is to restore the files from a backup archive done by your operations team (if configured).
Regards,
Holger
#Integration-Server-and-ESB#webMethods