IIS Worker Process message box

Application Error Event 1004 appeared with this in the event log:

Reporting queued error: faulting application w3wp.exe, version 6.0.3790.1830, faulting module unknown, version 0.0.0.0, fault address 0x00730061.

Not sure why this is occurring, but have been unable to find any solutions about this on the newsgroups. I have seen other posts, but no answers.



Answer this question

IIS Worker Process message box

  • Bart Butell

    I'm getting the same thing, but only on front end servers. I also have Symantec Mail Security installed. Has anyone found a solution yet
  • XBTester

    We are using Symantec Mail Security for Exchange version 5.0.4.363
  • AtomZ .be

    the problem is with the SYMANTEC

    try this it will help , it worked with me fine

    To modify bmiconfig.xml to work around the issue:
    Open the services menu by going to Start -> Run and typing services.msc
    Stop the Symantec Mail security for Microsoft exchange service, and the
    Symantec Mail security spam statistics service, if they are started
    Open <system drive>:\Program
    iles\Symantec\SMSMSE\5.0\Server\SpamPrevention\bmiconfig.xml in a text editor
    such as notepad
    Go to the File menu, choose save as, and save the file as bmiconfig.old
    Delete the following strings:

    <ruleType>header_regex</ruleType>

    <ruleType>body_regex</ruleType>

    <ruleType>lang_header_regex</ruleType>

    <ruleType>lang_body_regex</ruleType>

    <ruleType>bodysig</ruleType>

    · Once those entries are deleted, go to the File menu, and choose
    save as, save the file as bmiconfig.xml

    · Restart the Symantec mail security for Microsoft exchange service;
    it is not necessary to restart the Spam statistics service.


  • ThugLife

    I am also having the same problem.

    Any help would be appreciated.


  • Sacha Vieux-Roy

    If you have an answer, please reply. If you do not, please do not.
  • Andre.Ziegler

    We had this suddenly occur back in December -- running version 4.x of Symantec Mail Security for Microsft Exchange witrh Premium Anti-spam enabled. We found this KB article: http://support.microsoft.com/kb/912586

    We contacted Microsoft and received the patch described -- situation improved dramatically, but there were some minor lingering issues. I think the real issue was described in Symantec bulletin and we applied these changes as well.

    http://service1.symantec.com/SUPPORT/ent-gate.nsf/0/7fdf38b55d675f868825723800032d67 OpenDocument

    Our consultant suggested we should upgrade to SMSME 5. No problems until evening of 1/3/07 -- after the Liveupdate had run and downloaded new signatures. Very similar situation -- after enough crashes of IIS worker process/w3wp.exe, system stops sending and receiving and requires reboot of system.

    I was researching to see if anyone had come up with more information before I went ahead with the suggestions from Symantec again.


  • wutwjd

    Update - I made the single edit they suggest in the Symantec article as a first step (remove <ruleType>body_regex</ruleType> from Bmiconfig.xml) and server seems to be running fine again.
  • TMF

    Having the same issue- after 51 failure events in the event viewer IIS shuts down - exchange stops working - have to reboot - manually restarting all the services doesn't always work.
  • Sergey D

    Quick Question !

    is anyonye using symantec bright mail or symantec for exchange


  • Meso X

    Hey,

    I also just started having this problem this morning.

    Reporting queued error: faulting application w3wp.exe, version 6.0.3790.1830, faulting module davex.dll, version 6.5.7651.60, fault address 0x00067922.

    Has anyone came up with a solution to this

    Thank You


  • roboky

    I have SMSME 5 :)

    and yes it is affected i used the workaround 2


  • Rob1234

    Hi,

    We just started geting the same problem:

    Reporting queued error: faulting application w3wp.exe, version 6.0.3790.1830, faulting module unknown, version 0.0.0.0, fault address 0x00ee1aae.

    Anybody seen a solution to this

    Thanks



  • IIS Worker Process message box