accessing remote front panel in projected VI

[GabbyG]

Hello

I evaluate possiblities to provide user interfaces over a LAN.

One option would be Remote Panels (Using web-browsers has been set aside).

This is done with

Labview 2011 professional

PC1: Windows XP Professional with Kasperky IS; PC2: Windows 7 Professional with standard MS basic protection (both 32 bit)

Network: Windows Workgroup.

Direction: Server Win7; Client XP

Starting with Example "Remote Panel Methods" worked after enabeling port 8000 as well on client machine. (Kaspersky on XP would block the return path.)

Continuing to expand the example I moved it into a project and encountered a problem.

I am aware of:

To specify a VI that is part of a LabVIEW project, you must include the project name, the project library, and the target in the path of the VI, when applicable. For example, if MyVI.vi resides in a project called MyProject.lvproj under target My Computer, enter the VI name as MyProject.lvproj/My Computer/MyVI.vi. If the VI resides in a project library called MyLibrary, also include the project library in the path, as in MyProject.lvproj/My Computer/MyLibrary.lvlib:MyVI.vi. If the VI is not in a project or project library, you can enter the VI name without any additional information.

When the Win7 is running from inside a project  I will get error

Client does not have access to specified VI 

although programatically reading back the list of valid VIs shows the VI is in the list.

Disabeling the Windows firewall temporarilly has not helped.

Moving the project to XP and running the client on WIN7 does work.

Seaching the internet I found a similar report in a German Labviewforum but with no answer to it.

I think this cannot be an uncommon problem. So some hint would be helpfulp.

Gabi

[BRennhofer]

Its confusing

it is not a reproducible error. So I have no exact idea why do you get this issue.
You can try to check all Win7 firewall settings. All Ni Program have to check and also the settings in which area they are. See picture below.

i hope one of this two step can help you

[GabbyG]

Thank you for your response.

Unfortunatly none of your hints matched.

Labview 2011 as well as the NI Webserver are enabled in the firewall.

The link did not help any further as well. 

The amazing point is that where others fail, it works fine for me. An executable built out the RemotePanel frontend runs perfectly..

The client errors differ if you use the syntax xxx/yyy/server.vi or server.vi.If you omit the slashes you get the error "not loaded", if you have the slashes you get the error "no permission". Someone must parse the connection for / but not be able to locate the open project.

Two more additions to the surrounding parameters.

1. Both Window installations are German. The LabVIEW (2011 SP1) is English.

2. On the Win7 is also an installation of Labview 2012 

I may escalate the issue to NI München. Do you know if they have access to the material posted so far ?

Thanks

Gabi 

[BRennhofer]

Hi Gabi

I take a look to youre File.

I'm an application engineers in Munich.

[Julien_De_Freitas]

Hi Gabi,

I had a look at your post in the forum.

First, thank you for using the National Instruments discussion forum.

I just heard a custumer having the same problem accessing a remote Panel. He is using at the moment Kaspersky Internet 2012.

Could you try to disable the anti-virus?

Let me know if it works better.

Regards,

[GabbyG]

Salut Julien

Like in the original post described, Kasperki did block the return path, but that could be changed.

In general the problem came from different pathes for the application when the panel to access is still residing in a development environment. 

The issue was not solved and I gave up since another solution was used for the communication.

Sorry I can not help you any further.

Gabi