Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

NEW Unable to Connect to Console after Restore

  • Thread starter Thread starter sccmGuy
  • Start date Start date
  • Replies Replies 3
  • Views Views 3K

sccmGuy

New Member
Messages
2
Solutions
1
Reaction score
0
Points
1
Hi,
I have built a new server and restored current version of SCCM. Went from server 2012r2 to server 2019. The database is located on a dedicated sql server. I have went over the security settings in wmi several times and I am still not able to log in to the console. The repair option in the setup is greyed. I tryed uninstalling just the console and the registry hack to no avail. I have tried to reinstall sccm as well. I keep getting the same error listed below. I do have a successful connection the the sql box according to the ConfigMgrSetup log. Any help would be greatly appreciated.

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__75.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 = 'RC2'";
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__75.MoveNext()\r\nManagementException details:
instance of __ExtendedStatus
{
Operation = "ExecQuery";
ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'RC2'";
ProviderName = "WinMgmt";
};
 
Solution
I found the solution if anyone else needs it.
Although ConfigMgrSetup log states that the connection to sql was successful, it was not. At least not entirely.
I nuked the server user in sql and then added it back. That resolved the issue for me.

Take care.
I found the solution if anyone else needs it.
Although ConfigMgrSetup log states that the connection to sql was successful, it was not. At least not entirely.
I nuked the server user in sql and then added it back. That resolved the issue for me.

Take care.
 
Solution
I found the solution if anyone else needs it.
Although ConfigMgrSetup log states that the connection to sql was successful, it was not. At least not entirely.
I nuked the server user in sql and then added it back. That resolved the issue for me.

Take care.
You mean the computer account??? if you create a NEW server and renamed it to the OLD server then this is to be expected as the SIDs would be different.
 
Back
Top