Re: smsexec.exe faulting module kernel32.dll

Hi KK,

The crash is basically telling you that it is the SMS_STATUS_MANAGER
crashing the SMS_Executive service and then it also gives you the thread ID
where the crash occured. From the log entries you've posted we can't see why
it's crashing as usually you will see a particular file (such as a Status
Message) that it keeps crashing on every time. If that were the case and you
deleted the Status Message the error would likely go away but in this case
(from the logs) it seems that we are talking about a SiteCtrl change in
progress and as Thierry said, you don't want to EVER delete your SiteCtrl.ct0
file (unless you want to go through an exercise in Site Recovery). With each
crash is it consistent with the Thread ID or does it change? Honestly for
this type of problem it is probably best to contact Microsoft Support.

A few other things would be:

1. Enable Debug logging on the problem server (there is a KB article for
this)
2. Check to see if the thread ID is consistent
3. From the thread ID, filter the corresponding component log (in the last
case, Status Manager) by the thread ID.
4. See if you can identify the specific file it is crashing on

Also:
1. Make sure you take a Site Backup
2. Run CHKDSK/ScanDisk against the problem server to make sure of no file
corruption
3. Possible Defrag (doubt it would help resolve the issue at hand, but if
you're getting bad files written to the disk causing exec to crash it can't
hurt).
4. Run AV Scan

Let us know if the component is consistent. (ie. Is it ALWAYS Status
Manager or does it change?)

-Jeff

"KKYee" wrote:

> Is it possible that this maybe related to a software distribution? I notice
> this happens after an create an advertisement or when a client computer tries
> to run the advertised program.
>
> "Thierry" wrote:
>
> > No never delete the sitectrl.ct0 file.
> > In your log, i don't see any problem
> >
> > If it's not a problem to loose some status, you can delete all file in
> > E:\SMS\inboxes\statmgr.box\statmsgs and subdir.
> >
> > "KKYee" <techusergroups(removebrackets)@gmail.com> a écrit dans le message
> > de news:C86478B3-AFBC-42F8-B8A0-113746E0EFB1@xxxxxxxxxxxxxxxx
> > > Thanks Thiery.
> > >
> > > In SMS_STATUS_MANAGER 5616, I get the following
> > >
> > > Site code: 002 $$<SMS_STATUS_MANAGER><Mon May 30 12:02:18.165 2005
> > Mountain
> > > Daylight Time><thread=5616 (0x15F0)>
> > > Site type: Primary Site $$<SMS_STATUS_MANAGER><Mon May 30 12:02:18.165
> > 2005
> > > Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Resolved the "Status Manager" inbox to
> > > "E:\SMS\inboxes\statmgr.box\statmsgs". $$<SMS_STATUS_MANAGER><Mon May 30
> > > 12:02:18.196 2005 Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Opened a change notification handle for directory
> > > "E:\SMS\inboxes\statmgr.box\statmsgs". $$<SMS_STATUS_MANAGER><Mon May 30
> > > 12:02:18.196 2005 Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Resolved the "Site Control Manager (Master Site Control File)" inbox to
> > > "E:\SMS\inboxes\sitectrl.box". $$<SMS_STATUS_MANAGER><Mon May 30
> > > 12:02:18.243 2005 Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Opened a change notification handle for directory
> > > "E:\SMS\inboxes\sitectrl.box". $$<SMS_STATUS_MANAGER><Mon May 30
> > > 12:02:18.243 2005 Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Parsed the master site control file, serial number 177.
> > > $$<SMS_STATUS_MANAGER><Mon May 30 12:02:18.243 2005 Mountain Daylight
> > > Time><thread=5616 (0x15F0)>
> > > This site is the central site. $$<SMS_STATUS_MANAGER><Mon May 30
> > > 12:02:18.243 2005 Mountain Daylight Time><thread=5616 (0x15F0)>
> > > Summarizer SMS_OFFER_STATUS_SUMMARIZER registered for status message
> > stream.
> > > $$<SMS_STATUS_MANAGER><Mon May 30 12:02:18.274 2005 Mountain Daylight
> > > Time><thread=5616 (0x15F0)>
> > > STATMSG: ID=1203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_STATUS_MANAGER"
> > > SYS=SUPPORT SITE=002 PID=6024 TID=5616 GMTDATE=Mon May 30 18:02:18.274
> > 2005
> > > ISTR0="SMS_OFFER_STATUS_SUMMARIZER" ISTR1="" ISTR2="" ISTR3="" ISTR4=""
> > > ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
> > > $$<SMS_STATUS_MANAGER><Mon May 30 12:02:18.274 2005 Mountain Daylight
> > > Time><thread=5616 (0x15F0)>
> > >
> > > Do you mean to delete files that are in the listed folders? ie.
> > > "E:\SMS\inboxes\sitectrl.box".
> > >
> > > KK
> > > "Thierry" wrote:
> > >
> > > > In the crahsdump, open the log for SMS_STATUS_MANAGER_5616 and you will
> > see
> > > > which file have problem and delete this file
> > > >
> > > > "KKYee" <techusergroups(removebrackets)@gmail.com> a écrit dans le
> > message
> > > > de news:78E69848-6EBF-4479-AA67-79941779C921@xxxxxxxxxxxxxxxx
> > > > > smsexec.exe services will stop every few hours. When it does crash, a
> > log
> > > > > file folder is created in the crashdumps starting that looks like
> > this:
> > > > >
> > > > > Time = 05/30/2005 13:14:19.524
> > > > > Service name = SMS_EXECUTIVE
> > > > > Thread name = SMS_STATUS_MANAGER
> > > > > Executable = E:\SMS\bin\i386\smsexec.exe
> > > > > Process ID = 6024 (0x1788)
> > > > > Thread ID = 5616 (0x15f0)
> > > > > Instruction address = 77e649d3
> > > > > Exception = e06d7363 (Unknown exception code)
> > > > > Description = ""
> > > > > Raised inside CService mutex = No
> > > > > CService mutex description = ""
> > > > >
> > > > > I am trying to distribute software. However this is giving my package
> > > > > delivery grief. Any idea why I should start to trouble-shoot this?
> > > > >
> > > > > --
> > > > > KKYee
> > > > > Application Analyst
> > > > > SMS Admin
> > > > > Crystal Report Writer
> > > >
> > > >
> > > >
> >
> >
> >
.

Relevant Pages

  • Re: XFS: how to NOT null files on fsck?
    ... >> disk state on crash might be that the data update was done and the ... Application crashing? ... I don't think that the performance implications are large in typical ... BTW, the way my current hardware acts up, system crashes are more ...
    (Linux-Kernel)
  • Re: MS Office 2008
    ... but not on a Mac :-) ... Is the crashing associated with any particular document, ... Is there any specific event or command that seems to trigger the crash? ... Provide complete descriptive responses & ...
    (microsoft.public.mac.office.word)
  • Re: New User needs Freeware Firewall ...
    ... >> first it would not load at startup. ... This was an acknowledged problem ... Then my machine started locking up and crashing. ... >> then my machine would only crash a couple of times a day. ...
    (comp.security.firewalls)
  • Re: Autorecover not working or saving file.
    ... > The problem with 2 minuts is once it saves, the temp file PP uses to reopen ... > and the crash. ... It seems that the real problem is to get it to stop crashing, ... Steve Rindsberg, PPT MVP ...
    (microsoft.public.mac.office.powerpoint)
  • Re: Word 2004 + Macintel + Some Adobe OpenType Fonts = Crash on save
    ... I'm told this isn't technically a maggie, ... program has started to crash ... It's not consistent, ... This thing just keeps getting weirder. ...
    (microsoft.public.mac.office.word)