Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-11132: Reloading on user pull down fails in 18.7 with Error: Unknown column: pvaccount-OwnerID

Privileged Access Service ,  

3 October,18 at 05:34 PM

Problem:
  
After upgrading the Centrify Identity Service (CIS), the following error appears when reloading the User profile:
  
Query has failed: System.NotImplementedException: Unknown column:pvaccount-OwnerID

User-added image

Cause:
  
This error is due to an incomplete update of the CIS database.

Workaround:
  
Rerun the Centrify Identity Service installer and select the Repair option.  It is helpful to generate a logfile for the repair in case it is required to troubleshoot any further issues.  Instructions to rerun the update are detailed in the Centrify-Infrastructure-Service-HA-installation-guide.pdf that is included in the zip file of the CIS download.

The overview of the instructions are:
1) Using Microsoft Failover Cluster Manager, move the cluster role to a secondary node.

2) On the primary node, using the local Administrator account in a Powershell script, run the installer with the arguments /l <logfile> as seen in the example image below.
 
i.e. PS> Centrify-Infrastructure-Service-18.7.exe /l c:\Temp\cis.log

User-added image

3) Select to Repair
 
User-added image
 
4) Follow the instructions and answer the prompts as detailed in Centrify-Infrastructure-Service-HA-installation-guide.pdf

5) Once finished, move the cluster roll back to the primary node and run the same process on the secondary node.
 
Resolution: 
  
This issue will be addressed in a future release of customer managed Centrify Identity Services.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-3925: How to add Centrify parameter to a group policy articleKB-7441: List of error codes Adclient and DAD daemons generated for Solaris and Linux clients articleKB-5163: "GSSHeader did not find the right tag" error when connecting via Kerberos SSO using Cloudera