LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

network installation

I am trying to set up a network install of LabView 7 for Windows XP PC's. I followed the instructions on page 10 of the LabVIEW Release Notes.

I installed Labview 7 on COMPUTER-ONE, the server. I shared the National Instruments directory as COMPUTER-ONE\NI.

I created a shortcut on COMPUTER-TWO, the client, to point to "z:\Labview 7.0\labview.exe". I mapped Z: to COMPUTER-ONE\NI. I also added a "-pref c:\lvwork\labview.ini" switch to the shortcut. Using notepad, I created the c:\lvwork\labview.ini file.

When I try to launch Labview from COMPUTER-TWO, it launches briefly (less than 1 second) and immediately terminates.

What steps am I missing? Is there additional software that I need to install on COMPUTER-TWO?

Thanks!

Terry
0 Kudos
Message 1 of 7
(3,520 Views)
Are you logged on as an admin w/ the same user name/pw on both the client & server computers?
Also, are they NTFS or FAT file systems?
Sometimes the privaledge settings on NTFS systems can cause this effect, as it tries to use temp files on the server computer that only the admin has access to.


2006 Ultimate LabVIEW G-eek.

0 Kudos
Message 2 of 7
(3,520 Views)
Thanks for responding. I'm logged on as admin on both the client and the server. Both PC's have NTFS file systems. Share permissions are Full Control. NTFS permissions to the server share that has LabVIEW are full control.
0 Kudos
Message 3 of 7
(3,520 Views)
Does the labview.ini file on the client contain the path to the server before the pref:
z:\labview\labview.exe - pref c:\lvwork-labview.ini
I've never done this w/ LV 7, so I'm just looking at the ref doc, too. I'd also try it w/o the shortcut (just explore over to the server and open LV). If this works, remove the pref line from the shortcut (the ini file should handle this anyways). You can also try using the full path to the server, versus mapping it:
\\COMPUTER-ONE\C:\labview\labview.exe
That's about all I know.
G'luck


2006 Ultimate LabVIEW G-eek.

0 Kudos
Message 4 of 7
(3,520 Views)
Hi.

I'm having the same problem. Anyone have any luck with this?

Thanks,

Ben



Jonnie 5 wrote in message news:<506500000005000000160A0100-1042324653000@exchange.ni.com>...
> Does the labview.ini file on the client contain the path to the server
> before the pref:
> z:\labview\labview.exe - pref c:\lvwork-labview.ini
> I've never done this w/ LV 7, so I'm just looking at the ref doc, too.
> I'd also try it w/o the shortcut (just explore over to the server and
> open LV). If this works, remove the pref line from the shortcut (the
> ini file should handle this anyways). You can also try using the full
> path to the server, versus mapping it:
> \\COMPUTER-ONE\C:\labview\labview.exe
> That's about all I know.
> G'luck
0 Kudos
Message 5 of 7
(3,520 Views)
Hi,

I'm also having the same problem.
Is there a solution/workaround for this?

/Staffan
0 Kudos
Message 6 of 7
(3,520 Views)
You will need to have a multi-seat license agreement to enable this functionality. Running LabVIEW over a network is prohibited if you only have a single-seat license, as stated in the license agreement. Please contact your sales representative if you need to acquire a multi-seat license.

-Joseph DiGiovanni
Applications Engineer
0 Kudos
Message 7 of 7
(3,520 Views)