| What is the maintenance article about? | It explains how to keep a HELIOS 3D installation operational, recoverable, and transferable. The article covers backups, restore procedures, software updates, and moving local or network installations. (Helios 3D | HELP CENTER) |
| Which parts of a HELIOS 3D environment are affected by maintenance? | Maintenance can affect the SQL database, project folders, library folders, program files, workstation setup, AutoCAD / Civil 3D profiles, and, depending on the installation type, license components. (Helios 3D | HELP CENTER) |
| Who should perform HELIOS 3D maintenance tasks? | These tasks are usually performed by administrators, IT staff, or experienced HELIOS 3D users. Before changing versions, restoring databases, or moving installations, all users should close HELIOS 3D and a verified backup should be available. (Helios 3D | HELP CENTER) |
| Is a SQL database backup alone a complete HELIOS 3D backup? | No. A database backup alone is not complete because HELIOS 3D planning data is stored partly in drawings and partly in the database. Project folders, library folders, and configured external storage locations must also be included. (Helios 3D | HELP CENTER) |
| What data should be included in a HELIOS 3D backup? | A backup should include the HELIOS 3D SQL database, project folder, library folder, installation folder if a full environment copy is required, and any external storage location configured in the HELIOS 3D system settings. (Helios 3D | HELP CENTER) |
| What should I document before an update or migration? | Document the current database name, SQL Server name, project base path, library base path, program base path, license setup, and the Windows or SQL user used for database access. (Helios 3D | HELP CENTER) |
| Why should I check the project and library paths before creating or restoring a backup? | Restored database entries may reference drawings, component libraries, or project data stored in those folders. If the folders are missing or the paths are wrong, HELIOS 3D may not find the related project or library data. (Helios 3D | HELP CENTER) |
| Which tool is needed to back up or restore the HELIOS 3D SQL database? | SQL Server Management Studio is needed for database backup and restore operations. The article recommends that this should ideally be handled by IT staff or users with the required SQL Server permissions. (Helios 3D | HELP CENTER) |
| Where is the target path for a SQL Server backup evaluated? | The backup target path is evaluated on the SQL Server machine, not necessarily on the local workstation. If the backup file cannot be created or found, check the SQL Server backup directory and the permissions of the SQL Server service account. (Helios 3D | HELP CENTER) |
| Can HELIOS 3D create a database backup directly from the application? | Starting with HELIOS 3D 2017, users with full access to the SQL Server can also back up the database directly from the application. The .bak file target path is located on the SQL Server, not on the client. (Helios 3D | HELP CENTER) |
| How can I create a complete copy of a HELIOS 3D environment before an update? | Copy the entire HELIOS 3D installation, including installation, project, and library folders if applicable. Then copy the database by creating a backup and restoring it under a new name, start the copied HELIOS 3D version, connect to the copied database, and update the base paths in the system settings. (Helios 3D | HELP CENTER) |
| When do I need to restore a HELIOS 3D backup? | A backup may need to be restored if an update causes issues and no timely resolution is available. If the database version changed after the update, the database backup must be restored using SQL Server Management Studio. (Helios 3D | HELP CENTER) |
| Where can I find the HELIOS 3D program and database version numbers? | The version numbers are listed in the readme.txt file in the HELIOS 3D installation directory, for example C:\Helios3D. At the top of the file, you can find the program version and database version. (Helios 3D | HELP CENTER) |
| What must I check before restoring program files or a database? | Compare the HELIOS 3D program version with the database version shown in readme.txt. The program version must be compatible with the database version. The program version must never be lower than the database version, otherwise login will not be possible. (Helios 3D | HELP CENTER) |
| Is it always necessary to restore the database when rolling back HELIOS 3D? | No. In many cases, restoring the program files is sufficient if only the installed program version needs to be rolled back and the database structure has not changed. If the database version has changed, the database backup must also be restored. (Helios 3D | HELP CENTER) |
| How do I restore the HELIOS 3D program files? | Rename the current Bin directory instead of deleting it, locate the appropriate backup in the Backups folder, copy it into the main installation directory, and rename Bin_Date_Time to Bin. If no database restore is required, HELIOS 3D can then be started normally with the restored program version. (Helios 3D | HELP CENTER) |
| What should I do before restoring the HELIOS 3D database? | Make sure that no HELIOS 3D user is connected to the database. Open sessions can block the restore process or lead to inconsistent results. (Helios 3D | HELP CENTER) |
| How do I restore the HELIOS 3D database in SQL Server Management Studio? | Log in to SQL Server with administrative rights, select the HELIOS 3D database, right-click it, and choose Tasks -> Restore -> Database. Then select Device, add the appropriate .bak file from the SQL Server backup directory, and confirm the restore operation. (Helios 3D | HELP CENTER) |
| How are HELIOS 3D database backup files named? | Backup files generated by HELIOS 3D follow the pattern DatabaseName_#Version#Date#_Time.bak. (Helios 3D | HELP CENTER) |
| What is the risk when restoring a database? | Restoring a database can overwrite existing project, component, and system data. If the database should be restored as a copy, verify the database name and the MDF and LDF file names before confirming the restore. (Helios 3D | HELP CENTER) |
| What should I check if I restore a database under a different name? | Verify that the MDF and LDF files are correctly renamed on the Files page. Otherwise, parts of the original database may be overwritten. (Helios 3D | HELP CENTER) |
| How does the HELIOS 3D update function work? | During program startup, HELIOS 3D checks whether a newer version is available. You can then install the update immediately or save it for later installation. (Helios 3D | HELP CENTER) |
| What should I do before installing a HELIOS 3D update? | Create a backup of the HELIOS 3D database and the configured project and library folders. After the update, review the information about new functions or changes. (Helios 3D | HELP CENTER) |
| What should I consider when updating a multi-workstation HELIOS 3D environment? | Make sure that all clients are updated or connected consistently according to the installation concept. Inconsistent client or program versions can cause access and compatibility problems. (Helios 3D | HELP CENTER) |
| When should I use the “Moving installations” section? | Use it when a HELIOS 3D installation must be copied to another workstation or moved to a server-based network installation. The goal is to reproduce the existing working environment with the same program version before any additional update is performed. (Helios 3D | HELP CENTER) |
| Should I combine a migration with a version upgrade? | No. The article explicitly advises not to combine a migration with a version upgrade unless it has been planned and tested. First create a working copy, verify login, database access, project paths, library paths, and licensing, and perform the update as a separate step. (Helios 3D | HELP CENTER) |
| What is required to move HELIOS 3D to a local workstation? | Microsoft SQL Server Express is required on the target system. The article recommends using the sa account for server login. The server collation must be identical on source and target systems, otherwise the database cannot be imported. (Helios 3D | HELP CENTER) |
| Which information should I collect before moving HELIOS 3D to another workstation? | Collect the current HELIOS 3D program version, SQL Server name, database catalog, project base path, library base path, program base path, license setup, and the Windows or SQL user used for database access. (Helios 3D | HELP CENTER) |
| How do I move HELIOS 3D to a local workstation? | Install SQL Server Express on the new computer, copy the database by backup and restore, copy the full HELIOS 3D installation directory including project and library folders, run .\Client Setup\setup.exe to install the Sentinel driver and create a shortcut, start HELIOS 3D, connect to the new database, and adjust program, project, and library paths in the system settings. (Helios 3D | HELP CENTER) |
| What should I test after moving HELIOS 3D to a new workstation? | Start HELIOS 3D on the new workstation, log in to the copied database, and verify that projects, libraries, and system settings point to the new locations before the old system is removed or decommissioned. (Helios 3D | HELP CENTER) |
| How do I move HELIOS 3D to a network installation? | Install SQL Server Express on the new server, copy the database by backup and restore, copy the HELIOS 3D installation directory including project and library folders to a server drive, ensure all users have write access, run Client Setup, start HELIOS 3D from the first workstation, connect to the new database, and adjust the shared base paths. (Helios 3D | HELP CENTER) |
| What permissions are needed for a network installation? | All users need write access to the HELIOS 3D directory and must be able to access the configured program, project, and library paths. These paths must be valid for every workstation, for example by using consistent drive letters. (Helios 3D | HELP CENTER) |
| Why must the same paths be valid for every workstation in a network installation? | HELIOS 3D uses the configured program, project, and library base paths for all workstations. If paths or drive letters differ between clients, users may not be able to access the required drawings, libraries, or program files. (Helios 3D | HELP CENTER) |
What does Client Setup do after moving HELIOS 3D? | Client Setup registers the workstation, updates the desktop shortcut, and installs the Sentinel driver if required for license detection. It is run from the Client Setup folder of the HELIOS 3D installation. (Helios 3D | HELP CENTER) |
| What must be changed if Autodesk Civil 3D loads HELIOS 3D from a network path? | By default, launching Autodesk Civil 3D from the network is disabled. The Acad.exe.Config file may need to be adjusted by adding <loadFromRemoteSources enabled="true"/> in the first <runtime> section. (Helios 3D | HELP CENTER) |
| What should I do if HELIOS 3D DLLs are still loaded from the old directory after moving? | Delete or recreate the Autodesk Civil 3D profile used by HELIOS 3D, usually named Helios3D. HELIOS 3D should recreate the profile on the next Civil 3D start, but personal Civil 3D profile settings will be lost. (Helios 3D | HELP CENTER) |
| What should I check if HELIOS 3D does not start correctly after an update, restore, or migration? | Check whether the HELIOS 3D program version is compatible with the database version, verify SQL Server access and the selected database catalog, confirm that no workstation is connected during restore, check project and library paths, verify permissions for network clients, recreate the Civil 3D profile if DLLs load from an old path, and rerun Client Setup if licensing is not detected. (Helios 3D | HELP CENTER) |
| What should I check if the license is not detected after moving the installation? | Run Client Setup again and check the Sentinel driver or license server configuration. (Helios 3D | HELP CENTER) |
