This topic provides information on troubleshooting issues that you may encounter running the Aptify 6.2 or Aptify Web 6.2 setup.
In some cases (as noted) it is recommended to re-run the setup on a restored backup taken from prior to installation.
Troubleshooting issues with installing Aptify 6.2 are addressed in the following sub-topics:
If you experience an error not described below, please contact Aptify Technical Support for assistance.
If your organization has modified the Orders entity, it is possible that the Aptify 6.2 installation may fail when the setup program is updating the Orders entity while attempting to update virtual field definitions for the ShipToEmail and BillToEmail fields to support company only orders. Perform the following steps if the installation fails as described in this scenario.
Set the definition for the ShipToEmail virtual field:
ShipToEmail -Set virtual Field Type = Calculated Set below Calculation: Case p2.LastName when '[Not Specified]' then c1.MainEmail else p2.Email1 End
Set the definition for the ShipToEmail virtual field:
BillToEmail -Set virtual Field Type = Calculated Set below Calculation: Case p3.LastName when '[Not Specified]' then c.MainEmail else p3.Email1 End
Set the definition for the BillToName virtual field:
Update below Calculation: (RTRIM(p2.FirstName) + ' ' + LTRIM(p2.LastName))
Save and close the Orders entity record.
The Aptify 6.2 database setup may fail if a form template or dashboard circular reference error is found. In Aptify 6.2, 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 6.2. However, you may see this issue if your database was at one point an earlier version.
The setup process catches these during installation (the setup will provide information about the affected form templates and dashboards in the Installation log). These references will need to be corrected before installation can continue.
Below is an example of a form template circular reference that was found during multiple client database installation tests. There are two sub-templates (IDs 8167 and 8173) that hold a circular reference back to itself via its children. The part lists are the same as the part list for another sub-template (ID: 8170 for 8167 and 8174 for 8173). In short, the part lists for form templates 8167 and 8173 are incorrect. The part lists should be deleted and replaced with the following:
You can then re-run the setup, you do not need to restore the database to prior to previous installation attempt.
If an entity has a required field that does not have a default value, the installation may fail. If this occurs, follow these steps to resolve the problem:
If an entity has a field that is not part of the base view, the installation may fail. For example, Aptify 6.2 added a new field to Companies called Logo. This can be a problem for certain databases whose entity meets these conditions:
If an organization has an entity that meets all of the conditions listed above and the 6.2 setup program is adding or new field to that entity, then the 6.2 setup program will fail. The work around for the above example is:
When launching the Aptify website, 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 any questions or concerns about removing objects from the AptifyServiceAPI folder.
When upgrading to Aptify 6.2, the database setup fails if Row Set Security is set in the Persons and Companies entities in your environment. To ensure a successful upgrade, you should remove Row Set Security from the Persons and Companies entities before beginning the installation procedure. You can reinstate the Row Set Security settings once the install is successful. Follow these steps for the Persons and Companies entities:
If a rule is set, right-click on the rule and select Delete from the drop-down menu.
Repeat step 4 for any additional rules in the record.
Click Save and Close.
Once you have completed the upgrade to Aptify 6.2, you can re-enable the rules for Row Set Security in the Persons and/or Companies entities using the following steps:
Save and close the Entities record.
Regenerate the base view for any related entities that join to the entity for which you just enabled row set security.
After upgrading to Aptify 6.2, there might be a scenario where the 'Create Order' option from a person or company summary form may not work. Follow the below steps for the respective entity to make sure it works:
Set Record ID: -1
Set New Record Parameter: PARAMS(CompanyParty='Individual'| ShipToID=<%ID%>)
If you have records contain bad data, the setup may fail when the Database Objects validation options is selected in the setup. For example, if you have orders for a subscription with invalid Subscriber ID where that person (Subscriber ID) does not exist in the database hence failing the validation process. You will need to fix the invalid data before continuing with the install. The dialog that is displayed during the setup process when this error is encountered includes suggested SQL to resolve or further investigate the issue. See the appropriate step in the Installing Aptify 6.2 Server Software for more details.
When installing Aptify 6.2, you may receive an error about not being able to load a file or assembly:
|"Could not load file or assembly 'file:///C:\Somelocation\Data\Aptify620\files\releaseAssemblies\SomeObject.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)"|
If Windows's security blocking the files needed for the installation, you will receive the above-mentioned error.
Please perform the following steps to resolve this issue: