quote:

---

> We are having problems with one of our intranet iss servers.
> The server is Windows NT4 server+service pack 6a, IIS4.0, Site server
> 3.0+service pack4
> The problem we are having is that the below services stop every couple of
> days on their own:
> -WWW
> -Microsoft SMTP
> -Site Server LDAP
>
> When they go down we get the below in our Event Log:
>
> ----------------------------------
>
> Type: Error
> Source: Transaction Server
> Category: Context Wrapper
> Event: 4104
>
> An object call caused an exception. (IID:
> {51372AEF-CAE7-11CF-BE81-00AA00A2FA25}) (Method: 3) (Microsoft

---

quote:

---

> Server Internals Information: File:

---

quote:

---

> Line: 889) (Exception: C0000005) (Address: 0x72705c74)
> + 0x723A5C40
> asp + 0x263AC
> asp + 0x2070B
> asp + 0x206A7
> asp + 0x208EC
> asp!TerminateExtension + 0x65AD
> asp + 0x29845
> mtxex!MTSCreateActivity + 0x1F3C
> mtxex!MTSCreateActivity + 0xF3E
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> ----------------------------------
>
> I have looked at http://www.eventid.net/display.asp?eventid=4104&source=

---

quote:

---

> the recommended MS KB Q's - Q291365 , Q262187 , Q267993 , Q228495
> but I have yet to find an answer.
>
> I did find this article in the MS KB though,
>

---

quote:

---

>
>
> Unhandled Exceptions
> These errors occur when a component performs an illegal action, and does

---

quote:

---

> handle the exception. MTS traps this error. When the proper symbols are
> installed, a call stack is available at the bottom of the event log
> description. Review the call stack to determine the cause of the

---

quote:

---

> Eventlog Entry
>
>
> An object call caused an exception.
> (IID:{51372AEF-CAE7-11CF-BE81-00AA00A2FA25}) (Method: 3) (Microsoft
> Transaction Server Internals Information: File:
> d:\viper\src\runtime\mtxex\activity.cpp, Line: 889) (Exception: C0000005)
> (Address: 0x78001799)
> This error occurs when a component registered in MTS performed an illegal
> action (often an access violation). MTS traps the exception, and then

---

quote:

---

> down the process.
> Eventlog Entry
>
>
> An object call caused an exception. (Package: Crash) (ProgId:
> Crash.Crasher.1) (CLSID: {157732AE-16D7-11D4-8801-00C04FB9CD9A})

---

quote:

---

> ICrasher) (IID: {157732AD-16D7-11D4-8801-00C04FB9CD9A}) (Method: 7)
> (Microsoft Transaction Server Internals Information: File:
> i:\viper\src\runtime\cw\cwlib.cpp, Line: 935) (Exception: C0000094)
> (Address: 0x01201cd1)
> Crash + 0x1CD1
> mtxex!ContextWrapper::OnCall(unsigned int,void * const,unsigned long *
> const) + 0x1C7
> mtxex!CWList::VbStopDebugging(void) + 0x281C
> RPCRT4!NdrStubCall2 + 0x4E0
> RPCRT4!NdrClearOutParameters + 0x5B2
> OLEAUT32!LHashValOfNameSysA + 0x5BDD
>
> This error indicates that a component registered in MTS performed an

---

quote:

---

> operation (an access violation) during a method call. MTS traps the
> exception, and then brings down the process. The Prog ID of the component

---

quote:

---

> included in the event log, as are the name of the package, the interface,
> and the call stack.
>
>
> Has anyone else come across this that can offer some advice or a fix or

---

quote:

---

> any MS MVP's offer their opinions/words of wisdom? Thanks!!
>
>

---

quote:

---

> Search google for "mtxex". I just found a bunch of other posts with the
> same problem from about 4 years ago. One person's response/resolution was
> to change from using Access to SQL server.
>
>
>
> --
>
>
> - Jake
> www.nthelp.org
> Microsoft MVP - IIS
>
> "brandon" <brandon@NOSPAMhello.com> wrote in message
> news:OOIDFQ84DHA.2524@TK2MSFTNGP11.phx.gbl...
of[QUOTE][color=darkred]
> Transaction
> i:\viper\src\runtime\mtxex\activity.cpp,
> and
>

---

quote:

---

> not
> exception.
C0000005)[QUOTE][color=darkred]
illegal[QUOTE][color=darkred]
> brings
> (Interface:
> illegal
component[QUOTE][color=darkred]
> is
interface,[QUOTE][color=darkred]
> can
>
>
>

---