I Need to call an exe using ActiveX/DCOM on a Windows Server 2003 Machine HOW?

[rdewey]

I have been getting an error every time I attempt to run an executable remotely using ActiveX / DCOM. The error is -2147023174, The RPC server is unavailable, The application is currently working with a Windows NT4 server without any problems at all. When we apply the same settings to the Windows Server 2003 machine, we continue to receive the same error listed above. I have followed the postings that direct me to update the security settins and select the interactive user option, however there has been no success.

Any advice?

[P. Jack]

What are the applications that you are trying to connect to when you are using the ActiveX?

This error appears because the activeX property/method you are using is not available on the machine (or network) where you are trying to run your "executable VI".

Basically, this technology's concept is to re-use, but how will it re-use functions that does not exist locally. Try to verify the location of the server of your ActiveX's properties and methods. When working locally, try to verify if the server application is still available in your local machine. You have mentioned that you are running an "executable remotely", is you VI, when executed in a remote location, knows how to contact the applications in the server?

A good configuration of your Automation Open function will do the trick.

http://zone.ni.com/reference/en-XX/help/lv/71/lvcomm/Automation_Open/

If possible, can you post your code? I'll try to see.

[rdewey]

 The file I use is attached, however I believe I have determined one small issue. If I compile the attached vi. and move it to the server it will call the application locally. In other words, the app will be called on the local server when the code attached is compiled. I have configured the default security per a couple of posts on this topic, and have modified the DCOM settings for the interactive user. The same code attached does work for another server on the same network that runs Windows NT 4.0. The other machine ( the one I cannot call Name.exe from remotely) has windows server 2003 enterprise edition. I believe the code is simple and pretty much correct, however I seem to be having some problems with the Win server 2003 enterprise security. Please evrify that this code should work (open an exe called Name.exe, and return the value of a control "IP Dot". Have you seen any issues with Windows XP or Server 2003 Enterprise, that may cause DCOM communication issues with the sample code I have provided?