Trouble executing COM+ DLL

Folks,

here's the story:

We got 4 servers (O, T, A and P, all Windows 2000 Server). They are all
configured the same way (OS, patches, updates en further
(COM+)configuration).
There is a COM+-application defined using roles for security. IIS is
used as the webserver.
They are all running a COM+-application containing several DLLs
compiled with Delphi 5. We are now migrating to Delphi 2005.

After replacing the D5-DLL's with de D2005-version on the O-server,
everything went fine.

But after placing the same new DLL's on the T and the A servers, big
disappointment.
When calling the methods in the DLLs via ASP, DLLHOST hangs. The
process has to be killed to continue the website to work. Calling the
DLLs via an EXE is also not possible, the EXE hangs and has to be
killed.
There's no log or whatever, even the eventlog doesn't show any
(COM)-faults.

After placing back the D5-DLL's (bij dragging them into the
COM+-application) everything worked fine again, so you'd suppose it's
not a security-issue

I hear you say, get rid of D2005. But wait, there's more!

After removing the DLLs from the COM+-application (on A and T) and
registering the DLLs with regsvr32 everything works fine! But then, we
cannot use the COM+-security, so that's no option.
Also, creating a COM+application as 'library' (instead of 'server')
solves that problem (again, it's no option because of the lack of
security).

I've also made an 'empty' DLL (just one method returning a number) in
Delphi 5 and in Delphi 2005. The Delphi 5 version runs fine, the Delphi
2005 version shows the same problems described above.
And I've tried to compile the empty DLL with Delphi 2006. Same
problems.

So is it Delphi? Is it COM?

Anybody any idea what's the matter over here? Is there any way to debug
this problem?

Thanks in advance,
Dethmer Kupers

.

Relevant Pages

  • Re: Trouble executing COM+ DLL
    ... We got 4 servers. ... There is a COM+-application defined using roles for security. ... They are all running a COM+-application containing several DLLs ... compiled with Delphi 5. ...
    (microsoft.public.win32.programmer.ole)
  • Re: VB6, VB2005, or Something Else?
    ... Also you can't compile a DLL with RealBasic at the mean time, ... to 10 years, except for the DLLs. ... library) in Delphi is much more complete and robust than VB itself. ... Microsoft .NET Framework v1.1 Redistributable ...
    (microsoft.public.vb.general.discussion)
  • Re: .Net applications, not optimized for CPU at all?
    ... I mean apart from 'hello world' class of applications (which are comparable to the size of Delphi when using BPLs), the .Net EXE and DLL didn't strike me as being particularly lean at all compared to native versions. ... The .Net DLLs especially are huge, things like Tao.OpenGL, at 2 MB+, is about 10 times the size of the equivalent Delphi *DCU*, and even Microsoft-provided DLLs are huge for the amount of things they do, meaning it's not a programming mistake of non-microsofties that makes the DLLs big, f.i. ... IME .Net EXEs and DLLs size is in the same order of magnitude as their code size, just like for DCUs in Delphi, except that in native Delphi applications, the linker links those DCU into EXE/DLL, that are typically one order of magnitude smaller than their DCUs. ...
    (borland.public.delphi.non-technical)
  • Re: Rekursive Strukturen Parsen in Delphi
    ... kann man Calling-Konventionen etc. komplett vergessen, ... Es geht hier um die Benutzung von bestehenden DLLs, ... Delphi Interface Units genau um die exakte ABI der zugehörigen DLLs ... "The difference between fiction and reality? ...
    (de.comp.lang.delphi.misc)
  • Re: Refering to From of ActiveX DLL
    ... >> Personally I use Delphi for DLLs, ... >I don't know much about Delphi. ... IMO all programmers should have two languages ... 'MASM is a high level language' ...
    (microsoft.public.vb.general.discussion)