Tuesday, August 7, 2012

Unable to connect to the SCCM Console - How to fix issues related with connectivity to the SCCM Console

You may see the dreadful screen when SCCM console just refuses to connect to the database and throws up a generic error prompt 



First go through this link and ensure that the required checks are performed:
http://technet.microsoft.com/en-us/library/bb932213.aspx

Validate the errors in the AdminUI.log that is stored <Path where SCCM is installed>\Microsoft Configuration Manager\AdminConsole\AdminUILog
Check the event viewer for any specific errors. Perform the below steps for generic issues:
1. Ensure DCOM is active
a. Expand Component services > Computers > Right click My Computer and go to
"Properties".
b. Make sure that "Enable Distributed COM on this computer" is selected.
2. Validate the DCOM Permission
    1. From the Start menu, click Run and type Dcomcnfg.exe.
    2. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.
    3. In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.
    4. In the Launch Permissions dialog box, click Add.
    5. In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, type SMS Admins and click OK.
    6. In the Permissions for SMS Admins section, select the check box to allow Remote Activation.
    7. Click OK twice, and then close Computer Management
3. Verify WMI Permission
    1. On the SMS Provider computer, click Start, click Run, type wmimgmt.msc, and then click OK.
    2. Right-click WMI Control, and then click Properties.
    3. On the Security tab, expand Root, and then click SMS.
    4. Click Security in the results pane to see the permissions.
    5. Click Advanced, click SMS Admins, and then click View-edit.
    6. If the SMS Admins group does not have Enable Account and Remote Enable permissions, grant the permissions.
    7. Repeat this procedure for any groups used in addition to SMS Admins
4. Check whether the user has the necessary privileges to the SMS provider on the site server
5. Check whether the user has the necessary security rights to the database?
6. Verify namespace connectivity
    1. On the computer where the SMS Provider is installed, click Start, click Run, and then type wbemtest.
    2. Click Connect, type \\<siteserver>\root\sms, and then click Login.
    3. Click Enum Classes, click Recursive, and then click OK.
    4. In the Query Result list, double-click SMS_ProviderLocation.
    5. Click Instances, and then double-click the line that contains the target site code. For example, SMS_ProviderLocation.SiteCode="ABC."
    6. In the Properties section, locate the NamespacePath line. You might have to double-click this line to see the whole line.
    7. Copy the NamespacePath value to the clipboard. For example, copy the following value:
    8. \\Server1\root\sms\site_ABC
7. To verify server connectivity
    1. Close all WBEMtest windows from the preceding procedure.
    2. Click Connect, paste the NamespacePath that you copied in the preceding procedure, and then click Login.
    3. Click Enum Classes, click Recursive, and then click OK.
    4. In the Query Result list, double-click SMS_Site.
8. Verify the SMS Provider details
a. Open sms\bin\i386\smsprov.mof and validate the following text in the mof file
b. instance of SMS_ProviderLocation
c. {
d. SiteCode = "ABC"; -- here ABC refers to 3 digit side code
e. Machine = "CAS Server name";
f. NamespacePath = "\\\\<CAS SERVER NAME>\\root\\sms\\site_ABC";
g. ProviderForLocalSite = TRUE;
h. ;
9. Rebuild the namespaces:
    1. Recompiling the mofs located in the sms\bin\i386 directory will rebuild the namespace.
    2. This has to be done on the site server itself. Open a command prompt and go to the sms\bin\i386 directory. Once there, enter the following commands:
i. mofcomp smsprov.mof
ii. mofcomp smsstub.mof
iii. mofcomp pollprov.mof
iv. mofcomp netdisc.mof
v. mofcomp cpprov.mof
vi. mofcomp cmprov.mof
Posted by Picasa

16 comments:

  1. Section 2 validate DCOM permissions. SMS Admins does not exist

    ReplyDelete
  2. SMS Admins is just an Active Directory group, so it could have any name.

    ReplyDelete
  3. I'll add, check that your WMI provider hasn't exceeded its memory quota. You can determine this by opening up wbemtest and attempting to query the any WMI namespace.

    ReplyDelete
  4. If the Logs folder has the wrong permissions the console will not connect.
    In my case it was missing the administrators group and the system account.
    Just put it there and the console connects like normal again!

    ReplyDelete
  5. same issue here... it was one of the registry key is missing..

    save the following into note pad and save it as .reg then run it.

    this fixed my issue... good luck...
    -----------------------------------

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\QueryProcessors\WQL]
    "Assembly Path"="C:\\Program Files (x86)\\Microsoft Configuration Manager\\AdminConsole\\bin\\AdminUI.WqlQueryEngine.dll"
    "Depends On"=""
    "Type"="Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager

    ReplyDelete
    Replies
    1. Good call on this missing registry key and values. Had this causing connection problems even after a fresh uninstall/reinstall of the console on a machine.

      Delete
    2. Thank you!! it's working :)

      Delete
    3. I forgot to mention that this is Microsoft System Center Configuration Manager (SCCM) 2012 SP2 on a 64-bit Windows Server 2008 R2 Standard SP1.

      I tried to install the Intel SCS SCCM Addon version 2.1.6.3.

      Kjetil B.

      Delete
  6. This really helpful post, I am searching for this type blog. Thanks a lot , for share with us. I have a website about website error fix. You are welcome from my site.

    ReplyDelete
  7. Thank you! Working for me

    ReplyDelete
  8. This worked for me to after upgrading from SCCM R2 to SCCM R2 SP1. Thanks Mitchell

    ReplyDelete
  9. Thank you for posting such nice article read. I am very glad to read this. Really good one.
    Web Designing Company in Bangalore, Web Development Company Bangalore

    ReplyDelete
  10. A very well-written post. I read and liked the post and have also bookmarked you. All the best for future endeavors. Getting some solution regarding.
    UI Designing Companies, Web Application Development in Bangalore

    ReplyDelete