Write Error on Shared Folder with LabView in Windows XP

[mmnw]

I'm using VirtualBox 2.0.2 on Mac OS X 10.5.5 with a Windows XP SP3 guest and GuestAdditions 2.0.2.

I ran into a problem with the shared folders feature when using National Instruments LabView (Version 7.1 and Version 8.5). I am able to open and edit files located on a shared folder drive. But when I try to save the file (overwriting the original) I get an ominous LabView Error Code 48, saying the file can not be saved, because temporary files could not be moved to the destination folder. Still, the original file was modified and is indeed corrupt and can not be opened anymore.

I could not reproduce this behaviour with any other program (tried Notepad, Word and Corel Draw). Also LabView works fine on other Network Drives, i.e. a samba share.

On the side, what does work is to use the "Save as" feature and save in a new file. So the problem obviously goes back to overwriting an existing file.

Has anyone else experienced this problem, perhaps with a different application? Is there any solution known? I couldn't find anything on the forums or with the tickets.

As a temporary workaround I either use save as, which is very impracticable with LabView, or work on a smb share of my host, which I don't want to use because I don't want to activate samba on my Mac OS X host.

[spicedHam]

It sounds like your problem might be related to bug 1870. http://www.virtualbox.org/ticket/1870

The title of the defect says it was fixed, but it was reopened. If LabView is copying a directory structure from a temporary location, this might be why it is failing. In some cases, the Windows guest additions have problems making nested directories.

[PaulHarfas]

Hi.
I am having the exact same problem as mmnw with LabView 8.6 in an XP Pro guest, under an Ubuntu 9.04 host. ( was the same in 8.10 however). I haven`t yet found any workarounds, except from working on the guest`s HDD ... VBox 2.2.2 is just out, maybe this will fix this issue.
If anyone has similar experience with LabView under VBox, or maybe found a workaround to this issue, please share.
Paul.

[cpschnuffel]

Hi there,
I have exactly the same problems described above with LabVIEW 7.0 and LabVIEW 7.1, but NOT with LabVIEW 6.1. I tested it with a W2K guest and an XP guest under XP as host, using VirtualBox 3.2.8, both with the same behaviour. I didn't test this with newer versions of LabVIEW until now.

Here's the exact error message LabVIEW produces:

LabVIEW: File permission error

VI '<VI-Name>' could not be saved!!
LabVIEW Save error code 48: Could not move temporary file to destination.

Do we have a chance that this old error ticket is cashed in the near future?

Regards from Berlin/Germany

cpschnuffel

[cpschnuffel]

Hi there,
a possible workaround for this problem is NOT to use the shared folder directly but to create a network share (for this you have to use network bridging).
Example: One of my shared folders is the D:\ drive of my host PC. To avoid this error I create a network share for this drive D:\ (e.g. named "D") and perform network access from the guest PC (via \\<IP Address>\D\). This works without any problems!

Regards

cpschnuffel

[dazur]

Hi cpschnuffel,
Thanks to your suggestions I managed to get this work, too. I explained my steps shortly on 2nd page of this NI forum article about Labview in Virtualbox: http://decibel.ni.com/content/thread/64 ... 0&tstart=0

[Asper]

Hi Folk,
I am using VirtualBox 4.0.4 on a Windows XP SP3 host with a Windows XP SP3 guest where I have installed LabVIEW 2010 SP1.
I am experiencing a similar problem when I try to save, from the LabView interface, on a shared folder.

I can successfully save individual files that belong to the LabVIEW project, but I can not save the file of the LabVIEW project itself.
When I try to save the LabVIEW project file, I get the following warning and the file is corrupted:

LabVIEW: File permission error. You do not have the correct permission for the file.

Cannot save project "project_name.lvproj"
LabVIEW Save error code 44: Could not move temporary file to destination.

Please note that the LabVIEW error code is now 44.

The workaround proposed by cpschnuffel works fine.
Regards,
Asper

[cpschnuffel]

Hi there,
a small update: Network access as described above is only possible if you have an active network connection; otherwise network bridging doesn't work. On the road with your laptop and without a WLAN connection you'll be in trouble.

A solution is to use a second virtual network adapter in host-only mode. Please take care that the "VirtualBox Host-Only Network" adapter on your host and the second network adapter on your guest share the same IP range (e.g. 192.168.56.1 and 192.168.56.2).

It might be necessary to disable this second network adapter on your guest temporarily if you have another network connection (e.g. WLAN); otherwise there are two concurrent ways to access your host from your guest (via bridging using the WLAN adapter, and via host-only adapter), and Windows doesn't like this at all !

Regards

cpschnuffel