Hi,
I think the issue is the path building, and the different ways labview returns paths in a VI and a exe.
I recommend that you start with the Launch DS Server if Local URL VI. Add two path indicators to the diagram. One that shows what is returned in the VI Lib path constant, and another after the build path primative. Save the VI under a different name, and outside of VI lib, and then build this test VI into an exe.
I think that you will see the dynamic path that is built doesn't point to the VI (<vi lib root>\Platform\dataskt.llb\DataSocket Server Control.vi).
If this is the case, you can physically get the vi from the dataskt lib yourself, and add it to your main app before you built it into an exe. Another option is to use System Exec (I think this is the way it was done in older versions of LV?). You can test the system exec method (on windows) by doing Start >> Run >> "C:\Program Files\National Instruments\DataSocket\cwdss.exe" ( igot this path by browsing to the DSS, right clicking and selecting Properties) >> then press enter. If the DSS starts, you're good. This is also a good test to make sure you have installed the server onto the target machine properly (as long as the target is a windows box...)
Let me know if you have any questions.
J
