Skip to main content
Skip table of contents

Migrating to SQLite mode (SpinFire Publish 2025.1.0+)

Starting with SpinFire Publish 2025.1.0, customers MUST now use an embedded SQLite database instead of ArangoDB, as ArangoDB is no longer supported.

This is called SQLite mode.

SQLite mode makes it easier to install or update SpinFire Publish as there is no need to deploy ArangoDB.

Migrating an existing installation

Migrating an existing installation

An existing installation of SpinFire Publish (CAD Publisher) based on ArangoDB must be migrated before it can use SQLite mode. This is a one-time operation done by running a migration program called CadPublisherArangoMigrator.exe.

The program connects to ArangoDB using the same network settings as Centro Web App.

It turns off the applications, deploys the ArangoDB database, migrates its content to an SQLite database and sets a system environment variable CAD_PUBLISHER_SQLITE=true to toggle SQLite mode on.

Follow the steps below to perform the migration:

  1. Create a backup of the ArangoDB database.

  2. Download and extract the ZIP file CadPublisherArangoMigrator.zip

  3. Download C7-deploy-2025.1.x.x.zip and place it next to CadPublisherArangoMigrator.exe.
    You don’t need to extract the zip file, the migration program will do it automatically.

    image-20241129-170727.png

  4. If you have installed Centro Web App in a different folder than the default C:\inetpub\wwwroot\Centro, open CadPublisherArangoMigrator.exe.config and update CentroConfigPath setting with the correct value.

  5. Open an administrator Command Prompt in the folder that contains CadPublisherArangoMigrator.exe.

    image-20241129-171006.png

  6. Run CadPublisherArangoMigrator.exe from the command prompt.

    image-20241129-182250.png

  7. Enter the password for ArangoDB root user and press Enter.

    image-20241129-171424.png

  8. Wait for the migration to complete. If successful, you will see Migration Successful!.
    If an error occurs, refer to the troubleshooting section below.

    image-20241129-185230.png

  9. (Optional) Turn off or uninstall the ArangoDB service.

  10. Restart the machine. This is required to make sure that the environment variable will take effect everywhere (e.g. in IIS).

  11. Install SpinFirePublish.exe

    1. Run the installer. If prompted for ArangoDB credentials, the environment variable from step 10 has not been propagated. Ensure the variable is set then reboot the machine.

    2. Navigate to your SpinFire Publish instance to make sure it is running correctly

    3. Note: you may need to re-set the Log On As credentials for the Centro Pipeline Service (now replacing Pipeline Host and Pipeline Manager).

New installation

New installation

  1. Set CAD_PUBLISHER_SQLITE=true as system environment variable

  2. Restart the machine. This is required to make sure that the environment variable will take effect everywhere (e.g. in IIS).

  3. Install SpinFirePublish.exe

    1. Run the installer. If prompted for ArangoDB credentials, the environment variable from step 1 has not been propagated. Ensure the variable is set then reboot the machine.

    2. After the installation navigate to your SpinFire Publish instance to make sure it is running correctly.

Troubleshooting

Troubleshooting

Failed to deploy database

image-20241115-150934.png
  • Check the log files for more information: CentroWebApp00.log and deploy_log_<appVersion>_<dd-MM-yyyy-HHmmss>.txt

  • Make sure that the IIS application pool (usually CentroPool) has write access to the folder that contains the database file: <ProgramDataRoot>. The default is C:\ProgramData\SpinFire\SpinFire Publish\.

Attempt to write a readonly database

image-20241204-120800.png
  • Make sure that the IIS application pool (usually CentroPool) has write access to the folder that contains the database file: <ProgramDataRoot>. The default is C:\ProgramData\SpinFire\SpinFire Publish\.

HTTP Error 500.0 - Internal Server Error

image-20241204-111405.png
  • Ensure that the the IIS application pool CentroPool is started.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.