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-0925: adquery results in an Unsuccesful IPC execute: system error

Auditing and Monitoring Service ,   Authentication Service ,   Mac & PC Management Service ,  

12 April,16 at 11:02 AM

Applies to: Centrify DirectControl 4.1 on all platforms

Problem:

adquery results in the following error: Unsuccesful IPC execute: system error
bash-3.00# adquery user -a administrator
Unexpected error from adquery: Unsuccesful IPC execute: system error

and its corresponding debug messages in centrifydc.log

adclient[17656]: DEBUG <fd:23 get object> daemon.execute Get object: sid = 0105000000000005150000001a280732714a805d7e145c2f01020000 
adclient[17656]: DEBUG <fd:23 get object> base.adagent Find SID: S-1-5-21-839329818-1568688753-794563710-513 (7) 
adclient[17656]: DEBUG <fd:23 get object> util.except NotFoundException unknown domain SID (reference base/adagent.cpp:877 rc: 1) 
adclient[17656]: WARN <fd:23 get object> daemon.execute Uncaught exception 'unknown domain SID' -- returning 'unsuccessful' to client 
Cause:

We found couple of causes for this behavior:
1) The domain map may not be complete if there was a problem reaching the Global Catalog during startup.
2) This can also be caused by sIDHistory values which result from using the Active Directory Migration Tool to migrate users and groups from one domain to another. We will support
sIDHistory in 4.2 release.
Resolution:

This issue is fixed in DirectControl 4.1.1.

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

Related Articles

 articleKB-1958: ipc socket errors preventing connection to domain controller 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-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-3925: How to add Centrify parameter to a group policy