Skip to main content
  • EN

Hello,

I just performed an upgrade from FME FLOW 2023.1 to version 2024.2 and now I have a big problem because I can’t restore the backup I made before upgrading.

The restore process fails with 

The system restore failed for the following reason:
The export location provided is invalid.

The error message in the History list says

COM.safe.fmeserver.configuration.migration.FMEConfigurationException: java.lang.NullPointerException: inputStream

in a red box just above the heading “Failure”.

The log just states 

Unable to extract import package.

 

The backup.fsconfig is a quite large file (15 GB) because I forgot to remove some raster files from the resources before creating the backup. I copied it manually to the resources/Backup folder so I can select it from there for restoring instead of uploading. Nonetheless it won’t restore.

I can unzip the file and see its content, so the archive itself is seemingly OK. 

What I did try:

Unzipped the file to a directory, removed the raster files from the created subfolder and zip the whole thing again, renaming the new zip file to backup.fsconfig. Copied that to the resources/Backup folder and tried to restore, but no success.

Our FME FLOW install is a pretty plain Express installation, I think I checked all access rights in case it’s a permission problem. Normally the services run under a dedicated service user account so there could potentially be an issue with that. Therefore I changed the services back to run as local system account and tested again but still no luck.

Now I have no further clue what to try next.

Does anyone have an idea what else I could try?

Any help would be appreciated because we have a lot of things configured and would have to build everything new from zero if I don’t manage to get the backup to restore successfully.

Kind regards,
Andreas

I think you want to contact Safe directly for this. You probably need to submit a case or contact your reseller.

That is what I thought, too, after reading again what I wrote yesterday. But thankfully it’s no longer necessary to go this way. I finally managed to resolve this problem. 😀

Here’s the story:

Luckily I made a manual backup of the shared resources folders and the ProgramData folder where the FME database files are stored before uninstalling version 2023.1. So I uninstalled version 2024.2 and installed 2023.1 again after that. After completing the installation of the older version I stopped all FME services and copied all the database files from the manual backup to the ProgramData folder and overwrote the shared resources folder with the ones from my manual backup.

After restarting the FME services all my repositories, workspaces, automations etc. where there again and everything seemed to be working fine.

Then I did remove all the raster files (that made my original backup fsconfig such a big file) from the repository and did a backup once again. This resulted in a much smaller fsconfig file. After that I tested the restore process with the same version and it was successfully restored without errors.

Now knowing that the backup.fsconfig is valid and can be restored successfully I uninstalled version 2023.1 and installed 2024.2 again. When I restored the backup this time all went well an I now have a current version of FME FLOW 2024.2 with all data from the previous version. 😀

After all it seems that my first (big) backup file was indeed corrupted despite of being able to unzip its contents.

 

So this topic can be marked as solved by now.

Reply


Community Stats

30,351
Posts
115,336
Replies
38,078
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.