LabView2013 DCOM Problem

[BadLuckMan]

Hello again,

one more question regarding LabView2013 and DCOM.

 

I am now able to start a activex-enabled labview2013 application on a remote PC, get a VI reference and run the VI without errors.

The only problem is that there is no frontpanel shown on the remote PC. I only see the application in the process list of task manager.

 

Does anyone know of a possibility to let Labview2013 open the frontpanel when the application is started from remote?

 

Thanks for any help,

Ralf

Sorry,

forgot to mention that I have tried ShowFPOnCall = true and OpenFrontPanel(true) from remote without success.

 

Thanks,

Ralf

[Rolf Kalbermatter]

Hello again,

one more question regarding LabView2013 and DCOM.

 

I am now able to start a activex-enabled labview2013 application on a remote PC, get a VI reference and run the VI without errors.

The only problem is that there is no frontpanel shown on the remote PC. I only see the application in the process list of task manager.

 

Does anyone know of a possibility to let Labview2013 open the frontpanel when the application is started from remote?

 

Thanks for any help,

Ralf

Sorry,

forgot to mention that I have tried ShowFPOnCall = true and OpenFrontPanel(true) from remote without success.

 

Thanks,

Ralf

 

You are logged in on that remote computer with an unlocked user session? And connecting to the LabVIEW instance over DCOM under this account? Maybe DCOM executes the LabVIEW process under a different account that has no desktop session available!

[BadLuckMan]

Guess you are right.

I saw the process in task manager only when I checked to show processes of all users.

 

It's a bit strange because both PCs were in the same domain and the identical user was logged in on both PCs.

 

I can not reproduce the behavior in the moment.

Thought first it might have something to do with labview development system or only labview runtime on the target PC.

 

Thanks for your help,

Ralf

[Rolf Kalbermatter]

Guess you are right.

I saw the process in task manager only when I checked to show processes of all users.

 

It's a bit strange because both PCs were in the same domain and the identical user was logged in on both PCs.

 

I can not reproduce the behavior in the moment.

Thought first it might have something to do with labview development system or only labview runtime on the target PC.

 

Thanks for your help,

Ralf

 

 

No that is definitely some DCOM issue. It very much depends how you setup the configuration of the DCOM authorization. It's a pain to get it to work at all already and therefore I actually always avoid this. Usually create remote apps that get installed under a specific account as service and then connect to them over TCP. Initially more work to do, but eventually easier to manage, as you don't have to fight DCOM (and with some customers also their entire IT department).

[Tim_S]

(and with some customers also their entire IT department).

Amen.