# EntireX 6.1.1.0 via .Net Managed Code

**URL:** <https://techcommunity.softwareag.com/t/entirex-6-1-1-0-via-net-managed-code/59299>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [May 6, 2005, 6:44pm UTC](https://techcommunity.softwareag.com/t/entirex-6-1-1-0-via-net-managed-code/59299 "2005-05-06T18:44:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![W1ld0ne](https://avatars.discourse-cdn.com/v4/letter/w/9f8e36/32.png) [@W1ld0ne](https://techcommunity.softwareag.com/u/W1ld0ne)\
**Post date:** [May 6, 2005, 6:44pm UTC](https://techcommunity.softwareag.com/t/entirex-6-1-1-0-via-net-managed-code/59299/1 "2005-05-06T18:44:41Z")

</div>

We have an [ASP.Net](http://ASP.Net) application that communicates with EntireX (to Natural) via VB6 COM+ components. (We obviously reference dll generated by EntireX Workbench from the pda’s). I have rewritten one of these VB6 COM+ components into a VC#.Net COM+ Managed component. This object works perfectly in Development, test and even production. As the load picks up on this new .Net COM+ object, some strange in interesting errors start occurring or errors on the system occur more often.

Errors include our favorite:  
System.Runtime.InteropServices.COMException: Catastrophic failure  
Followed very closely by:  
System.Runtime.InteropServices.COMException: Error: 0215 0148 EntireX Broker not active

These errors occur a couple of times until eventually we get:  
System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown

In the original development documentation, the original developers said that they built the COM+ components in VB6 because EntireX could not handle .Net Managed code.

:?: Can anyone point me towards some documentation or other website/page that states this more clearly and possibly the reason for it. If anyone else has any other ideas, I’m real open for any suggestions at this stage.

Thanks in Advance  
David

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [May 9, 2005, 6:19pm UTC](https://techcommunity.softwareag.com/t/entirex-6-1-1-0-via-net-managed-code/59299/2 "2005-05-09T18:19:31Z")

</div>

Hi David,

We haven’t see this error so far. A possible reason for these errors could be a memory leak or threading issues.

In case you are using 6.1.1.0 on Windows I suggest to upgrade to a more recent version of EntireX.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:39pm UTC](https://techcommunity.softwareag.com/t/entirex-6-1-1-0-via-net-managed-code/59299/3 "2021-04-02T14:39:45Z")

</div>