From: CarlaU on
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:

- Go to the Start � Run and type dcomcnfg  
- Double-click on Console Root � Component Services � Computers � My Computer
- Right-click on My Computer and select Properties
- Select the Default Properties tab
- Check Enable Distributed COM on this computer

-  Set Default Authentication Level to Connect
-  Set Default Impersonation Level to Identify

- Select the COM Security tab

- For both Edit limits (Access Permissions and Launch and Activation Permissions), give Everyone access to both settings

- Click OK
- In the Component Services window, double-click on My Computer � DCOM Config
- Right- click on the appropriate application from the list of Apps and select Properties
- Select the Security Tab
- Under Launch and Activation Permissions, choose Customize and click on Edit...
- Click on Add... and enter Everyone. Click OK
- Select Everyone from Group or user names
- Check Remote Launch and Remote Activation from Permissions for Everyone. Click OK
- Under Access Permissions, choose Customize and click on Edit...
- Repeat steps 12 and 13
- Check RemoteAccess from Permissions for Everyone and click OK
- Under Configurations Permissions, choose Customize and click on Edit...
- Repeat steps 12 and 13
- Check Full Control and Read from Permissions for Everyone and click OK
- Click on the Select Identity tab and choose the interactive user
- Click on the Default Protocols tab and ensure Connection-oriented TCP/IP is selected

 On the Client machine:

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

I hope this helps!
From: fanl on
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.
From: CarlaU on
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!