Skip to main content

configmgr console crashes with “the given key was not present in the dictionary"

Frustration

Image by bdgamer via Flickr

one of our site servers seemed to exhibit this puzzling problem.  i stumbled upon this because the site server’s reporting page would not come up correctly.  i also noticed that when i tried to fire a report from the console, it was trying to go to http://myServer:0/smsreporting_xyz.  i knew that couldn’t be right because the port was usually set to 80 or some other value.

i tried to get into the reporting components and received an error.  i thought it was related to the local console at first.  i tried it under my credentials, other credentials, on the server, on my workstation, from the local site server, and from the central site server – which all failed nicely.

as a last resort, i used what little i learned in school and actually read the failure message.  if you’ve been reading my blog awhile, then you’re probably well aware that i got nothing out of this message. :)

image

you won’t be able to read the stack trace in the screenshot, but I’ve copied the contents and dropped it in below.  the important value to capture is right at the top “The given key was not present in the dictionary”.

Server stack trace: 
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.ReportingPointControl.InitializePageControl()
   at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()
   at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
   at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

alright, so i knew the condition that was causing this.  every time i tried to view the reporting component options, the mmc would crash.  i could reproduce this on every machine available for this particular site server.  at this point, you may want to stop reading.  (if you’re my microsoft support rep, you can stop reading, too.)  i had to hack the dreaded site control file (sitectrl.ct0).  it’s pretty cryptic so you’re not exactly supposed to know what you’re doing – hence the statement that you jeopardize support if you do this type of operation.

i’m making it sound more complicated than it was.  i compared the control files from the broken site and a working site.

bad:

BEGIN_SYSTEM_RESOURCE_USE
    RESOURCE<Windows NT Server><["Display=\\myServer\"]MSWNET:["SMS_SITE=XYZ"]\\myServer\>
    ROLE<SMS Reporting Point>
    PROPERTY <ReportingPointFolder><><SMSReporting_XYZ><0>
    PROPERTY <Server Remote Name><myServer.myDomain.com><><0>
    PROPERTY <Server Remote Public Name><><><0>
    BEGIN_PROPERTY_LIST
        <Objects Polled By Site Status>
        <["Display=\\myServer\x$\SMS\"]MSWNET:["SMS_SITE=XYZ"]\\myServer\x$\SMS\>
    END_PROPERTY_LIST
END_SYSTEM_RESOURCE_USE

good:

BEGIN_SYSTEM_RESOURCE_USE
    RESOURCE<Windows NT Server><["Display=\\myServer\"]MSWNET:["SMS_SITE=XYZ"]\\myServer\>
    ROLE<SMS Reporting Point>
    PROPERTY <ReportingPointFolder><><SMSReporting_XYZ><0>
    PROPERTY <Protocol><><><0>
    PROPERTY <PortNumber><><><80>
    PROPERTY <Server Remote Name><myServer.myDomain.com><><0>
    PROPERTY <Server Remote Public Name><><><0>
    BEGIN_PROPERTY_LIST
        <Objects Polled By Site Status>
        <["Display=\\myServer\x$\SMS\"]MSWNET:["SMS_SITE=XYZ"]\\myServer\x$\SMS\>
    END_PROPERTY_LIST
END_SYSTEM_RESOURCE_USE

now that we know what we’re working with, here’s what i did:

  1. copy the sitectrl.ct0 file to sitectrl.mco
  2. edit the contents of sitectrl.mco to match the good site (just the tags marked “PROPERTY” were different)
  3. stopped the sms executive
  4. renamed the sitectrl.ct0 to sitectrl.bak
  5. dropped in sitectrl.mco as sitectrl.ct0
  6. fired up sms executive

after that, i restarted the console and tested the reporting component properties.  worked fine.  i tested the reporting page.  that worked, too!

Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »