Note | ||
---|---|---|
| ||
Under certain circumstances, the setup may fail due to a memory utilization restriction. You will know this occurs if you find the following line in the InstallationStatusLog.txt file (found in the top-level directory of the setup): Exception Message: Exception of type 'System.OutOfMemoryException' was thrown. If this occurs, see Setup May Fail Due to Memory Utilization for an alternate installation method. If you continue to experience problems, contact Aptify Technical Support for assistance. |
This topic provides information on troubleshooting issues that you may encounter running the Aptify 5.5.3 or Aptify Web 5.5.3 setup.
Note |
---|
In some cases (as noted) it is recommended to re-run the setup on a restored backup taken from prior to installation. |
...
- Installation Fails During Update of Orders Entity
- Circular References with Form Templates or Dashboard
- Scenarios Where Setup May Fail Due to Entity Updates and Required Fields
- Grant SQL Cannot Generate a Field that Does Not Exist in the Base View and Field Level Security
- Aptify Web Site May Fail to Load Certain DLLsSetup May Fail Due to Memory Utilization
If you experience an error not described below, please contact Aptify Technical Support for assistance.
Anchor | ||||
---|---|---|---|---|
|
The If your organization has modified the Orders entity, it is possible that the Aptify 5.5.3 installation may fail when the setup program is updating the Orders entity , and the virtual while attempting to update virtual field definitions for several fields are missing in the Orders entitythe ShipToEmail and BillToEmail fields to support company only orders. Perform the following steps if the installation fails as described in this scenario.
...
The Aptify 5.5.3 database setup may fail if a form template or dashboard circular reference error is found. In Aptify 5.5, Aptify added the Unique Identifier for form templates to prevent circular reference errors, so you should not see this error on systems that originated from 5.5.2. However, you may see this issue if you database was at one point an earlier version (5.0 SP3 and earlier).
...
- Identify which required field does not have a default value based on the error information provided by the setup program.
- Restore the database back to its original state prior to the installation attempt which failed.
- Open the appropriate entity and specify a default value for the field you identified in step 1.
- Save and close the entity.
- Rerun the Aptify 5.5.3 setup program.
Sample Spaces Record May Fail to Create If Linked Entity Field is required with No Default
...
- .
Anchor | ||||
---|---|---|---|---|
|
If an entity has a field that is not part of the base view, the installation may fail. For example, Aptify 5.5.3 adds 2 added a new field to Companies called Logo. This can be a problem for certain databases whose Companies entity meets these conditions:
- There are fields in the Companies entity definition that do not exist in the base view’s SELECT statement.
- The SQL Text for the Companies entity’s base view is non-generated.
- The Grant SQL Text for the Companies entity’s base view is generated.
- The Companies entity has Field Level Security enabled.
If an organization has an organization’s Companies that entity meets all of the conditions listed above , and the 5.5.3 update to the Companies entity setup program is adding or new field to that entity, then the 5.5.3 setup program will fail. The workaround is as follows for the example above:
- Turn off the Grant SQL Text Generation for vwCompanies the entity's base view (backend update) .
- Update the entity (in this casefor example, add the Logo new field manually).
- Manually add Logo the new field to vwCompanies the entity's SQL Text and to the all the Grant statements from the appropriate Database Objects records.
- Turn on Grant SQL Text Generation (backend update).
- Re-run the setup, if possible, on a restored backup from prior to installation.
...
Anchor | ||||
---|---|---|---|---|
|
Note | ||
---|---|---|
| ||
When installing a large service pack like Aptify 5.5.3 (and on busy systems in general), Aptify recommends restricting the amount of memory that SQL Server can utilize based on the system’s overall available memory. This will ensure the setup program itself has access to the appropriate memory it needs to successfully install. You can find several examples online, including posts like the following, for guidance: |
...
When launching the Aptify web site, certain 32-bit DLLs in the AptifyServicesAPI Bin folder may prevent the site from loading – most notably is ConfigManifestForm.dll, which may exist on systems that have been through a major version upgrade. The workaround is to remove these DLLs and any dependencies from the AptifyServiceAPI folders and then load the site again. Contact Aptify Technical Support if you have questions or concerns about removing objects from the AptifyServiceAPI folder.
...
folder
...
Exception Message: Exception of type 'System.OutOfMemoryException' was thrown.
If this occurs, Aptify recommends installing each component separately, depending on what is already installed in your environment. Below is the recommend approach for this installation method:
...
title | Note |
---|
...
.
...
Run each install (Aptify 5.5.2, CES, Aptify Web Server Components, Aptify 5.5.3) one at a time (starting with the first item). By default the installer checks the boxes of the elements not installed yet.
For example, for a 5.5.2 to 5.5.3 install (with no CES or Aptify Web components already installed):
- Select 5.5.2 and complete the setup. Take a backup.
- Clear Aptify Web Components and 5.5.3, leaving only CES checked and complete the setup. Take a backup.
- Run the setup again. Check Aptify Web Server Components (i.e., clear Aptify 5.5.3) and complete the setup. Take a backup.
- Run the 5.5.3 setup.
...