SMS MMC

Goto the SMS Home Page
This page details problems and issues relating to the SMS Microsoft Management Console.

_com_error exception in MMC Admin UI

Anyone seen this?

_com_error exception in MMC Admin UI!

Description: Factory Enumeration Failure
HRESULT : 0xEEEE0001
File : E:\OPALSP2\mmcadminui\Support\SMS_NMGR\NMGR_NodeData.cpp
Line: 272
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Description: Unable to get SQL connection. SQL Err>> #18456 Sev 14:
Login failed for user 'sa'. NEXT:SQL Err>> #10003 Sev 2: Login incorrect.
(null)
Error : WBEM_E_FAILED
Operation: ExecQuery
ParameterInfo: select ObjectKey, ObjectName from SMS_SecuredObject
Wbem error object:
instance of SMS_ExtendedStatus
{
     CauseInfo = "";
     Description = "Unable to get SQL connection. SQL Err>> #18456 Sev 14: Login failed for user 'sa'. NEXT:SQL Err>> #10003 Sev 2: Login incorrect. (null) ";
     ErrorCode = 3242263810;
     File = "E:\\OPALSP2\\sdk_provider\\nt\\smsprov\\SspObjectQuery.cpp";
     Line = 1642;
     Operation = "ExecQuery";
     ParameterInfo = "select ObjectKey, ObjectName from SMS_SecuredObject";
     ProviderName = "ExtnProv";
     SQLMessage = "Login incorrect.";
     SQLSeverity = 2;
     SQLStatus = 10003;
     StatusCode = 2147749889;
};

Entry Point : Result node factory error Security Rights Operation :
Command Line: C:\WINNT\system32\mmc.exe "D:\SMS\bin\i386\sms.msc"
Trace :
MMF Build Info : SMS 2.0 SP2 (1493)

This is an error message that I have seen in the past due to insufficient SQL connections available to the database. Increasing the number of connections at the SQL server (if they're not set to auto-configure), and increasing the number of connections allowed to the provider (by editing the 'smsprov.mof' and recompiling it) resolved this issue for my users.
 

Admin console died and now says 'Connection Failed'

My Admin consoles just died. I can't open the console, it reports connection failed?

There seems to be a number of possible solutions including:

  • First stop is here for a List of common "Connection failed" issues [updated 6/2/02]

  • 248823 '"Connection Failed" Attempting to Use Remote SMS Administrator Console'

  • If you're using SQL 6.5 make sure the database isn't full

  • You may have also noticed a real slow down of connecting recently so try stopping and starting the WMI service on the SMS Site Server

  • 199359 'How to Fix the WMI Repository of a Site Server'

Admin console fails to connect to SMS Site Server after PDC IP address change

My Site server and Site database server is a member server of a resource domain. Ever since we changed the IP address of the PDC of that domain, I can't connect to the site with MMC. What can I do to fix it?

Start the MMC and create a new snap-in of SMS as the security context has probably got lost when the IP address was changed.
 

Can I install the MMC on a Windows 95 machine?

Contributed By: Cliff Hobbs [MVP SMS]
No as detailed in the following extract from Chapter 6 of the SMS Administrator's Guide:

"You can install just the SMS Administrator console on any computer running Windows NT Workstation 4.0 with Service Pack 4 or Windows NT Server 4.0 with Service Pack 4 or later and Internet Explorer 4.01, Service Pack 1 installed. (Active Desktop is not required.) Anyone with permissions for SMS Administrator console items for a site can use this console to connect to a site database and administer the site.

Note:  On any one installation of Windows NT 4.0, Service Pack 4 (Windows NT Workstation or Windows NT Server), you can have either the SMS 2.0 Administrator console or the SMS 1.2 Administrator, but not both.

If you want to install the SMS 2.0 Administrator console on a computer that has the SMS 1.2 Administrator installed, set the computer to dual-boot and install the SMS 2.0 Administrator console on the second installation of Windows NT. Alternatively, use the SMS 1.2 Setup program to remove the SMS 1.2 Administrator and then install the SMS 2.0 Administrator console."

Check out Altiris' Web Administrator for SMS which does run on Windows 95:

http://www.altiris.com/products/webadminsms/

Can I Install the SMS Administrator Console on a Secondary Site?

Contributed By: Wally Mead [MS]
 The answer is yes but there doesn't seem a much point when you think things through... [Go to article]
 

Can I use the SMS Admin tools on Windows ME?

Contributed By: Cliff Hobbs [MVP SMS]
No. As detailed in Can I install the MMC on a Windows 95 machine? you can only install the SMS Admin tools on Windows NT/2000.
 

Clients not showing as assigned/installed in the MMC

I have clients that are showing up in my Collection but they don't show as having a client and site installed. However the client is assigned to the correct site.

Several workarounds to this one:

  • Remove and re-install the client

  • Use SQL Query Analyser to connect to the SMS database and then run a query 'select * from _res_coll_sms00001 where name = "machinename"' you will be able to tell if it is in your SQL database. After that a few refreshes will do the trick.

  • If the client software has been installed but the information reflected by the resource entry in the MMC remains incomplete or inaccurate, you can correct it by deleting the resource entry and copying the 'SMSDISC.DDR' file from the target client workstation's '%WINDIR%\sms\sms\core\data' directory to the site servers '\sms\inboxes\ddm.box'. The local DDR should have the client flag set to '1' and should refresh the database. This is the equivalent of doing a Heartbeat discovery.

    Wait a few minutes....then, in the MMC, highlight the All Systems Collection, right click and select     'All Tasks | Update Collection Membership'. This usually places a small hour glass over the Collection Icon. Right click again and select Refresh    . A valid resource entry should now appear.

'Connection Failed' message when trying to connect to the site database as a non-admin

I'm having a problem with the security settings on the MMC console. When I login as an administrator everything works fine. When I log in as a member of out help desk group I get a 'connection failed' error. I have set class and instance rights for queries and collections as needed but it appears that I have missed a step. Where have I missed it?

Add the Help Desk group to the 'SMS Admins' local group on the server acting as the SMS Provider. This allows access to the WBEM piece of the puzzle.
 

Custom MMC for HelpDesk staff for Remote Control

We are about to give some of our helpdesk technicians the SMS Administrator Console so that they can remote control users desktops. I have used SMS security to grant them access to only certain Instances within the Collections Class. This works great for collections but they can still view other Classes.

I want to be able to block them from seeing Security, Product Compliance and Tools. The only way I have been able to do this is to create a custom 'SMS.MSC' and replace the default 'SMS.MSC'. But this isn't really a good way to do it. Anyone can still right click on 'Systems Management Server | All tasks | Connect to Site Database'. They can then follow the prompts and load all the console tree items.

Does anyone know a way around this ? I really don't want helpdesk technicians to be able to see who has certain security rights. My company is very very security aware.

The MMC is known for it's bad security. If user's 'play' (the norm) then they'll find ways of getting into all sorts of things that you don't want them to (such as setting up new consoles in author mode, connecting to other Site Servers and loading all of the console items etc.)

Creating a custom MMC file only limits what the users can see and not what they can access. The Security Rights wizard within SMS controls what users can access. You also need to consider which groups have which rights to ensure people don't have access to anything they shouldn't.

If you do decide to create a custom console, make sure this console doesn't open in Author mode (if it does then the user will be able to add further snapins).

If you want to be able to run Remote Control from outside of the MMC see the article Can I run Remote Control from outside of the MMC?
 

Error: "_com_error Exception in MMC Admin UI!" When Connecting from an XP Machine

From the microsoft.public.sms.admin newsgroup
 If you’re seeing this error when trying to connect to the Site Server from an MMC installed on an XP Client then read on… [Go to article]
 

How do I get the Admin console to not prompt to save changes on exit?

Every time I exit SMS 2.0 client it asks me to save desktop settings. How do I turn this off?

Modify the shortcut that you are using to open the SMS Admin Console. Remove '/a' from the end of the target. For Example:

Change  "C:\Program Files\SMSADMIN\bin\i386\sms.msc" /a   to

"C:\Program Files\SMSADMIN\bin\i386\sms.msc"

The '/a' indicates that the console should be opened in author mode.
 

How do I get the Crystal Info node to show up on the MMC?

How do I get the Crystal Info node to show up on someone's MMC? It shows up on my Site Server, yet when I connect from another machine's MMC it doesn't. I don't see any security rights for reports.

It is an install option. You have to rerun the installation and choose Crystal Reports as one of the optional components.
 

How do I install the MMC on a Windows NT Terminal Server?

Run Setup with the /nohydracheck switch. For example:

setup.exe /nohydracheck

How to get the Admin console to "forget" an invalid site code?

I installed an SMS 2.0 SP2 Primary site with the wrong code, so I de-installed and re-installed SMS with the correct Site code. Now, when I launch the Admin Console on the Site server, for some reason it is defaulting to the old site code, and of course the connection fails. When I go to All Tasks and try to make the connection manually, it *still* uses the old Site code. So I have no way to launch the Admin Console on the Site server. Any idea's on how I can get the Admin Console to 'forget' the old Site code and pick up the new one?

If you uninstall and re-install SMS on server where the new Site code is alphanumerically greater than the previous code, the SMS Admin console can't connect to the Site database as the server's  namespace isn't removed from the WMI repository.

This problem and a workaround are detailed in Microsoft Knowledge Base article 239899 'SMS: Administrator Console Cannot Connect After Reinstallation' explains this problem and how to resolve it.
 

Is there anyway to extend the commands available in the MMC?

Yes - you can add external commands and utilities to the SMS Admin console by inserting information into the registry. The SMS Admin Console has a common registry key:

 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\NodeTypes
\{4D26C0D4-A8A8-11D1-9BD9-00C04FBBD480}\Extensions - this is all on one line

Checkout:

http://www.myitforum.com/articles/1/view.asp?id=430

1E is an IT infrastructure solutions company that provides a free .REG file that adds an "SMS Tools" menu to the MMC which will appear whenever you right-click a resource. This .REG file contains commands to:

  • Start a Command Prompt and Ping
  • Start NT Server Manager
  • Start NT User Manager
  • Start Telnet

You can download this .REG file from here.
 

MMC 1.2 File Versions

Contributed By: Cliff Hobbs [MVP SMS]
 Think there’s only one version of the MMC version 1.2? Well think again as this article shows. If you know of any others send them over and we’ll update the article... [Go to article]
 

Problem upgrading Admin console to version 1.2

Has anyone had a problem with the admin console not being updated to 1.2 after SP2 is installed? We weren't able to update ours for some unknown reason.

SP2 doesn't upgrade your admin console to MMC v 1.2 - you must apply SP2 to each of your admin console machines in order for them to connect to an SP2 Site Server.
 

Problems connecting to the site database across domains

I am logged in to Domain A which has a SMS 2.0 site. I can run my Admin Console and connect just fine. I cannot connect my console to a SMS site in Domain B. Is this possible? If I log in to Domain B I can connect ok. All permissions look ok to me. Is there a domain issue in regards to connecting to a site server in another domain?

The account you are using for SMS needs to be in the SMSAdmins group in domain B. Checks any trust relationships are setup correctly. You may also need to duplicate the account used for SMS both domains.  See the Security Essentials whitepaper for further details.
 

Quiet and unattended Installation of the SMS Admin Console

I know to use the following command line
 setup.exe /script <Scriptname>

Here is my script that I use.

[Identification]
Action=InstallAdminUI

[Options]
Action=InstallAdminUI
FullName=<USER>
OrgName=Microsoft
ProductID=<CODE>
SMSInstallDir=C:\Program files\SMSADMIN
SDKServer=<ServerName>

[SQLInstallOptions]

[SQLConfigOptions]

[LicenseServer]

It runs fine until the very end when Microsoft shows the ever so famous "OK" box to click because the setup ran successfully. Any Ideas on how to suppress this dialog box and make it fully quiet? I have tried /q /qn /qn1?

You can use:

setup.exe /nouserinput /script <script>

This works.
 

'Tasks' Section Missing in the SMS MMC

I have just installed and configured an SMS Primary Site (Central). Install path = SP2 then SP4.

All components appear to be working correctly, however the "tasks" section of the "database maintenance" area of the SMS Admin Console is not populated at all.

I'm pretty sure this is not a security issue (ie: no privileges to view section).

Child sites (Primary) of this Central site are fine, ie: they have the default list of maintenance tasks.

From the microsoft.public.sms.setup newsgroup
Try logging into the server with the account that installed the SMS site and then opening the console and seeing if the tasks are there. Also check the WMI permissions just in case there is an error with the permissions for that particular namespace. There shouldn't be but other people have seen this issue as well.
 

'The site server cannot be contacted' after re-installing MMC

I have a LAN Admin who had the SMS Admin Console installed and functioning last week, with correct security rights, etc. She got a new PC, and has rebuilt it. Yesterday she installed the Admin Console. However, when she tries to add the site server (same one that was configured in her old PC), it gives her the following error:

"The site server cannot be contacted. Please enter a new site server name."

I can connect to this Site server, as well as about a hundred other people. I went down to her desk and actually typed the name in myself, so I know there's nothing silly (like a typo) going on. Her security hasn't changed, and she's logging in with the same account that worked before. The user can't connect to any site servers from her Admin Console. 'SMSPROV.LOG' on the servers does not show the user's computer name or user ID anywhere. The user can connect to the sites when logged on to another PC. Checked out 248823 'SMS: "Connection Failed" Attempting to Use Remote SMS Administrator Console', and looked at her machine. The 'WBEMPROX.LOG' doesn't exist on her machine. I did the 'DCOMCFG.EXE' steps anyhow, but they didn't help.

Try running WBEMTEST and connect to 'root\cimv2' to see if you can enumerate the classes from the SMS database. If WBEMTEST won't start with the error 'Failed to create WbemLocator Object' you'll need to stop the WinMgmt service, delete the WBEM subdirectory and registry keys and then run WBEMSDK.EXE from a CAP. The WBEM install requires a reboot after which time you should be able to connect again.
 

Where can I get version 1.2 of the MMC from?

Contributed By: Cliff Hobbs [MVP SMS]

http://www.microsoft.com/downloads/release.asp?ReleaseID=39917
© FAQShop.com 2003 - 2008

Goto the SMS Home Page

 Email the Author