SMS 2003 Admin Console not enumerating containers (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message


mwolcott -> SMS 2003 Admin Console not enumerating containers (9/17/2008 7:22:10 PM)

Strange problem here, and because of the nature of the issue, I'm mainly looking for advice where to start  Basically, the problem is that when clicking on Collections, or Advertisements, or ANY of the other containers in the admin console, the icon changes to an Hourglass, and never enumerates.  Sometimes (but not usually) if I click the plus sign before the container name, it will expand the list (of parent collections, for example), but even that usually just returns the Hourglass forever.  (Forever, in this case, means until I restart the MMC.  I've waited up to an hour.)

I can right-click and get the normal menu, and have been able to create collections, and advertisements.  Also, after I'd created an advertisement, which was created in the root of the Advertisement container (since I was unable to expand and drill into folders), I could right-click and Move the newly created advertisement to the appropriate folder -- in the Move wizard, expanding and enumerating worked fine.

The server is SMS 2003 SP3.  SQL is installed on the same physical server.  This is the only SMS server in the site, managing roughly 1000 servers.  Aside from general SMS functions (new agents being deployed, collections/advertisements being created, updating custom SQL reports, etc), no other direct changes to the server or configuration have occured (no new patches, products, server tuning, etc).  The last action I remember performing before noticing this behavior was the creation of a collection via vbscript (outside the console).  The script is the same script we've used for a couple years -- it does not change.  I've since confirmed that the members of the collection created are all valid, and healthy agents.

The processing on the server is within normal range (10-25% utilization), and well over 2gb available memory.  Disk activity is low/normal.  Logging into SQL directly, and viewing tables functions normally.  No relevant errors recorded in the system/application event logs.  I've reviewed a few of the SMS logs, but even though activity wasn't noticeably different than normal, I don't really know what to look for.  I've rebooted the server twice.  After each reboot, I can expand a couple containers once, but once I click about the 3rd or 4th container to expand, I get the endless hourglass again, and all other containers become unresponsive.  The order I click doesn't seem to matter, so it doesn't seem to be any specific container that puts the console in this state.  This occurs for all other admins, from remote terminals that have the SMS console installed, as well as directly on the SMS server.

From all the evidence, it appears the server is otherwise functioning normally... distributing advertisements, receiving agent check-ins, etc, but managing the environment is non-functional without the Admin Console.  Any suggestions of where I can start?  Any specific logs to look at first?  Any tools or integrity checks I could perform, manually or otherwise, to verify the health of SMS?  I'm not great with SMS, primarily just know the general "run the business" functions of SMS, so any guidance is greatly appreciated!

Michael




mwolcott -> RE: SMS 2003 Admin Console not enumerating containers (9/17/2008 7:27:17 PM)

I should also clarify that once a containers enters the "hourglass state" the MMC does not become unresponsive.  I can click other containers, each in turn will enter the hourglass state as well.  Also, the one branch that usually can expand, even after others have started entering the hourglass state, is the site hierarchy branch.  I can still review configuration information.  System Status --> Site Status also generally expands, however when clicking to Show Messages, that resulting window nevers brings up any messages.




skissinger -> RE: SMS 2003 Admin Console not enumerating containers (9/18/2008 12:03:32 PM)

Start here--> http://support.microsoft.com/kb/317872
In general though, I usually check dcomcnfg first (on the server).  That's historically (for me) usually ended up being the issue.  dcom settings will often be reset on windows server 2003 following an 03 service pack, or hotfix, or a service pack or site reset on SMS2003 on the server.  here--> http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq02.mspx, under server 2003 sp1, are the dcomcnfg things to check.




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.890625