Error 4689
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine TechNet Subscriptions TechNet Video
Event Id 4689 Process Termination
TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security Virtualization the run-time environment has detected an inconsistency in its internal state Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL
Event Id 4688
Server 2014 SP1 Windows 8.1 Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. COM+ COM+ Service COM+ General Functionality COM+ General Functionality Event ID 4689 Event ID 4689 Event ID 4689 Event ID 771 Event ID 772 Event ID 773 Event ID 774 Event ID 775 Event ID 776 Event ID 777 Event ID 778 Event ID 779 Event ID 780 Event ID 781 Event ID 782 Event ID 783 Event ID 4433 Event ID 4434 Event ID 4435 Event ID 4440 Event ID 4441 Event ID 4444 Event ID 4445 Event ID 4446 Event ID 4449 Event ID 4450 Event ID 4451 Event ID 4453 Event ID 4454 Event ID 4455 Event ID 4456 Event ID 4457 Event ID 4458 Event ID 4459 Event ID 4460 Event ID 4462 Event ID 4463 Event ID 4464 Event ID 4465 Event ID 4689 Event ID 4690
Question Need help? Post your question and get tips & solutions from a community of 418,502 IT Pros & Developers. It's quick & easy. Error 500.13 (Server too busy) and Event 4689 P: 4 jn00s I am running a windows 2003 server with close to 150 websites. The majority of the sites, which are all running the same very complex classic ASP portal application using ASPImage/ASPMail/ASPUpload, are receiving the vast majority of the traffic and all are working fine. However all of my smaller websites that do not use this application or any of those 3rd party COM DLL's, and only get a tiny bit of https://technet.microsoft.com/en-us/library/cc774264(v=ws.10).aspx traffic across just a few simple ASP scripts, all fall into a state of perpetual 500.13 errors after about an hour. I have had to put IISRESET onto an hourly scheduled task to keep them from being down too much, but this adversely affects all my users because they're getting Service Unavailable errors ever hour. The main clue I've found so far is that the Application log is completely full of Event 4689 errors https://bytes.com/topic/asp-classic/answers/632420-error-500-13-server-too-busy-event-4689-a that are happening at a rate of sometimes several per second. The text of this eventlog entry is always the same: Expand|Select|Wrap|Line Numbers Therun-timeenvironmenthasdetectedaninconsistencyinitsinternalstate.ThisindicatesapotentialinstabilityintheprocessthatcouldbecausedbythecustomcomponentsrunningintheCOM+application,thecomponentstheymakeuseof,orotherfactors.Errorind:\nt\com\complus\src\comsvcs\threads\stathread.cpp(285),hr=8007000e:CSTAThread:CoGetApartmentIDfailed I've been scouring the web for weeks and the only solution I found so far was to completely uninstall/reinstall IIS and DCOM, and I'm not really convinced that this step would solve the problem as both of my webservers do the same thing. One other thing that seems like it's probably relevant (but may not be at all), is the way in which I set up my websites. I use an ASP script to build or rebuild my websites in IIS. It's based on code put out by microsoft in their IIS admin scripts, I just simplified it into functions that I could call from within my scripts. Originally it was built to work with Windows 2000 Server so it would just set the app to isolated on each site and that worked great, and I never had any 500.13 erros. For Win2003 I modified the script so that it creates an app pool for each website as it builds or rebuilds the website. If the app pool already exists, it seems to still work fine: either because another duplicate pool is not created, or because the first one is deleted when the script del
and before 593 Discussions on Event ID 4689 Ask a question about this event 4689: A process has exited On https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=4689 this page Description of this event Field level details Examples Discuss this event Mini-seminars on this event Event 4689 documents when a process ends. When you start a program you are creating a "process" that stays open until the program exits. This process is identified by the Process ID:. You can use this event to tell event id how long the program ran by correlating it to the earlier 4688 with the same Process ID. Free Security Log Quick Reference Chart Description Fields in 4689 Subject: The user and logon session that the program ran under. Security ID: The SID of the account. Account Name: The account logon name. Account Domain: The domain event id 4689 or - in the case of local accounts - computer name. Logon ID is a semi-unique (unique between reboots) number that identifies the logon session. Logon ID allows you to correlate backwards to the logon event (4624) as well as with other events logged during the same logon session. Process Information: Process ID: is a semi-unique (unique between reboots) number that identifies the process. Process ID allows you to correlate other events logged during the same process. To determine when the program started look for a previous event4688 with the same Process ID. Process Name: The full path of the executable Exit Status: the exit code of the process - normally 0. Top 10 Windows Security Events to Monitor Examples of 4689 A process has exited. Subject: Security ID: WIN-R9H529RIO4Y\Administrator Account Name: Administrator Account Domain: WIN-R9H529RIO4Y Logon ID: 0x1fd23 Process Information: Process ID: 0xed0 Process Name: C:\Windows\System32\notepad.exe Exit Status: 0x0 Keep me up-to-date on the Windows Security