COM+ in Windows 2003

Apparently, there are some major bugs in COM+ in Windows 2003.  Not only does the application that I support and maintain (somebody else wrote it), but I just found out this week that another application that I was involved with writing that uses COM+ has problems.  Both apps ran on Windows 2000, but under Windows 2003, they both seem to have problems.  In talking to Microsoft Support, I am thinking the problem is COM+.  There seem to be too many issues listed in the Support Knowledge Base that require a call to Support for a Hotfix for my taste.

http://morewally.com/cs/blogs/wallym/archive/2006/06/21/80.aspx

1 Comment

  • I have noticed some issues with Win2k3 com+ 1.5, and I'm wondering if you have this problem:
    Using classic asp to call a .net assembly registered in COM that inherits EnterpriseServices.ServicedComponent. Activate method fires appropriately, but when "Set obj = nothing" is called on the object (obj), the DeActivate method never fires.
    I'm not finding much help on the MSDN forums and newsgroups on this. Oh, yeah, it all works fine in Win2k.

    If you did have the problem, what did you do to fix it?

    Thanks,
    Ward Delcomyn

Comments have been disabled for this content.