Jump to content


We use cookies to let you log in, for ads and for analytics. OK

Photo

Configuration Manager cannot connect to the site





  • Please log in to reply
8 replies to this topic

#1 shockwave

shockwave

    Advanced Member

  • Established Members
  • PipPipPip
  • 43 posts

Posted 16 February 2014 - 02:37 PM

Hello,

 

Everytime I start the configuration manager console after waiting some minutes I get the following error: 

Configuration manager cannot connect to the site (configmgr1.eindwerk.local).

The Configuration Manager console cannot connect to the Configuration Manager site database. Verify the following:
 
      • This computer has network connectivity to the SMS Provider computer.
      • Your user account has Remote Activation permission on the Configuration Manager site server and the SMS Provider computer.
      • The Configuration Manager console version is supported by the site server.
      • You are assigned to at least one role-based administration security role.
      • You have the following WMI permissions to the Root\SMS and Root\SMS\site_<site code> namespaces: Execute Methods, Provider Write, Enable Account, and Remote Enable.
     
 
 
back some week ago I installed SCCM and it worked. I could install the agent on clients, install software on the client through SCCM,...
 
Then yesterday I was trying to capture a OS. I lookup up how to do that and apparently Windows Deployment Services was necessary, so in server manager I installed it.
 
Today I try to continue. I open the console and I get the error mentionned above. I run C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\AdminCOnsole.msi and choose repair, it still doesn't work. I uninstall the windows deployment service, it still doesn't work. I install the console on a windows client, it doesn't work.
 
specs:
windows 2008 server r2 VM
sccm 2012R2
AD domain level windows 2008R2.
 
note:
In server manager: WSUS has a red cross next to it. I can't open it.
services installed on VM: file services, IIS, WDS, WSUS
 
Can anyone help me?
 
 

  • Bobbyslulp likes this



#2 Eswar Koneti

Eswar Koneti

    MCTS

  • Moderators
  • PipPipPip
  • 705 posts
  • Gender:Male
  • Location:Singapore
  • Interests:Computers,Gaming

Posted 17 February 2014 - 07:57 AM

Did you rerfer AdminConsole\AdminUILog\SmsAdminUI.log for more information about the error ? are you trying to connect locally or remote ?


Eswar Koneti | Configmgr Blog: www.eskonr.com | Linkedin: Eswar Koneti |Twitter: @eskonr

 


#3 shockwave

shockwave

    Advanced Member

  • Established Members
  • PipPipPip
  • 43 posts

Posted 18 February 2014 - 05:45 PM

locally,

 

this is wat is in SmsAdminUI.log (multiple times):

[5, PID:1096][02/16/2014 09:48:05] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'SVD'";
ProviderName = "WinMgmt";
};
 
Error Code:
ProviderLoadFailure
\r\nSystem.Management.ManagementException\r\nProvider load failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'SVD'";
ProviderName = "WinMgmt";
};


#4 Rocket Man

Rocket Man

    Advanced Member

  • Moderators
  • PipPipPip
  • 992 posts
  • Gender:Male
  • Location:Ireland
  • Interests:System Center 2007,2012

Posted 18 February 2014 - 06:58 PM

Maybe when you installed the WDS service and after the restart the SQL service did not restart automatically if SCCM, SQL and WDS on same box.

Check the services on the server.


Rocket Man

#5 newadmsccm

newadmsccm

    Advanced Member

  • Established Members
  • PipPipPip
  • 74 posts
  • Gender:Male
  • Interests:All about System Center Configuration Manager 2012.

Posted 18 February 2014 - 07:53 PM

Try insert IP address in console SCCM. Maybe can be problem in your DNS.



#6 shockwave

shockwave

    Advanced Member

  • Established Members
  • PipPipPip
  • 43 posts

Posted 20 February 2014 - 06:13 PM

Maybe when you installed the WDS service and after the restart the SQL service did not restart automatically if SCCM, SQL and WDS on same box.

Check the services on the server.

 

in the services window I tried to star the SQL server service and the error I got was:

 

Windows could not start the sql Server (MSSQLSERVER) service on Local COmputer

 

Error 1069: The service did not start due to a logon failure.

 

now that I remember, A week ago (or two) I had to change my admin password because it was expired.

 

I then changed the Administrator pasword back to the original. Logged in again. Then I could start the SQL server service and start the SCCM console.

 

Thanks



#7 Rocket Man

Rocket Man

    Advanced Member

  • Moderators
  • PipPipPip
  • 992 posts
  • Gender:Male
  • Location:Ireland
  • Interests:System Center 2007,2012

Posted 20 February 2014 - 06:20 PM

Good that it is working :) .... however I must stress the point that a dedicated SQL service account would be the best option for such services like SQL and set it that it does not expire and cannot be changed, because if any other service also used the original admin account with original password they too would not have been functioning.

It is good practice to do this. ;)


Rocket Man

#8 Shanks

Shanks

    Newbie

  • Established Members
  • Pip
  • 2 posts

Posted 08 April 2014 - 04:11 PM

Good that it is working :) .... however I must stress the point that a dedicated SQL service account would be the best option for such services like SQL and set it that it does not expire and cannot be changed, because if any other service also used the original admin account with original password they too would not have been functioning.

It is good practice to do this. ;)

 



#9 Shanks

Shanks

    Newbie

  • Established Members
  • Pip
  • 2 posts

Posted 08 April 2014 - 04:15 PM

All the above solutions didn't worked for me. AdminUI.log in Client PC where I am installing Admin console gives errors of Version mismatch. I am installing Admin Console from SCCM CD.

 

This worked for me:

1. Uninstalled Admin Console from Client PC

2. Copied AdminConsole.msi file from my SCCM server PC \\SCCM_PC\SMS_Site\Tools and then installed Admin console from this file

3. And Guess, I am able to connect to SCCM site from Client PC






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users