Tech Notes

Tech Note: 136

Migration of Galaxy to System Platform 2023 Never Completes

When migrating a Galaxy from an older version to System Platform 2023, the process hangs without any errors or warning and never completes.

By default, the migration process handles 500 templates at the same time from the original Galaxy. If there are more than 500 templates, this may exceed the 3.5 GB that aaGR process can handle, causing a crash as we see in the Log Viewer.

This tech note provides the steps to change the default MaxTemplateCacheSize from 500 templates to 10 to make sure the 3.5 GB limit is not violated.


Tech Note: 135

Slow Performance in IDE when Opening or Checking In Objects

It is possible that you may experience slow performance in the System Platform IDE when opening or checking in objects.  There could be various reasons why the performance within the IDE could be slow, including compatibility issues with newer version of Microsoft SQL Server.

This tech note provides steps to address the issue from the database setting perspective.


Tech Note: 120

Backing up and Restoring a Galaxy

System Platform Galaxies should be backed up so that if the Galaxy becomes corrupted, you can restore it to a working state.  The Galaxy backup file can be used to overwrite an existing, corrupted Galaxy or to re-create it as a new Galaxy.

This tech note will provide instructions on how to create a Galaxy backup file and provide the steps for restoring an existing Galaxy as well as using a Galaxy backup to create a new Galaxy.


Tech Note: 121

Correcting Deployment State Mismatches

Certain conditions (hardware failure of a deployed node, restoring a Galaxy from a backup, etc.) can cause the deployment state of an object in the IDE to be different from the object’s actual state.

This tech note will provide steps to correct this mismatch.


Tech Note: 116

Adding Auto Reconnect Functionality to Device Integration Objects

When a Device Integration object gets disconnected from its data source (e.g. an AVEVA OI Server), it must be manually triggered to reconnect when the source becomes available again.  This tech note will instruct you on how to set up an auto reconnect feature and add additional diagnostic information that will indicate the number of disconnects the object has experienced since it last went on scan.