DAQmx version conflict preventing deployment

Hi all,
After installing LV2010 on both my dev machine and my RT target (rt desktop running Pharlap), I am unable to deploy DAQmx tasks to the target. The error message suggests that the deployment problem is related to a daqmx version conflict between the two systems, but looking at the software lists in Measurement and Automation Explorer (v4.7) both show components for DAQmx 9.5.1. I've reinstalled the daqmx components on both systems and have not gotten any different behavior. Anyone else having this problem or know of anything else to try?
Thanks,
tHa
CLAD

In grasping at straws I also noticed that the entries visible under the Software tree in MAX Explorer do not match those that appear in the dialog box when I select "Add/Remove" software. Maybe my system is using the wrong version of daqmx when it tries to deploy?
I've also been able to successfully run the tasks from the Explorer window.
CLAD

Similar Messages

Could not load file or assembly 'nationalinstruments.DAQmx, version= 9.2.40.82

Hello,
I have a problem in my software deployment, using NIDAQ 6518.
I get the following message when i start my software on the deployment computer:
could not load file or assembly 'nationalinstruments.DAQmx, version= 9.2.40.82
On my development computer, I don’t have this problem.
By opening Measurement studio on my development computer, i find, in the software tab:
- Measurement studio for VS2005.
- Measurement studio for VS2010.
As you can see on this picture(SEE ATTACHMNET).
But on the deployment computer when I install NIDAQ923-1. I find only
Measurement studio for VS2005.
As you can see on this picture (SEE ATTACHMNET).
Please help me to install properly the correct version that will allow me to have Measurement studio for VS2010.
NB:
-on the deployment computer installed NIDAQ923-1.
-I use Visual studio 2010 to programming
Attachments:
Measurement & Automation ATTACH1.png ‏87 KB
Measurement & Automation Attach2.png ‏125 KB

Hello there,
Are you just trying to run an executable on the deployment machine, an executable which you created in Measurement Studio 2010 on your development computer? I just want to confirm whether or not you have an installer for this deployment, or a just copying and pasting the executable you created. As long as you are using an executable, and not actually running Measurement studio, the version of Measurement Studio installed on the machine is irrelevant, since you are not using the development environment.
The message that you are getting, “could not load file or assembly nationalinstruments.DAQmx, version= 9.2.40.82”, means that you do not have the correct version of the NI-DAQmx drivers (NI-DAQmx 9.2.3) installed on the deployment machine. Your executable needs the same version of NI-DAQmx installed on the machine you are running it on, as the machine it was developed on. Currently you have DAQmx 9.3 installed on your deployment machine, and are using DAQmx 9.2.3 for development. This message also points out to me that you developed in the .NET Framework 4.0, so I would also make sure that you have that installed on the development machine as well.
So just to be clear, all you should have to do to get your executable to run, is make sure you have the same version of the NI-DAQmx drivers (9.2.3) installed as you developed with, and the correct version of the .NET Framework (v4.0).
Matthew R.
Applications Engineer
National Instruments

NI-DAQMX version Compatability

Is there a list that shows the newest NI-DAQMX version that will work with Labview 2009 SP1?
I am using 2009 SP1, and am converting an existing set-up with a SCB-68A and SCC-68 to run with a new PCIE 6323 card. The older MX version (4.6.2) does not have the SCB-68A, and doesn't appear to be setting up the 6323 properly, and the new MX version (9.7.5) that came with the card creates lost of conflicts.

ATPL wrote:
Is there a list that shows the newest NI-DAQMX version that will work with Labview 2009 SP1?
Yes there is:http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248
Looks like DAQmx 9.7 is the last version that will work with LabVIEW 2009.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Possible version conflict, sending purchase order to SUS in MM-SUS scenario

We are currently trying to get the MM-SUS scenario working. In this
scenario, we create a purchase order in the ERP/MM system. The
purchase order is then transferred into SUS via XI/PI.
After creating a purchase order in the MM system, the purchase order
reaches the SUS system, but then errors-out in the SUS system upon
posting. The specific error is paraphrased as follows:
No interface action for sender or receiver found (from Trace)
PARSE_APPLICATION_DATA
CX_ST_MATCH_ELEMENT
System expected the element http://sap.com/xi/SAPGlobal20/Global;
PurchaseOrderRequest
We suspect a version conflict. The SUS version is 7.01. The XI/PI
system is version 7.11.
Can you confirm or rule-out a version conflict?
The Integration Builder scenario we are using is Plan
Driven Procurement with Supplier Enablement.
We have tryed many variations in Integration Builder, but all
produce errors in SUS. The test tool in Integration Builder also shows errors
for certain message types. The message type ORDERS.ORDERS02
needed to be added manually, and did not come along with the scenario.
Edited by: Bill Guderian on Mar 19, 2010 4:53 PM

Any clue from here.
Note 936003 - ERS Invoice causes conversion error within SRM
When the SRM system attempts to process an ERS Invoice sent from the MM backend, a PARSE_APPLICATION_DATA CX_ST_DESERIALIZATION_ERROR fault is thrown.
Other terms
CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping
Reason and Prerequisites
This error will occur when the IDOC does not have a VPREI value; it is the result of an error within the divide logic of the XI mapping operation. This operation is performed within the XI system. A calculation of NETWR/MENGE is performed; however, the result is not properly formatted. As such, 72.30/10 produces a result of 7.2300002. This value is too long for the inbound SRM proxy and hence the error is thrown.
Solution
The solution to this problem is to add a FORMATNUM function within the XI mapping operation. This restricts the result to 2 decimal places, which adheres to the definition of the inbound proxy.
Step by step directions on how one implements the FORMATNUM function are as follows:
1. Log into the XI system with SAPGUI
2. Start the Integration Builder:Design tool (for steps on how to do this, review the steps below):
    a. Run transaction sxmb_ifr
    b. This will cause a browser to come up. Select the Integration Repository link
3. In the left pane, select the Objects tab
4. Navigate to the SAP SRM SERVER ' SAP SRM SERVER 5.0 ' http://sap.com/xi/SRM/SupplierEnablement/Global --> Mapping Objects --> Message Mappings folder
5. Double-click on MM2SUSInvoice
6. The right pane will display the mapping object
7. Select Edit mode
8. In the box that contains the output (Message Type: InvoiceRequest), navigate to InvoiceRequest ' Invoice ' Item ' Price ' NetUnitPrice
9. Double-click on the Amount element and you should see the mapping, represented graphically in the bottom pane
10. In the status line of the graphical editor, select Arithmetic from the list box:
11. To the right of the listbox, scroll until you see the FormatNum function
12. Click on FormatNum, which will cause the function to be added to the graphical editor. You may drag the box as desired
13. Select the connection that binds the if/then/else to the Amount box by grabbing the arrow within the input of the Amount
14. Release the drag of the connection while over the input to the FormatNum box. This will reassign the output of the if/then/else to the input of FormatNum
15. Create a connection between the output of the FormatNum box and the input of the Amount box. You accomplish this by clicking within the output and releasing within the input (respectively).
16. Save the modified mapping object
17. Activate the changes
    a. In the left pane, select the Change Lists tab
    b. Navigate to the Standard Change List entry
    c. Right-click the Standard Change List entry and select Activate
    d. Select only MM2SUSInvoice if more than one item is available, and press the Activate button
18. This will complete the required modification.

Version conflict in PI QA system

Hi All,
We are facing version conflict issue in QA system.
We transported a Mapping object from Dev to QA and after transporting it is giving Version conflict at QA.
This thing happen because some user has edited mapping program at QA level and activated .
We thought of transporting a deleted object first then the latest active version. But my doubt is that when we transport the same mapping program with same name PI will bring back object along with its history.
Can anyone having any idea about how to resolve this conflict.
Regards,
Navneet

Hi Ninu,
Thanks.
We activated the conflicting version from conflict tab and then transported the dummy changes from DEV to QA to verify it wont give version conflict any more.
it worked fine and conflicting version which we activated at QA considered as latest version for transport.
Regards,
Navneet

File Transport: Version conflict.

Hi,
I have a doubt on a particular scenario while transporting object from QA to PRD using File transport.
I have exported a tpz file say 1.tpz from QA with say the following objects
Obj_1(ver 1.0)
Obj_2(ver 1.0)
Obj_3(ver 1.0)
Now before this 1.tpz is imported in PRD few more changes happend to Obj_3 and I exported again a file say 2.tpz
Now this 2.tpz has only Obj_3(ver 2.0)
Now the basis has by mistake Imported this 2.tpz file before importing the 1.tpz file. SO in my PRD the object Obj_3 is existing with a advance version i.e 2.0
Now my doubt is can we Import 1.tpz now in PRD and then again import 2.tpz ?
I am having a feeling that we will definately get in version conflict. Even if I ignore the warning during transport and go ahead with this procedure of importing 1.tpz and then 2.tpz again, will it impact my scenarios.
I am lookign for a quick suggestions.
Regards,
Rahul.

Hi Rahul,
If you import V1 file first & later V2, it will not impact on your scenarion & you wil be able to see latest object in PRD.
But V2 is already imported so import of V1 may not be successful.
You may generate a new export if possible & transport this. It should include all object with their lastest version.
Regards
Sushil

Which DAQmx Version is sutiable for Labview 8.2.1

Hai Guys,
I am Thiyagu. I have one Doubt in DAQmx. If One year before my senior create One VI. The VI Labview Version 8.2.1. Lastweek running VI Harddisk was crased. I have only source code. I pasted that source code in another PC. I opened that source code It shows DAQmx Write file.VI was Missing. So i searced Daq file and I find it. So i Pasted that Vi in Source code It shows Labview 11 error. Currnt labview Version is 8.6 and DAQ version 8.8. So kindly tell me How to slove this issue and Which DAQmx Version is suitable for 8.2.1
Please do the needfull.
Thanks
Thanks
Thiyagarajan.S
WABCO Vehicle Control System

Any DAQmx should work, I use the latest with LV7.1. You can download it from ni.com or use the CDs supplied with your hardware.
The mistake you made was to copy the missing VIs. You need to run the DAQmx installer instead (after installing LV, so it can detect which LV versions to support).
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

XI 3.0 Version Conflict after SP 10 import

My XI 3.0 integration builder shows a version conflict for IDOC adapter meta data after we have implemented support package 10.
What needs to be done ?

Hi Peter,
We have this issue as well. not sure it is too much of an issue though.
Cheers
Colin

Version conflict while targeting a vi to RT engine

When i am targeting a vi to Labview RT engine the message "Version Conflicts between Host Labview and RT engines" is coming.
I am using a CFP-2100 and want to run a vi on it. (No PC should be connected with it)
After targetting how will i execute it on CFP? is it automatically executable?
Please reply me
--Alok Trivedi
Pune
-AL☼K

Thanx for replying me so soon.
I am still stucked with the problem.
I have Labview 7.0 installed on my computer and where i am making a vi which is to b loaded into CFP - 2100.
Here are other versions i am using.....
Field point VI manager 3.1.0
Field point Drivers 5.1.0
Data socket for Labview Real Time 4.2
Labview Real Time 7.1
NI-Irda RT 1.0.1
NI-Serial RT 2.5.4
NI-VISA 3.2
NI-Watchdog 2.1.2
When i switch the execution target to RT engine for remote device and enter the machine IP address it shows me "Version Conflict while targeting a VI to RT engine".
I talked to Rahul about this and he well told me how to repair version conflicts between Host machine and RT engine. I went to remote machine and by right clicking on "software" installed all the versions to remote machine according to the host machine.
the interesting thing is here it's not showing any version mismatch all the versions shown above are same as the host machine......but whenever i try to target the execution to RT engine it shows the version conflict.
now what all questionis running in my mind are :
1. Why the version conflict is occuring?
2. If I get succeed to targeting the execution of vi onto RT engine how would i install it to CFP, if i just copy and paste it via FTP how will it know what vi is to run? i think we'r missing some way to "install" the vi into CFP.
3 What is "RT Communication wizard for".......why it makes 3 other vi's....
4. what are the total ways to run a vi onto CFP
Waiting for your reply...
thanks again
-Alok Trivedi
Pune
-AL☼K

Version conflict between XE's ODP and VS2005/ODT's ODP

Suppose you've just built an application with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 which uses Oracle.DataAccess.dll version 2.102.2.20. You want to be able to run the application on a client machine that has an Oracle XE database installed locally. Perhaps you even require that the client machine runs the Oracle XE Client. Unfortunately, even with both there seems to be a version conflict regarding Oracle.DataAccess.dll. Can anyone say what are the best practices for such a situation?

Situation:
1) Oracle XE (database with/without client) installs with the following two files in the <ORACLEXE_SERVER_HOME>/BIN directory:
Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0)
OraOps10.dll v10.2.0.100 (for .NET Framework 1.0)
2) Applications built with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 use Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0).
3) The client machine will be missing the following two files vital to the application: Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0), OraOps10w.dll v2.102.2.20 (for .NET Framework 2.0). These two files can be found on the development machine in the <ORACLE_ODAC HOME>/odp.net/bin/2.x and <ORACLEODAC _HOME>/bin directories, respectively.
Action:
When installing the application on the client's machine, place copies of the two missing files into the client's <ORACLEXE_SERVER_HOME>/BIN directory, overwriting the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0).
Result:
The application performs as expected.
My immediate concern is that the client may object to replacing the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0). What are the best practices for such a situation?

Version conflict resolution failure - catch 22

Hi,
I have a situation where I am trying to delete a DIRECTORY object (a receiver determination for example), but when I attempt to activate the change list a version conflict is reported.
When I attempt to resolve the conflict through the editor, I always get a 'MERGE RELATION IS NULL' error and cannot resolve the conflict and therefore cannot delete the object.
I am using SP 13.
Any help will make me VERY happy !
Cheers,
Guy

Hi,
Use TCODE : SXMB_IFR then Exhange Infrastructure Browser Will Display then
GoTo--> Administration by using PISUPER or XISUPER ->select ID->Select Administration of Locks and Caches -> Select Lock Overview>Delete if ur userid is display.
Then Refresh Cache once.
Plz allot points if u satisfy with the answar....
With Regards,
Mahesh

How do I correct version conflicts between host and RT engine?

I was running LabVIEW RT7.0 on a host PC (WinXP) and PXI-8145 system. I installed LV7.1 and LVRT7.1 on the host. However, the software versions in MAX still report as 7.0
I would like to upgrade to 7.1 on my 8145-RT. I cannot run 7.1 on the host and target the 7.0 RT engine (results in version conflict). Version 7.0 is installed on C:, but 7.1 is installed on D: due to space.
How can I get MAX to recognize my latest version (which should allow my to download it to the PXI)?
Thanks.
Laine

Thank you for the response.
C:\RT Images contains only a single folder for NI-PAL
However, I backed it up and copied the RT Images folder from D:, but still the same effect (MAX thinks 7.0 is the latest LabVIEW version).
D:\RT Images\LabVIEW\7.0 contains subfolders and install scripts (e.g., 7002.rts)
D:\RT Images\LabVIEW\7.1 contains subfolders but no install scripts. Also, there are many fewer files in these subfolders than in the 7.0 folder. I'm worried about trying to manually install from the 7.1 folder.
Any other suggestions? Thanks.
Laine

Target fieldpoint connection failed due to version conflicts

I have set up a small network of fieldpoint (fp-2015) and laptop with Ethernet. Then, I have succesfully configured this fp with MAX and downloaded the iak file to it. Now, I want to target the labview RT of this fp. However, the the connection failed with following message "Version Conflicts between host labview and RT Engine". I'm using Labview 7.1 released in August.

It sounds like the FP-2015 that you have has an older version of software on it (probably LabVIEW 7.0). To upgrade the software on the FP-2015, first launch Measurement & Automation Explorer. Locate the FP-2015 under Remote Systems. Right click on the software item and select Install Software. This will allow you to install the new software image and upgrade the controller to LabVIEW 7.1. Note: You will need FieldPoint Explorer 4.1 which shipped with LabVIEW 7.1. If you have an older version of FieldPoint Explorer, it will not have the 7.1 image for the FieldPoint controller.
Regards,
Aaron

Version conflicts between host labview and RT engine

there is problem that i cannt switch target to feild point. It said that "version conflicts between host labview and RT engine" . But my labview is version 7.0 and the real time module is version 7.0 too. Anyone can give me hand? Thanks

Depending on your version of MAX, you should be able to change the version on the FP (in remote systems). If you can't do it in 3.0, try upgrading to 3.1 (you will have to search for it on the site). If that doesn't work, you can try resetting to factory default and then see if you can do this.
Another tip, which for some reason seems to help, is updating the OS\Run-Time Engine when windows is in safe mode.
Try these and see if they help.
BTW, as a tip for next time, you're more likely to get a good answer for something like this if you post in the FieldPoint board.
Try to take over the world!

Evaluation version for "Base Deployment Engine " available?

Hello,
we have one "Development-version" to develop testplans.
Now we are creating a cutom OPUI that calls the teststand-API. It works fine with the "Development-version".
Normally it should be enough to just install the "Base Deployment" to compile and use our custom OPUI.
The price is ~500EUR for the "Base Deployment"
Question is now:
Is there an evalution-download available to check if i can use our custom OPUI with the "Base deployment"?
I only find an evaluation-download for the full "Development-version"
Thanks

Deleting the license files will have the same effect as having an evaluation license, that's correct. Edited: Actually, deleting the license file will only trigger evaluation mode if the original evaluation license files are on the machine. This would be the case for a clean install, but may not be the case for OnlyOne's install. In that case, deleting the license files would just cause TestStand to not open.
However, my interpretation of the question (please correct me if I'm wrong, OnlyOne), is that he was wanting an eval version of base deployment so that he could confirm that his OI would work with a base deployment license. If that's the case, I think it's an equally accurate test to use an activated Base Deployment license.
Daniel E.
TestStand Product Support Engineer
National Instruments

DAQmx version conflict preventing deployment

Similar Messages

Maybe you are looking for