SCCM console connection problem to SMS provider

I have installed sccm in the bolw deisgn for the lack of Cluster test environment. It is just to test SCCM HA.
SQL 2008 and SCCM 2012 Site server in two separate physical box(win 2008) and installed additional sms provider to another windows 2003 box. I am trying to connect the console installed on SQL box to new SMS provider(win 2003 box). It does
not connect. What could be the reason? Is it possible by technology at all or not? If it is, how could it be possible?
Thanks
Rafiqul

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

Migrate of SCCM Console connection

Hey,
I installed a second MP and additional SMS_Provider to one of my SiteServer to be able to connect via SCCM AdminConsole to it.
Unfortunately it is not working :P
What I already checked is the existence of WMI keys Root\SMS\site_<site code> with wmiexplorer and Remote Activation permission to site server and my new SMS_Provider server.My User has an assigned role and admin console version is supported
by site server (it is working if I connect to my Site Server).
Network connectivity is given, too (since I am running local on new SMS_Provider server)
I restarted the Site server the new SMS_Provider Server and the SMS_Agent Host & WMI service on both servers.
Please see SMSAdminUI log below:
[10, PID:3956][11/03/2014 17:21:13] :System.ArgumentOutOfRangeException\r\nProvider machine not found
Parameter name: configMgrServerPath\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)\r\n
[10, PID:3956][11/03/2014 17:21:13] :Transport error; failed to connect, message: 'Provider machine not found
Parameter name: configMgrServerPath'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nProvider machine not found
Parameter name: configMgrServerPath\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nProvider machine not found
Parameter name: configMgrServerPath
\r\nSystem.ArgumentOutOfRangeException\r\nProvider machine not found
Parameter name: configMgrServerPath\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)\r\n
[10, PID:3956][11/03/2014 17:21:13] :System.Management.ManagementException\r\nNot found \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of __ExtendedStatus
Operation = "ExecMethod";
ParameterInfo = "SMS_ObjectLock";
ProviderName = "WinMgmt";
\r\n
Thank you for help in advance ( I am sure this must be a very easy thing I do not see currently :))
Kind Regards
MK-Maddin

Hi,
Yes I know MP has nothing to do with Admin Console but this was what I did at once (whereas MP seems to work fine) - I just wrote to have you informed about the whole process which was done.
Well on newly installed SMS_Provider server I run the Admin Console and defined to connect to the FQDN of the new SMS_Provider server.
From my point of view in installation log of SMSP everything is (nearly) fine. :)
I received the following warnings and errors during the installation process:
WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106.
ERROR: Site component Manager did not respond after one minute, giving up.
ERROR: Failed to stop service SMS_SITE_COMPONENT_MANAGER, Win32 Error =0
ERROR: Failed to stop SMS_EXECUTIVE, Win32 Error=0
ERROR: Failed to get SMS_Identification class object.
But none of them caused the setup to stop.
Thank your for help

Router Console Connect Problem With Mini Usb (1941 Series - Os Win7 64Bit) (SOLVED)

I can not connect console with mini usb, my router is cisco 1941 series and my os win7 x64 help me please ?
My problem was solved thanks to this topic;
https://supportforums.cisco.com/discussion/11492306/usb-console-driver-install-failing#comment-9697916

Hi,
Here is how I have managed to enable the communication with the 1941 using the usb A-B cable:
Download the usb console driver 3.1
Install the x64 version on your PC (as administrator)
After the installation was completed:
Open the Device Manager. There will be a new entry named “CiscoUsbConsoleWindowsDrive”. Expand it and select the “Cisco USB to Serial adaptor”.
From the drop-down select “Update Driver Software…
In the “Update Drive Software” dialog select “Browse my computer for driver software”
In the next window, a driver location should be displayed, if not browse your PC and find the …\Windows_64 folder where you have extracted the 3.1 driver.
After the driver software was updated, there should be a new entry in the “Ports (COM &LPT)” named “Cisco Serial (COMx)”.
You can configure the port here:
Right click on the “Cisco Serial (COMx)” and select “properties” and set the properties to this;
Bits per second :9600
Data bits              :8
Parity                    :None
Stop bits              :1
Flow control       :None
The new COM port should be ready to accept the connection with the router.
I am using Tera Terms VT, and it is working well with the above driver and settings.
Should you wont to use the Cisco Configuration Professional (CCP) download the 2.7 version and make shore you have the current Adobe Flush and a current Java installed on you PC.
Hope this will help.
AlexS

Root Cause Analysis (OS and DB - OS Command Console) Connection problem!

Dear Community,
i've got a problem with the Root Cause Analysis OS Command console!
Currently I try to read the System MemStat info from the console, without success!
I've got the following errors:
Error1:
Error to parse the data returns by 'SAPOSCol', cause :com.sap.smd.plugin.remoteos.exception.SAPOSColDataParserException: Unknown Error during the parsing of saposcol output; nested exception is:
java.lang.NullPointerException
Error2:
'SAPOSCol' Service not availbale, detail :com.sap.smd.plugin.remoteos.exception.SAPOScolNotAvailable: SAPOSCol not available (detail output: )
The saposcol service is running, when I look on the server, I've got the correct status:
server:<sid>adm> saposcol -s
Collector Versions :
running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
Shared Memory       : attached
Number of records   : 5758
Active Flag         : active (01)
Operating System    : Linux server 2.6.5-7.283-smp #1 SMP Wed Nov 29
Collector PID       : 9536 (00002540)
Collector           : running
Start time coll.    : Wed Apr 23 15:00:58 2008
Current Time        : Wed Apr 23 15:12:08 2008
Last write access   : Wed Apr 23 15:12:04 2008
Last Read Access   : Wed Apr 23 15:12:03 2008
Collection Interval : 10 sec (next delay).
Collection Interval : 10 sec (last ).
Status              : free
Collect Details     : required
Refresh             : required
Header Extention Structure
Number of x-header      Records : 1
Number of Communication Records : 60
Number of free Com.     Records : 60
Resulting offset to 1.data rec. : 61
Trace level             : 2
Collector in IDLE - mode ? : NO
become idle after 300 sec without read access.
Length of Idle Interval : 60 sec
Length of norm.Interval : 10 sec
The strange thing is, sometimes it works, sometimes not!
Any Ideas?
System: Solution Manager 4.0 SP Stack 13
Thanks and regards
Sascha

>   running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux
>   dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16
I suggest you upgrade your saposcol on the Linux box, it's more than a year old and it's possible, that the SMD client needs a newer version that provides the data you're requesting.
Markus

Console Connection problem

I am trying to connect from my Windows 7 machine through IE 8. I can create machines do almost everything I need to except connect to the console.
The error I get is below.
I am able to VNC into the machine that I have VM Manager installed on which is centos 5.0 and connect to the console just fine.
load: class VncViewer.class not found.
java.lang.ClassNotFoundException: VncViewer.class
     at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed:https://oraclemgr:4443/OVS/faces/app/VncViewer/class.class
     at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
     at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
     at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     ... 7 more
Exception: java.lang.ClassNotFoundException: VncViewer.class

Firefox won't help you I'm afraid - the problem is actually at the server end not the client.
What you actually need to do is install TightVNC on your Oracle VM Manager node.
You can get it from http://oss.oracle.com/oraclevm/manager/RPMS/
You will then have to close down your browser on your Windows 7 machine and reconnect to the Oracle VM Manager system and try the console again. It will moan briefly about the certificate but accept it and carry on - you should not get the Java error again.
I found this a great help because the cursor control on my Oracle VM Manager is nearly imposible because I am 5000 miles away from it and over an ILO connection, but with TightVNC on my laptop I can get the same GUI up with mouse control that is as good as local!
Let me know if this fixes yours too!

Sunone Server console connectivity problem

I am not able to connect directory server through console , getting following error message
Cannot logon because of an incorrect userID,
Incorrect password or Directory Problem
HttpException:
Response: HTTP/1.1 500 Server Error
Status: 500
URL: http://10.0.2.4:52103/admin-serv/authenticate
but i am able to connect from other ldapbrowsers ...and directroy server is running what could be be problem with console...
Any advise will be appreciated.
Thank you.

try this
http://swforum.sun.com/jive/thread.jspa?threadID=48144&tstart=0
see reply #5

Sun iplanet console connect problems

Hello,
We've changed the ldap port from 389 to 390, we did this via the iplanet console.
Restarted ldap, everything OK.
Now we want to change it back to 389, but we can not connect with the iplanet console.
It looks like that the console besides the 27400 also connects to port 389 which is not running.
Any help would be great
Regards,
Dirk

hello,
problem solved: read the following
If you want to change the port number of the Configuration Directory Server used by your Administration Server, you can use either the following GUI or CLI instructions (391575)(391363):
GUI Instructions:
Open the Directory Console and select the Configuration tab.
Change the LDAP port to a new value
Click OK. The success dialog tells you to restart the server for the changes to take effect. Do not quit Console.
Restart Directory Server from the command line.
Next, change the Administration Server LDAP port with the following steps:
In Console, select the administration server that you want to change, and then click Open.
Click the Configuration tab, click Settings, and then change the value for Port.
Click OK. The success dialog tells you to restart the server for the changes to take effect.
Quit Console.
Restart Administration Server
To change the Administration Server LDAP port from the command, use the following instructions:
Command Line Instructions:
Go to the Administration Server's server root and make the following changes:
Open /admin-serv/config/adm.conf and change LDAP port to the new Configuration Directory Server port number.
Open /shared/config/dbswitch.conf and change the directory default URL to reflect the new port number.
Restart Administration Server. When you launch Console, it will point to the new Configuration Directory Server port.
Note: The above steps are performed for each individual Administration Server in the topology that will use a new Configuration Directory Server.
Regards,
Dirk

Problem after moving the SMS Provider

Hi, I have change the SMS Provider on a new server in my SCCM R2 SP2 configuration. The SCCM run the sql server 2005 localy (all in 64 bits), but the SCCM Console are extremly slow on my workstation. I have decided to move the SMS Provider on a new server. This config is benefit to my SCCM Console, because the console run more fast.
The SCCM Server is a Dual Xeon Quad Core 3 Ghz with 32 gig of memory running Windows 2003 R2 SP2 x64 with SQL 2005 Std SP2 x64. I have move the SMS Provider on a new server running Single Xeon Quad Core with Hyperthreading and 16 gig of memory with Windows 2003 R2 SP2 x64.
Now, when I try to edit Task Sequence in my OSD, I receive the error:
An error occurred when loadind the task sequence.
I use MDT 2010 integrated in my SCCM.
There is some reason for this error and how I can solve it ?
Thanks,
SteveSteve

Hi, here is the log. I can't understand because all SCCM console before meving the SMS provider are capable of editing task sequence.
[147F150 PID:2780] Initializing provider for namespace root\sms\site_P01 TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
[147F150 PID:2780] Initialization of provider for namespace root\sms\site_P01 succeeded TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 04:54:45 4940 (0x134C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 04:54:46 2444 (0x098C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:46 2444 (0x098C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:46 2444 (0x098C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 04:54:46 2444 (0x098C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 04:54:46 2444 (0x098C)
[PID: 2780] Invoking method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load node Use Toolkit Package from XML into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load children steps for node "Initialization" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load children steps for node "Execute Task Sequence" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load children steps for node "" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Failed to load XML for the task sequence into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
[PID: 2780] Done with method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 04:54:47 4940 (0x134C)
[147F150 PID:2780] Initializing provider for namespace root\sms\site_P01 TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
[147F150 PID:2780] Initialization of provider for namespace root\sms\site_P01 succeeded TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:07:00 2444 (0x098C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:07:01 4940 (0x134C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 4940 (0x134C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 4940 (0x134C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:07:01 4940 (0x134C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:07:01 4940 (0x134C)
[PID: 2780] Invoking method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load node Use Toolkit Package from XML into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load children steps for node "Initialization" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load children steps for node "Execute Task Sequence" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load children steps for node "" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Failed to load XML for the task sequence into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
[PID: 2780] Done with method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:07:01 2444 (0x098C)
[147F150 PID:2780] Initializing provider for namespace root\sms\site_P01 TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
[147F150 PID:2780] Initialization of provider for namespace root\sms\site_P01 succeeded TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:14:39 2444 (0x098C)
[PID: 2780] Invoking method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:14:40 4940 (0x134C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 4940 (0x134C)
Failed to export task sequence to XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 4940 (0x134C)
[PID: 2780] Done with method SMS_TaskSequence.ExportXml TaskSequenceProvider 2010-01-28 05:14:40 4940 (0x134C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:14:40 4940 (0x134C)
[PID: 2780] Invoking method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load node Use Toolkit Package from XML into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load children steps for node "Initialization" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load children steps for node "Execute Task Sequence" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load children steps for node "" from XML 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Failed to load XML for the task sequence into WMI 0x80041002 (2147749890) TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
[PID: 2780] Done with method SMS_TaskSequence.LoadFromXml TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Setting status complete: status code = 0x80041002; Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. TaskSequenceProvider 2010-01-28 05:14:40 2444 (0x098C)
Steve

SCCM Console Won't Connect to Site Server WMI Connection Issues

Ok, I've been scratching my head with this one for a while. We're running SCCM 2007 R3 in native mode, site server is Win 2008 Std R2, Config Mgr database sits on a seperate SQL box. When I launch the console (user account I use when logged into server
which is a member of SMS Admins group) on my Win 7 machine I receive the error..
The ConfigMgr console could not connect to the Config Mgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the Config Mgr site server and SMS
Provider computers
I've read numerous articles around DCOM permissions, I can confirm have all been set on the site server and SMS Admins group has the Remote Activation permission checked. Also I can open WMI, select properties to view the WMI namespace structure, permissions
on the SMS folder and subfolders are set as per microsoft articles.
So then I launched wbemtest from my Win 7 machine, when I try and connect to
\\[SiteServer]\root\sms\Site_SiteCode. I receive WMI error below. I can however connect successfully to WMI on any other server
Number: 0x80070005
Facility: Win32
Description: Access is denied
When logged into SCCM Site server and open wbemtest I can't remotely connect using WMI to any server in our domain, each time receiving the error below.
Error
Number: 0x800706ba
Facility: Win32
Description: The RPC server is unavailable
Whilst logged onto the site server I can use wbemtest to connect to itself using the SMS Provider namespace(\\[SiteServer]\root\sms\Site_SiteCode) which would suggest the WMI isn't corrupt.
It appears that I can't connect remotely to or from this machine using WMI, that something is blocking or not allowing the connection maybe? Please note the Windows Firewall is disabled, we don't use any third party firewall software on our servers and
WMI service is started.
Any ideas or suggestions on this one would be most welcome.
Cheers

Hi Eswar, thanks for the reply. This is the extract from the adminUI.log when I try and launch the console
[6][20/01/2012 10:24:21] :Insufficient privilege to connect, error: 'Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))'\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))\r\n
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n
[6][20/01/2012 10:24:21] :Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions to the ConfigMgr site and then
try to connect again.
\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))\r\n   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n
[8][20/01/2012 10:25:37] :Insufficient privilege to connect, error: 'Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))'\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))\r\n
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n
[8][20/01/2012 10:25:37] :Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException\r\nThe ConfigMgr Administrator console could not connect to the ConfigMgr site database. Verify your user has read permissions to the ConfigMgr site and then
try to connect again.
\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.BuildTreeWorker()\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
\r\nSystem.UnauthorizedAccessException\r\nAccess is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))\r\n   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)
   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\n
[3][20/01/2012 10:25:48] :Failure while loading required 'WQL' query engine, console cannot connect

What are the steps to remove SMS Provider traces from a server

Hi,
My client's environment is set up with a standalone primary site. They decided to install a second SMS Provider on a site system also running the Reprting Services Point to provide redundancy in the case the SMS Provider on the primary site
would go down.
They experienced a problem with the server running the second SMS Provider and it went down for about a day. The behavior for SCCM console users was to get an error message preventing them to connect to SCCM; they had to close the console and re-launch it
so it would randomly connect to the SMS provider on the primary site successfully. When a SMS provider is down, it seems the console won't redirect itself automatcally to another provider when trying to connect.
Since it was causing some frustration because console users had to launch it several times before they could connect, someone removed the second SMS Provider using the Site Maintenance wizard on the primary site. The thing is the wizard ran while the second
SMS Provider was down, it removed traces of this SMS Provider from the site configuration, but couldn't remove the actual SMS Provider files and registry entries since the server was down.
Now, only one SMS Provider is active on the primary site server, but we have orphaned SMS Provider files and registry keys on the site system server. Is there a way to remove them cleanly? The site system is still running the Reporting Services Point, so
we cannot remove everything related to SCCM.
Now we prefer to keep a single SMS Provider on the primary site server, since SCCM is not consider critical to the business anyway, and to avoid this issue in the future.
My guess would be to reinstall the SMS Provider from the Site Maintenance wizard and remove it after, but I just want to have feedback from people who might have deal with it in the past.
Tnx for help
Patrick

Hi,
Could you install the SMS Provider from the Site Maintenance wizard while SMS Provider files and registry entries are still there? Please have a look on the thread below, although it is for sccm 2007.
http://social.technet.microsoft.com/Forums/systemcenter/en-US/bb307748-7638-404d-a6a4-982827a051c8/how-do-i-remove-sql-provider-that-was-previously-installed-on-a-remote-sql-server?forum=configmgrsetup
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Not Widely Deploying the SCCM Console?

Hello all -
We are in the process of implementing SCCM 2012 R2 and the company I work for is fairly spread out, with lots of geographically dispersed locations and IT staff. Ideally we were looking to not deploy the SCCM console to these folks, but instead find
ways to make the functionality work outside of it. A few examples are:
All needed Collections based off AD Security Groups (tested this works)
SCCM Remote Connection, pull out of the console (tested this works)
I had a few questions based on this scenario:
Is there any way to make the resource explorer accessible outside of the SCCM Console?
Do a lot of people try and extrapolate the functionality out of SCCM like we are, or do most people deploy and train on the console?
When we were just looking at the collections and remove connection, i'll admit that I was leaning towards not deploying the console. Once I found out folks needed the Resource Explorer I started to wonder if just deploying the console would be the best
bet. I am worried we will keep finding these scenarios and it may been beneficial to just go the route of the console from the beginning.
I appreciate any feedback. Thanks.

A couple of additional notes here. The console uses a "fat" RPC connection to the SMS Provider. This generally does not perform well over WAN links so if you truly have a very spread IT population of folks needing access to console, I highly
recommend you use an RDSH solution.
Next, resource explorer would be the last reason I would give anyone access to the console. It's a nice tool for sure, but you can get the exact same (and a whole lot more) information out of the reports. I'm not saying don't give them the console,
just that resource explorer is not all that useful at the end of the day and can easily be replaced by reports.
Jason | http://blog.configmgrftw.com | @jasonsandys

The SCCM console happen to very slow

those days the sccm console happen to very slow, it is take long time to conenct to site database, also when i lucky login. the console UI is very very slow. i even can't do anything. loading any UI need even 10 minutes.

the sccm , sql installing on same server. i didn't see performance issue on server.
see this errorr in adminui log file:
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 = 'GDL'";
ProviderName = "WinMgmt";
\r\n
[5, PID:820][01/21/2014 03:12:44] :System.Management.ManagementException\r\nProvider load failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
[6, PID:4944][01/21/2014 03:35:30] :System.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 = 'GDL'";
ProviderName = "WinMgmt";
\r\n
[6, PID:4944][01/21/2014 03:35:30] :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 = 'GDL'";
ProviderName = "WinMgmt";

SMS Provider Locations Do Not Match - Problem installing SCCM 2012 R2 CU4

I have an SCCM 2012R2 CU1 site that has been upgraded from SCCM 2012 non-SP1, so I have gone from 2012 to 2012SP1 through CU5 and then to R2 and then to CU1.
Over the course of the life of this site, which has more than 10k clients and 10 Site Systems, we have installed roles, removed roles, moved roles and removed Site Systems.
I have also installed and removed SMS providers . . . which is where my issues begin.
The site properties in the console list 6 SMS Providers and even lists an SMS provider on a server that was retired and is no longer a Site System. When I query WMI using the following VBS script it only returns the *ACTUAL* SMS Provider locations,
2 of the 6 listed in the GUI.
On Error Resume Next
Const ForReading = 1, ForWriting = 2, ForAppending = 8
strComputer = "."
Set oFS = CreateObject("Scripting.FileSystemObject")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\sms")
If Err.Number <> 0 Then
WScript.Echo "Cannot connect to WMI"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set oLog = oFS.OpenTextFile("C:\Temp\SMS_ProvList.log",ForAppending, True)
If Err.Number <> 0 Then
WScript.Echo "Could not create output file"
WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
End If
Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_ProviderLocation",,48)
count = 0
For Each objItem in colItems
count = count + 1
oLog.WriteLine "-----------------------------------"
oLog.WriteLine Now()
oLog.WriteLine "Provider instance " & count & " : " & objItem.Machine
oLog.WriteLine "NamespacePath : " & objItem.NamespacePath
oLog.WriteLine ""
Next
I have a test environment which has also gone through some growth over its lifetime and has had the same changes to SMS Providers made. When I first attempted to install SCCM 2012 R2 CU4 in this test environment the installer continually failed the
prerequisite checker when querying the CU level of the SMS Providers. The only way that I could get past that issue was by running a site maintenance task via the CM installer and installing an SMS Provider at the location that had previously been an
SMS Provider but I had uninstalled that role.
I do not want to have to do that in my production environment, and would not even be able to do so if I wanted as I have retired one of the servers listed and cannot re-provision that machine.
Any CM12 gurus out there with suggestions? This strikes me as a standard MS problem when having multiple development teams working on a product/update and not having a standard location to check for configuration information (This is exactly the problem
when configuring DNS suffixes via GPO and not manually setting the GUI to match).
Thanks!
Josh Gerner
Cornell University.

The issue I have is that I cannot find the WMI class that holds the SMS Providers that are returned by the GUI.
I actually engaged MS Premier for a SCCM 2012 RAAS about 2 years ago and that was when the discrepancy first reared it's head. The support person that I worked with couldn't give me a way of cleaning those entries at that point which is when I started
logging the locations to be sure that my maintenance task was really installing or removing the SMS Providers.
Josh Gerner

Problem with Out of Band Discovery resulting with Out of Band features not available in SCCM console for computers with provisioned AMT device

Hi,
We configured the Out of Band component, but are using Intel SCS RCS to provision AMT devices remotely. The remote configuration process with Intel SCS works fine; we are able to connect to the AMT web UI and we can use a free KVM tool to manage the computer
remotely.
The AMT devices are configured with AD integration, so an object is created for each of them in a specific OU. Also, an AD group is added to the AMT devices so remote PT Administration permission is granted to it. This group includes the ConfigMgr Site
Server account, the account of the server running the Out of Band Service Point and my own user account.
This configuration seems OK since when connecting to the AMT web UI, I use Windows Integrated authentication with my user account and can manage the device successfully.
So the only step remaining is running the OOB discovery to enable Out of Band features for the computers in the SCCM console. We want to use the ConfigMgr OOB console. I right-click a computer or a collection and launch the AMT discovery. I check the OOB
server log, I don't see errors; the OOB service point connects to the AMT device and discover a status of 4, which is Externally provisioned, as expected. The problem is the AMT Status, AMT Version and Provisioned AMT fields for the computer in the ConfigMgr
console doesn't get updated, even after doing display refresh.
Here's the amtopmgr.log (I changed computer name and IP address information to protect client privacy) :
General Worker Thread Pool: Work thread 364 started SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
Discover COMPUTERA using IP address 192.168.12.7 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
session params : https://COMPUTERA.contoso.com:16993 , 11001 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
DoWSManDiscovery succeeded with user name: admin. AMTStatus = 1. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
session params : https://COMPUTERA.contoso.com:16993 , 484001 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
DoKerberosWSManDiscovery succeeded. AMTStatus = 4. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Discovery to IP address 192.168.12.7 16 15:16:32 364 (0x016C)
CSMSAMTDiscoveryTask::Execute, discovery to STI17259CPCO succeed. AMT status is 4. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CSMSAMTDiscoveryTask::Execute - DDR written to E:\SMS\MP\OUTBOXES\ddr.box SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Fill Machine Property' SID=1 MUF=0 PCNT=5, P1='COMPUTERA' P2='' P3='COMPUTERA.contoso.com' P4='' P5='' SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Created state message file: E:\SMS\MP\OUTBOXES\StateMsg.box\6heghx71.SMX SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='COMPUTERA.contoso.com' 16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Created state message file: E:\SMS\MP\OUTBOXES\StateMsg.box\rmit91js.SMX SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
General Worker Thread Pool: Succeed to run the task COMPUTERA.contoso.com 16 15:16:32 364 (0x016C)
General Worker Thread Pool: Work thread 364 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
General Worker Thread Pool: Work thread 364 exiting. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
The Management Point is up and running.
Any suggestion or advice is welcomed!
Thank you
Patrick

I found something interesting on this problem, it seems the OOB discovery process is working fine, but for an unknown reason, the site server is not receiving the information from the OOB Service Point to update the AMT Status of the client in the SCCM
database.
The log tells me that a DDR file is created to be sent to the site server. When looking into the SMS\MP\Outboxes\ddr.box folder, I see about 50 DDR files, the oldest one is dated when I started testing OOB discovery.
So the server is unable to send the files to the site server.
Also, since I started this thread, I noticed another issue that could be related to this problem. The same server is also holding the State Migration Point role, it is working fine, but when doing USMT operations, the status of the computer association is
not updated in the console (In Progress, Completed, missing USMT store path, etc.). When looking into the SMS folder on the server, I see a big backlog of SVF files containing information related to the SMP.
I looked into the log files, but didn't find the errors yet to explain this.
The computer account of the server is a member of the SMS_SiteSystemToSiteServerConnection_Stat_XXX group on the site server.
Note that status messages are being sent successfully, I see them in the Monitoring node of the console under Component State, and there is no backlog in the SMS\MP\Outboxes\statemsg.box folder.
Tnx for your help
Patrick

Reporting Services in SCCM Console (Cross Connect)

Hi,
we have a cas - primary site setup and have a reporting point on our cas server.
when connecting to the cas server with the sccm console from a client i see all reports and all is fine.
when connecting to the primary site server and type in the cas server in the reporting services pane i see no reports.
i thought that's possible. i can open the .../reportserver website with the client of course.
thx
steffen

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM console connection problem to SMS provider

Similar Messages

Maybe you are looking for