Cannot resolve conflicts in LV 2009.

[poethomer]

I have been developing a project on 2 different computers, one at my office and one on the test system itself (PXI chassis computer). I copied a project from my office computer over to the test system and conflicts appeared. There are two files named MNU.DIR. These are not VIs, they are dependencies. The resolve conflicts tools in the project explorer are not available. They are grayed out.

I cannot rename either of these files from within the project explorer (again that oppotion is not available) and if rename either of them in Windows Explorer then LV complians they are missing. There is no option to select the file found by the project.

Right clicking on either file and selecting Find>Callers, results in "no callers" for both files.

I have read through the help files on how to resolve conflicts and none of the options presented seem applicable. Any suggestions would be appreciated.

[Nick-C]

Can you give more information about how you moved the project to the test system.The article linked below describes how we recommend moving LabVIEW projects between systems.

http://digital.ni.com/public.nsf/allkb/166ECBD0AB87C320862571080082AA0F?OpenDocument

I would also recommend trying a mass compile of the project on the test system, this may help to resolve the missing dependency problems you are seeing.

http://digital.ni.com/public.nsf/allkb/654877E62A97B72986256C95006F9B24

Hope this information is helpful.

-Nick-

[poethomer]

I simply copied the project files from one computer to another. This is the first time I've ever encountered this problem, but it is also the first time I've ever had the development of a project spread over two machines. I've always worked on a single machine for development and then distrubuted executables from there. I do not own one of these machines.

My problem is not that some dependencies are not there. The problem is that multiple dependencies exist with the same name. MNU.DIR

[Nick-C]

I would recommend creating a zip file of the project as described in one of my links in the previous post. Then move this whole zip file to the second machine (where you are experiencing dependency problems). If you simply see duplicates of the dependent files have you tried removing the duplicate from the project?

-Nick-

[P@Anand]

The .mnu files is due to some of the modules in LabVIEW is missing in the computer where you have conflicts (I guess). Just install all the modules that you had in the development computer.  Right click the .mnu file and check whether you have an option called "why this file in dependency" if yes check it why else install the modules whatever you had in your development PC.

[poethomer]

I've been working to resolve this problem for a while, but it persists. The situation is this... I have installed an Agilent provided driver for the E364x series of DC power supplies. This driver was installed on two machines, the development machine (running Windows 7) and the destination machine (NI PXI running XP). The project was built using custom libraries as extensively as possible. I copied the project by zipping the entire project on the development machine and then unzipping it on the destination machine. There are no conflicts listed when the VIs are opened on the development machine but conflicts pop up on the destination machine. The conflict is a file called DIR.mnu in the agilent driver library and a file of the same name in the NI Signal processessing folder of labview 2009. This does not appear to be an issue with copying the projects. It seems to be an issue that is specific to the destination machine (again, an NI PXI-8110 running XP). I should mention that I have successfully performed a Mass Compile on both machines and neither results in any errors of problems. The project mass compiles cleanly on both machines. I do not get the conflict notice until i attempt to open a VI within the project that makes use of the E364x driver library. Any suggestions would be great!

[poethomer]

Here are the paths for the two conflicting files. There is only one difference in the paths on the two machines. LV 2009 exists in the (x86) version of the "Program Files" directory on the development machine and on the destination machine there is only one "Program Files" directory. Could this be part of the problem. Is the destination machine searching for the drivers and finding conflicts because the development machine has the directories listed differently?

Destination machine

C:\Program Files\National Instruments\LabVIEW 2009\menus\Categories\Signal Processing\dir.mnu

C:\Program Files\National Instruments\LabVIEW 2009\instr.lib\Agilent 34401\Public\DIR.mnu

Development Machine

C:\Program Files (x86)\National Instruments\LabVIEW 2009\menus\Categories\Signal Processing\dir.mnu

C:\Program Files (x86)\National Instruments\LabVIEW 2009\instr.lib\Agilent 34401\Public\DIR.mnu

[Nick-C]

Can you post a screen shot of the error that you are experiencing? Any error codes that it displays, in addition the exact text the error displays would be helpful in narrowing down how to resolve the problem. Thanks!

-Nick-

[poethomer]

Here is a screen shot of the conflict. I hope this helps. This apprears whenever I open a VI that uses any of the E364x library components. Just to reiterate, this only happens on the NI PXI chassis computer.

Thanks!

[nathand]

I don't know if this is of any help to you, but I've been seeing a similar warning in a LabVIEW 2009 project recently.  I never actually see the conflict in the project, though.  When I open a VI in the project I get a warning about a dependency conflict from the Signal Processing dir.mnu file, but when I click ignore, the VI opens and no conflict is listed in the project explorer.  As far as I can tell the problem is related to loading a DLL compiled in LabVIEW (yes this is silly, but we share that DLL with some non-LabVIEW code and want to make sure the core code, in the DLL, is the same on all systems).