Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Faulting smc.exe

Updated: 22 May 2010 | 10 comments
delifeath's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I'm getting a faulting smc.exe error.  A few times this has been accompanied by loss of network connection until I have completely uninstalled and reinstalled.  At the same time as this error (and sometimes on it own) a bunch of machines have the password prompt appearing (as if they received the smc -stop command)  If I input the password it actually does stop smc.exe.  All of this started happening today for some reason, nothing has been any different recently other than today being the monthly scan day.  (This problem appeared 2 days ago) and the fact that the server was down this weekend for a few hours.  The SEPM and most clients are using MR4 MP2.  Any insight would be greatly appreciated.  Thank you.

Comments

Here2Help's picture
10
Aug
2009
0 Votes 0
Login to vote

Hi, Can you post a screeshot

Hi, Can you post a screeshot of the exact error message from one of the clients ?

Thanks :-)

Regards,
AMOL BHOSALE
SCTS, MCP

Grant_Hall's picture
10
Aug
2009
0 Votes 0
Login to vote

Haven't heard of this

Haven't heard of this happening. As here2help said a screenshot would be great. My first thought was that  you might have an infection. Maybe a full scan in safe mode on one of these machines might not be a bad idea.

Cheers,
Grant

Please don't forget to mark your thread solved with whatever answer helped you : )

kailaspadwale's picture
10
Aug
2009
0 Votes 0
Login to vote

I am also facing same problem.

Hi,

I am also facing same problem, please help.

Thanx,
KAILAS

Paul Mapacpac's picture
10
Aug
2009
0 Votes 0
Login to vote

Hi TS and Kailas, please post

Hi TS and Kailas, please post a screenshot of the error. Have you had a recent update of Windows?

delifeath's picture
11
Aug
2009
0 Votes 0
Login to vote

Update

It's been a little crazy here because we've seen a decent number of pc's with this situation.  I was thinking the same thing along the lines of an infection because as I mentioned previously, in some cases it actully looks like the machine has received the smc -stop command.  Full scan's have been done with the newest virus defs and no there hasn't been any windows or application updates done very recently.  Kailaspadwale, have you just started seeing this in the past 3 days?  I opened a case with Symantec yesterday because i've seen KB articles and threads with similar situations in much older versions of SEP.  (Case # : 281728766)  All they have told me for now is to push out a new package to the clients that have this issue, and to make sure that the setting is checked which says to remove all communications files, etc.  They told me to let them know if it comes up again after that.  I haven't had the chance to do this yet.  I do know that I have a few machines which appear to have stopped doing this after a repair, and at least one other that is still doing it even after a full uninstall and reinstall.

Here are the types of errors we're getting out of the blue on random machines:

(Sorry about the second one...It was taken by someone else on a huge monitor, I had to zoom in on the print screen.  I'll try to get another one.)

imagebrowser image

imagebrowser image

imagebrowser image

Peterpan's picture
11
Aug
2009
0 Votes 0
Login to vote

same problem encountered, but

same problem encountered, but the workaround I did is to reinstall the SEP 11, I believe there is some conflict on the application installed on that machine? I am hoping that MR5 release will resolve this issue.

:-)

delifeath's picture
11
Aug
2009
0 Votes 0
Login to vote

Peterpan, When did this start

Peterpan,

When did this start happening for you?  Thanks

delifeath's picture
11
Aug
2009
0 Votes 0
Login to vote

Update

Symantec called and we closed this case today.  It seems that repairs have taken care of all but one of specific machine.  The one thing I did get out of the tech was that in the past they have had this happen on an older version of SEP and it could possibly have been caused by bad definitions or something else that was updated recently.

Grant_Hall's picture
11
Aug
2009
0 Votes 0
Login to vote

Well I am glad you got this

Well I am glad you got this solved. It was screaming virus to me, but I am glad that it was something simpler : )  I am going to mark your last post as the solution, but if you want this thread kept open for whatever reason please pm me and I will remove the solved mark.

Cheers
Grant-

Please don't forget to mark your thread solved with whatever answer helped you : )

Peterpan's picture
12
Aug
2009
0 Votes 0
Login to vote

we are experiencing this kind

we are experiencing this kind of issue from SEP version MR2 currently we stil encountered this in the latest version MR4 MP2 but not all of our pc.

:-)