error 2147024891when call an ActiveX object

[fanl]

I have a problem when calling an ActiveX object. The 2147024891 error code shows up. See the attached screen shot. I can call another ActiveX object to logon the COM and obtain a logon handle. Then according to the manufacture, I should be able to call other objects with the logon handle as authentification. Unlike the case discribed in the following thread, my error happens to Labview 7.0 also. The demo program provided by the manufacture works OK and it is writen in C++. I feel it is a Labview issue as the way it calls an ActiveX object. Appreciated your help in advance.

http://forums.ni.com/ni/board/message?board.id=170&message.id=231095&query.id=15715#M231095

Leimin Fan

[CarlaU]

Hi Leimin Fan,

I think that this error 2147024891 is usually has to do with ActiveX DCOM permissions. The error stems from not having sufficient permissions to the client computer. In Windows XP, there is a specific setup for the ActiveX permissions that you will need to have. There is a great knowledge-base article that walks you through this setup. Also, check to make sure that you can ping the computer and that you have no firewall or antivirus software that could be blocking the connection. You could also check that your default COM properties have been setup for the user who is going to launch the program. These steps are also included in that knowledge-base article. Please let us know if this helps solve the problem!

Carla

[fanl]

Hi Carla,

Thanks for your reply. I am not using remote access here. Do I still need to set the DCOM? Also Labview 8.5 does not allow me to select a object list in the "show all creatable objects only" window for the setup of automation refnum. Is it due to DCOM setting/COM property? In step 3 of setup DCOM permissions from the knowledge base article, I should select Labview as my application name, right? I am stuck here so please help. Thanks.

[fanl]

Is there anyone who can access Applied Biosystems' mass spectrometers that run under Analyst 1.4.2? Can you please help me and test if you can the objects different from me?  The Analyst 1.4.2 has COM components called AAO (Analyst Access Objects). Right now with Labview 8.5 I can only call the AAOLib.OAAO_Startup object. Of course all other functions are not accessable. I want to see if this is my computer setting problem or Labview problem. Sofar I tryed three computers. All failed to select other objects. Thanks.

Leimin Fan

[CarlaU]

Hi Leimin Fan,

I would suggest that you go ahead and set up the ActiveX DCOM permissions. On step 3, you should select the name of the application that you created. For step 4 and 5, click on the properties icon (which is on the top menu bar). Another window will pop up and you will see the Location and the Identity tabs. Also, could you clarify which version of LabVIEW that you are using? In your last post, it says 8.5 but I think earlier you mentioned LabVIEW 7.0. Also, which operating system are you using? Also, have you looked at any of the LabVIEW examples using ActiveX found in the NI Example Finder to see how they have set up the block diagram? I hope this helps!

Carla

[tgif]

Hi CarlaU,

can you relink the knowledgebase url again please? it says I don't have permission to open the document.

Thank you!

Message Edited by tgif on 05-03-2008 10:26 PM

[CarlaU]

Hi tgif,

I think the article is now on the internal database only. However, I will post some information about setting up the DCOM settings for you.

You then want to verify that you have the following DCOM configuration settings on the server and the client.

On the Server Machine:

1. Go to the Start » Run and type dcomcnfg  
2. Double-click on Console Root » Component Services » Computers » My Computer
3. Right-click on My Computer and select Properties
4. Select the Default Properties tab
5. Check Enable Distributed COM on this computer
   •  Set Default Authentication Level to Connect
   •  Set Default Impersonation Level to Identify
6. Select the COM Security tab
   • For both Edit limits (Access Permissions and Launch and Activation Permissions), give Everyone access to both settings
7. Click OK
8. In the Component Services window, double-click on My Computer » DCOM Config
9. Right- click on the appropriate application from the list of Apps and select Properties
10. Select the Security Tab
11. Under Launch and Activation Permissions, choose Customize and click on Edit...
12. Click on Add... and enter Everyone. Click OK
13. Select Everyone from Group or user names
14. Check Remote Launch and Remote Activation from Permissions for Everyone. Click OK
15. Under Access Permissions, choose Customize and click on Edit...
16. Repeat steps 12 and 13
17. Check RemoteAccess from Permissions for Everyone and click OK
18. Under Configurations Permissions, choose Customize and click on Edit...
19. Repeat steps 12 and 13
20. Check Full Control and Read from Permissions for Everyone and click OK
21. Click on the Select Identity tab and choose the interactive user
22. Click on the Default Protocols tab and ensure Connection-oriented TCP/IP is selected

 On the Client machine:

1. Go to the Start » Run and type dcomcnfg  
2. Double-click on Console Root » Component Services » Computers » My Computer » DCOM Config
3. Right- click on the appropriate application from the list of Apps and select Properties
4. Select the Location tab and check Run Application on the following computer
5. Enter the machine name

I hope this helps!

[fanl]

This problem still not resolved. I have an NI tech service #1109771. After many rounds of dicussion, the sad suggestion was to use VB write ActiveX calls and wrap it to LV. That just stopped me to go any further. Anyway, CarlaU, can  you please check if the CAR #4EB98R6O has been resolved? Thanks.

[CarlaU]

Hi fanl,

I looked into the CAR and our R&D teams are still investigating this. Unfortunately, I do not know a time frame for when this will be fixed or in what version of LabVIEW this will be fixed in. The best thing to do would be to check back in with us in a bit. I hope this helps!