This topic provides information on troubleshooting issues that you may encounter running the Aptify 5.5.3 or Aptify Web 5.5.3 setup.

...

• 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 DLLs
• Database Setup May Fail Due to Memory UtilizationFails Due to Enabled Row Set Security

If you experience an error not described below, please contact Aptify Technical Support for assistance.

Anchor
_OrderFail _OrderFail

Installation Fails During Update of Orders Entity

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.

1. Open the record for the Orders entity in the Entities service.

2. 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
   
   

   No Format
   ShipToEmail -Set virtual Field Type = Calculated Set below Calculation: Case p2.LastName when '[Not Specified]' then c1.MainEmail else p2.Email1 End

3. 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
   
   

   No Format
   BillToEmail -Set virtual Field Type = Calculated Set below Calculation: Case p3.LastName when '[Not Specified]' then c.MainEmail else p3.Email1 End

4. Set the definition for the BillToName virtual field:
   
   

   No Format
   Update below Calculation

   expression
   

   : (RTRIM(p2.FirstName) + ' ' + LTRIM(p2.LastName))

   
    

5. Save and close the Orders entity record.
   
   

...

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).

...

1. Identify which required field does not have a default value based on the error information provided by the setup program.
2. Restore the database back to its original state prior to the installation attempt which failed.
3. Open the appropriate entity and specify a default value for the field you identified in step 1.
4. Save and close the entity.
5. Rerun the Aptify 5.5.3 setup program.

...

1. .

...

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:

1. Turn off the Grant SQL Text Generation for vwCompanies the entity's base view (backend update) .
2. Update the entity (in this casefor example, add the Logo new field manually).
3. 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.
4. Turn on Grant SQL Text Generation (backend update).
5. Re-run the setup, if possible, on a restored backup from prior to installation.

...

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. 

Anchor
_

...

rowSet _

...

rowSet

Database Setup

...

Fails Due to

...

...

...

Enabled Row Set Security

When upgrading to Aptify 5.5.3

...

,

...

http://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sqlserver-20052008/

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 folder
of the Aptify 5.5.3 setup):

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:
 

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):

1. Select 5.5.2 and complete the setup. Take a backup.
2. Clear Aptify Web Components and 5.5.3, leaving only CES checked and complete the setup. Take a backup.
3. Run the setup again. Check Aptify Web Server Components (i.e., clear Aptify 5.5.3) and complete the setup. Take a backup.
4. Run the 5.5.3 setup.

If you continue to experience problems, please contact Aptify Technical Support for assistance.

 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 install. You can reinstate the Row Set Security settings once the install is successful. Follow these steps for the Persons and Companies entities:

1. Open the record for the entity in the Entities service.
2. Click the Row Set Security tab and determine whether a rule is set for this entity.
3. Record the rule information for use later in re-enabling this functionality.
4. If a rule is set, right-click on the rule and select Delete from the drop-down menu. 
5. Repeat step 4 for any additional rules in the record.
6. Click Save and Close.

Once you have completed the upgrade to Aptify 5.5.3, you can re-enable the rules for Row Set Security in the Persons and/or Companies entities using the following steps.

1. Open the record for the entity in the Entities service.
2. Click the Row Set Security tab.
3. Open a new Row Set Security sub‐type record.
   • Either click the New Record... button in the menu bar, or right‐click in the gray area and select New from pop‐up menu to open a new record.
     
     
4. Enter the rule you recording back in step 4 in the Base View Where Clause field.
5. Enter a description for the rule.
6. Click OK to save the rule.
7. Enter additional rules for the same entity, if necessary. Aptify uses an AND operator to separate multiple Base View Where Clauses within a generated base view.
   • Alternatively, you can click OK and New in Step 8 to save the current and open a new Row Set Security record in one step.
     
     

8. Save and close the Entities record.

9.  Regenerate the base view for any related entities that join to the entity for which you just enabled row set security.