[DUG] Com Server registration in Win 2003 SP2

[staff]

I am (still) working with D6 on a program that provides a COM/OLE services on windows clients, windows networks. The program allows VB code in MS Word and other programs to call these com services in my D6 executable. Typically the services get data from a Firebird DB and pass it to the requestors.

The program can register its COM interfaces when it first runs or by running it with the /regserver command line option.
It registers OK in all MS operating systems win9x, win2000, XP, win 2003, win 2003 SP1, (but not Win 2003 SP2) and Vista (once we use the "real admin" logon account). I have verified its registration works on each OS mentioned in actual sites and in my test setup. I have verified the registration is only partial in Win 2003 SP2. The com interfaces appear in the registry and they are removed when I run the program with command line /unregserver. Using TREGSRV does not help.

I repeat that Win 2003 SP1 and below is OK and Win 2003 SP2 gives me this problem.

The dot (myfile.dot) file used when users are running MS Word as part of the application, when on Win 2003 SP2, is failing to compile.  The VB Editor tissues the error "Compile error \n Error in Loading DLL" and points to an object referencing a servive provided by my program. When other programs ask for com services they are not provided. Yet when I edit this code in the VB Editor the code completion feature knows about my type library and presents options from my type library. So my type library seems to have been registered OK.

This appears to be a Win 2003 SP2 bug. But, as the program is a Delphi 6 product I am hoping someone here has some insights for me. We need the program running on Win 2003 where it is used as a terminal server.

Insights will be welcome.
Thanks,
Russell Belding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.adventureeducation.co.nz/pipermail/delphi/attachments/20071103/6e02dc63/attachment.html