ttene1.5524949174526318E12 asked a question.
Costing COM+ Application fails!
Hello,
This section is a part of probably trying to cost a COM+DLL.
The setup terminates.
For god sake, What does that mean???
MSI (s) (AC:00) [10:39:32:553]: Leaked MSIHANDLE (4726) of type 790531 for thread 1020
MSI (s) (AC:00) [10:39:32:553]: Note: 1: 2769 2: ISComponentServiceCosting 3: 1
DEBUG: Error 2769: Custom Action ISComponentServiceCosting did not close 1 MSIHANDLEs.
Internal Error 2769. ISComponentServiceCosting, 1
Action ended 10:39:32: ISComponentServiceCosting. Return value 3.
Thanks...
When you want to "import" the com+ components from the windows component services manager, you need first to build manualy the applications and then add the the components.
The problem happened because I added one component (dll) not from the place where it should have been installed to on the destination machine, but I added it from the place I hold the files to be copied and installed in the destination machine.
For example:
If I hold the files on c:\setup files, but the specific dll should be installed to c:\my components on the destination machine, I should add it on my(!) pc from c:\my components to the components services apllication I built first, and only then perform "refresh from system" in the "component services" manager in the DevStudio.
Hope it was clear!