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-18828: Reporting Service does not startup after reboot where SQL server installed on the same machine

Authentication Service ,  

15 April,20 at 10:07 AM

Applies to: All versions of Centrify Infrastructure Service

Issue:
After restarting the machine where Centrify Reporting Service has installed (where the SQL server is on the same machine), the Reporting service does not start up automatically.

Cause:
Reporting Service relies on the SQL service as its dependence. While the SQL Service is not yet started during Reporting Service startup, Reporting Service will not be able to startup due to the dependence check failure.

Workaround:
Manually start up the Centrify Reporting Service after the SQL service has completely boot up

Solution:
We will delay the startup of Reporting Service to ensure the SQL service is started up completely. The fix will be included in Centrify Infrastructure Service 19.6.

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

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part II articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6041: How to show current license type in use by adclient articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6040: How to change the license type in use after adclient successful joined to the AD?