When running an application we developed on The server, we will randomly see this error

Any idea what could be causing this?  The application we wrote is a re-entrant com DLL.

Do you actually have UTILS.lbr.dll in C:\\Windows\\system32?

Micro Focus Server 5.1 keeps all of its binary files in C:\\Program Files (x86)\\Micro Focus\\Server 5.1\\Bin, and none of them i called UTILS.lbr.dll. There is one called UTILS.lbr.

What happens when you remove or rename UTILS.lbr.dll?

---

 When running an application we developed on The server, we will randomly see this error

Any idea what could be causing this?  The application we wrote is a re-entrant com DLL.

I am actually thinking it may be a memory leak as we are also seeing DLLHost errors , followed closely behind by a comm Surrogate error. We have not tried copying and renaming the utils.lbr as yet.

---

 When running an application we developed on The server, we will randomly see this error

Any idea what could be causing this?  The application we wrote is a re-entrant com DLL.

You state that the error is random. At what point do you experience the error? Is it when the COM server is first instantiated or does it process for awhile and then get the error when perhaps a certain program is called? Does it occur when a certain number of threads are active, etc?

Like Fano said, there should be no file called UTILS.lbr.dll. If you do have a file with that name and you copied it to the System32 folder to perhaps alleviate a different problem with the application not finding UTILS.lbr, you should remove it and ensure that the PATH is set to find the correct UTIL.LBR file in the bin folder of the Server product. Frequently when people copy executable files or .dlls to the System32 folder they forget to update these when the Server product is updated and the files get out of sync as installing an update will not automatically update copied files.

---

 When running an application we developed on The server, we will randomly see this error

Any idea what could be causing this?  The application we wrote is a re-entrant com DLL.

There is no file by that name on the system. The Com object is started and has processed over 8,000 transactions without any errors or shutdown. The transactions do not seem to be the issue as I have run the same exact ones back through it up to the crash and it continues after that without fault.

---