Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

IIS trouble on Exchange server - Application Error - Event ID:1000 - System Log - Warning -WAS EventID 5139 generated at same time.

Posted on 2016-08-09
5
Medium Priority
?
472 Views
Last Modified: 2016-08-17
I have a Windows 2008 R2 DataCenter SP1 running Exchange 2010 SP3 Rollup 14.  IIS 7 is installed too.
Every 20 - 25 minutes I receive about 20 Event id: 1000 logged over a 3-4 minute span.  Then there's peace until the events get logged again in about 20 minutes.  When these application events get thrown I received warnings (5139) in the System log at the same time.

Log Name:      Application
Source:        Application Error
Date:          8/9/2016 12:01:34 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HQVS06.mlg.us
Description:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23455, time stamp: 0x573a54fc
Exception code: 0xe053534f
Fault offset: 0x000000000001a06d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-09T16:01:34.000000000Z" />
    <EventRecordID>1143679</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HQVS06.mlg.us</Computer>
    <Security />
  </System>
  <EventData>
    <Data>w3wp.exe</Data>
    <Data>7.5.7601.17514</Data>
    <Data>4ce7afa2</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.23455</Data>
    <Data>573a54fc</Data>
    <Data>e053534f</Data>
    <Data>000000000001a06d</Data>
  </EventData>
</Event>
0
Comment
Question by:mlghelp
  • 3
  • 2
5 Comments
 
LVL 29

Assisted Solution

by:Dan McFadden
Dan McFadden earned 2000 total points
ID: 41751669
Since the error appears to occur at a regular frequency, is there a monitoring system tapping the system at that time?

Also, here you read the following articles/threads?

1. https://social.technet.microsoft.com/Forums/en-US/89e41ca7-9095-448c-a72d-0d07e6c66207/exchange-2010-iis-not-working-event-id-5139?forum=exchangesvrsecuremessaginglegacy
2. https://technet.microsoft.com/en-us/library/cc735207(v=ws.10).aspx

Also, in the application pool that supports the site, under Advanced Properties, under section "Process Model"... what is the "Idle Time-out (minutes)" properties set to?  20 minutes?

Have you tried setting it to "0" which would disable the timeout process.  What may be happening is that there is no activity on the site for 20 minutes and IIS then shuts down the apppool.  The next in bound request causes IIS to start a new process for the apppool which could be throwing the errors as the process makes the initial request.

Dan
0
 

Author Comment

by:mlghelp
ID: 41752980
Dan,  Checked into all your suggestions with no luck.  We don't have a monitoring system but we do have a GFI Mailarchiver application installed on another server that keeps history of all our emails.

So I took a look into the Mail Archiver server , no errors logged.  But I did notice windows updates were available so I took the opportunity to install them and disable the Mail Archiver services.  I left then stopped for 1 hour and walla...no errors logged on Exchange.

I'm now working with GFI to resolve this issue as it appears their software is the cause.

Thanks Again for your reply.
Todd
0
 
LVL 29

Expert Comment

by:Dan McFadden
ID: 41753437
Glad to hear that you isolated the culprit.

Dan
0
 

Accepted Solution

by:
mlghelp earned 0 total points
ID: 41754429
Issues resolved.  Turns out our Exchange Journaling Mailbox was chock full of oversize emails which GFI Mail Archiver could not pull over.  A tech from GFI enlarged a MAPI and EWS setting on their side to accept the larger emails, others (still to large) that were garbage emails still remained.  I loaded the Journaling Mailbox via Outlook (oddly enough OWA showed the number count of the large email, but not the actual emails) created a rule to permanently delete them and our Exchange logs are free of 1000 Application errors.
0
 

Author Closing Comment

by:mlghelp
ID: 41759072
Third party software involved in initial problem.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question