Solved

Faulting application inetinfo.exe

Posted on 2004-09-10
13
1,585 Views
Last Modified: 2012-08-14
"Faulting application inetinfo.exe"
We keep getting this error in Application Log about five times each day. Not so long ago we applied SP1 to Exchange 2003 could it start cause the problem? And if so how it can be fixed? Also another error is appeared in System Log almost every minute
"Timeout (30000 milliseconds) waiting for a transaction response from the SMTPSVC service."

Any help will be greatly appreciated. Thanks.
0
Comment
Question by:Cymru1
  • 8
  • 5
13 Comments
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
what is the event id?
0
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
0
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
0
 

Author Comment

by:Cymru1
Comment Utility
It's event ID 1000.

Faulting application inetinfo.exe, version 6.0.3790.0, stamp 3e8000f7, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0xdcdf9645.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Then it seems to trigger a load of Event ID's 7011, timeouts with the pop/smtp/IISADMIN services and eventually  Event ID's 7034 service terminated unexpectedly.

Thanks.

0
 

Author Comment

by:Cymru1
Comment Utility
Forgot to mention, server is win2k3 server with exchange 2003 with all the latest patches and service packs.
0
 
LVL 15

Accepted Solution

by:
Yan_west earned 500 total points
Comment Utility
Btw, lots of people had your problem of different newsgroup, I have seen solution for windows 2000, but not for 2003. Nobody had any solution, in any case, follow this guideline (From eventID):

We have received reports about this event with various applications listed as the "Faulting application". To name a few: mmc.exe, winword.exe, iexplore.exe, newsupd.exe, matlab.exe, explorer.exe and list can go on and on. The "faulting modules" are typicall dlls used by those applications (and the event even gives us their version). All this tell us that this is a generic message from the operating system.

So Windows considers (in certain conditions) these applications as faulty. Windows NT/2000/XP is typically tolerant to applications as long as they "mind their own business". That is, they respond to the thread scheduler and do not attempt to use memory that is reserved to Windows itself. In this case, it seems that one of the modules used by the application tried to write in an area of the memory that is reserved for the operating system. If Windows would allow this, the stability of the whole system might be put at risk so the application is simply terminated and this event recorded. So, why would this happen? Why would an application try to use a portion of the memory reserved to Windows? Several posibilities:
1. Bugs. Probably most typical cause, a poorly written application may attempt to "break" the rules.
2. Applications/Dlls out of sync. Some applications may need a new dll but for some reason the dll on the system is an older version that does not support all the functions that the new application needs so the calls to these functions may have arguments that cause the dll to misbehave. The solution to this is to update the dll to the latest version or reinstall the application.
3. Corrupted files. If a dll is corrupted (i.e. problems with the hard disk, viruses, etc...) it is hard to predict what it can do when is loaded. Again, here the solution may be to reinstall the application. Also, the hard disks should be scanned (with scandisk) for potential errors. The latest service pack may help as well.
4. Hardware problems. The solution to this is obvious but it may be hard to detect it in the first place. Use it as the last resort.

The troubleshooting approach here would be the one for any faulty application or driver:
1. Obtain the latest updates from the vendor
2. Make sure the hardware is functioning properly
3. Reinstall the latest Service Pack
4. Run scanddisk (to fix any problems with the file system).
5. If file corruption is suspected uninstall and install again the application in question  
0
Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
Oh, just got this:

http://flaphead.dns2go.com/blog/archive/2004/08/20/315.aspx

seems to be your exact problem.
0
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
The stupid link is unavalable from all sources.. You'll have to contact microsoft to get your fix.. if you tell them it'S for this fix, they wont charge you.
0
 

Author Comment

by:Cymru1
Comment Utility
Cheers Yan. Unfortunately, that fix is no longer valid and is no longer available.
0
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
I know.. and everywhere this article is published, the link is bad.. something is wront with MS website for this link I think..
0
 

Author Comment

by:Cymru1
Comment Utility
It seems that the 872963 fix is gone. It's gone from the M$ website also.

I've just got off the phone with M$ and there is a new free fix although that is not on their site either. The new article number is 827214 but you must still refer to the "Exchange Information Store service terminates unexpectedly", and then the smtp, pop, etc., serviced failing. According to them, it's a Win2K3 server issue and not exchange.

They emailed the download within two minutes. All in all it was an excellent experience on the phone with no hassles. All I hope is that it continues to work.

The phone number is for the Small or Home Business section (800) 936-4900, option 2 then 5. You dont even need your product key to call.

Hope it helps someone else also.

Thanks for all the help. Its always appreciated.
0
 
LVL 15

Expert Comment

by:Yan_west
Comment Utility
Hey thanks, that's great info :)
0
 

Author Comment

by:Cymru1
Comment Utility
Last thing, make sure you try a chkdsk/f and reboot before installation. That was another recommendation.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Exchange 2013 P2P 15 60
EXCH2013 with DAG and Loadbalancer 11 32
Exchange & AD management console 2 40
Exchange Powershell help 6 29
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

728 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

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now