ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity Upgrade error "Error validating NSQL"

book

Article ID: 186675

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The install.log is showing the following error post upgrade:

The log may show multiple query names:

3/08/20 3:11 PM (Java) Error validating NSQL
3/08/20 3:11 PM (Java) 
3/08/20 3:11 PM (Java) Query name=Issues Listing : Query ID=<Query.ID> : Content Source=csk.niku.com : cmn_nsql_queries.id=5001000
3/08/20 3:11 PM (Java) You must correct invalid NSQL queries.  In PPM Studio, go to the NSQL tab for each failing NSQL query. Click the 'Preview' button to view the error details. See the Change Impact Guide for further information.

Cause

This can be due to custom queries that require corrections post upgrade.

Environment

Release : All Supported Releases

Component : CA PPM INTEGRATIONS & INSTALLATIONS

Resolution

  1. Correct any invalid custom NSQL queries.
    • Notes:
      • See section: (On-Premise and SaaS) Post-Upgrade: Verify NSQL Queries at: (On-Premise and SaaS) Complete the Post-Upgrade Steps where the below steps and more details are referenced
      • If a query is associated with a portlet, clear the Available for User Portlets check box on the query properties page to edit the query.
      • Note: You cannot edit system queries that are provided by Clarity PPM
 Follow these steps: 
  • Click Administration, Studio, Queries.
  • Open each failing query and click the NSQL tab.
  • Clear the Available for User Portlets check box.
  • Click Save and Continue.
  • Review the errors and repair the broken query constructs or fields.
  • Click the Preview button.
  • Confirm that the NSQL query is valid.
  • Click the General tab.
  • Select the Available for User Portlets checkbox.
  • Click Save and Return.
 If the query is in use by active portlets and cannot be edited in Studio, use the XML Open Gateway (XOG):
  • Export the failing query.
  • Correct the broken query constructs or fields.
  • Use XOG to import the corrected query. Perform the steps above this tip to preview and verify the query.
2. Check for additional errors in the install.log that may be the root cause of the failure that require fixing prior to retrying the upgrade.

Additional Information

Note: The warnings are not blocking the upgrade and will not fail an upgrade