SMS 2003 SP2 component status?

[linkeloetje]

When looking at the component status of the primary site, the collums "last started" and "last message" are no longer updated. when looking in "SMS Service Manager" the collumn "Last Poll" as the current date. It seems that a crash occured at the same date that is showed in "last message". In the "D:\SMS\Logs\Crashdumps" directory the last crash occured on this "last message" date. The crash-directory name is 20070317_123331_smsexec and 2007-03-17 is the date in "Last message". I can't find a current error in any log file.

Before upgrading to SP3 I would like to resolve this issue.
Does anyone know were else to look?

 

[tbrennans]

How is your SQL setup, space wise, is it set to auto-grow?

Can you look on your server and see if the SMS related services are running? perhaps they are not! If they are not try to manually start them, if they are re-start them or re-boot.


there is a few things to check.

 

[linkeloetje]

SQL has plenty of space. Autogrow is default.
All services are running.

Ive installed the SP3 update, and everything except the update of the components messages work fine.
I've restarted service, restarted the server. But that didn't help. Maybe some windows update could have been the cause, but whose to tell.

 

[tbrennans]

by chance did the component status summarizer get disabled in the admin console site settings, status summarizers.

or since there seems to be an error that lead to this, it may be a reg key that got fudged. Something like the hklm\software\microsoft\sms\tracing or \components key. I'd poke around in there and make sure you can access it all (that and the other keys, if your locked out anywhere, bingo!)

 

[linkeloetje]

Thanks for you quick reply.
All status summarizers are enabled.

I've run "sms setup" without any changes. So the sms-site was reset. It looks like the column "last message" en "info"
get updated again.I will wait till tomorrow and see if the column "last started" will be updated.

 

[linkeloetje]

Well, it didn't help.
"Last message" gets stuck on yesterday date/time. column "last started" is stil not updated and all mesage counters have value zero. So nothing changed.

There must be something wrong with the "sms exec" service because all failing components are threads from this service!