Erreur -19050 lors de la compilation avec Deployment Utility/TestStand

Bonjour à tous,
Je souhaite créer un exécutable incluant des séquences TestStand avec des VIs Labview. Je suis tombé sur l'outil Deployment Utility qui a l'air de correspondre à ce que je souhaite faire.
J'ai donc essayer de construire un installateur avec cet outils qui inclut mes séquences et mes Vis etc..
Le problème arrive lors de la construction, une erreur apparait mais ne me donne pas plus de détails que ceci:
"error -19050: The bitness of LabVIEW does not match the bitness of the deployment utility."
J'ai essayé de chercher d'où vient le problème mais je suis au point mort la, je ne sais pas du tout où je dois regarder pour régler ce problème.
J'utilise les versions 2014 de LabVIEW et TestStand. Mes séquences fonctionnent correctement.
Merci de votre aide
Mehdi

Bonjour,
Je pense que tu risques d'avoir queslques difficultés pour exécuter ton application de test en distribution. Pour la distribution, il te faut effectivement au moins une licence Run-Time de TestStand et je pense que tu veux te passer de la licence LabVIEW.
Si j'ai bien compris, tu veux une distribution avec un installer de ton application TestStand. Tu as des séquences en TS2014 64 bits et tes codes modules LabVIEW sont en LabVIEW 32 bits pour le développement. J'imagine que ton adapter LabVIEW est configuré pour fonctionner avec LabVIEW en développement.
Première étape, as tu essayé de passer ton adapter LabVIEW en run-time ? A mon avis,ca ne va pas fonctionner d'parès cette KB .
Il faudrait que tes modules LabVIEW soient en LabVIEW 64 bits.
Le Run-Time TestStand n'est pas l'éditeur de Séquence. TestStand est un serveur ActiveX, et si tu as créé une interface opérateur spécifique, tu n'as pas besoin d'avoir l'éditrru de séquence pour exécuter ton application. SI tu veux les éditer ou l'exécuter depuis la même interface que celle que tu as en développement, il faut installer au moins le séquence Editor qui est disponible dans les "Optional TestStand Features..." lorsque tu coches Install testStand Run-Time. Pour l'acitvation de la licence, au pire, lors du premier lancement de ton application, il proposera de l'activer. Pense a ajouter le run-Time LabVIEW dans ton installeur si tu veux que ca installe tout d'un seul coup.
Mais je pense qu'avant de réussir tout ca, il faudrait vraiment vérifier l'exécution en Run-Time LabVIEW au niveau de l'adapter.
Petite question de curiosité, pourquoi tu chsoisis d'utiliser TestStand 64 bits ?
Cordialement
 

Similar Messages

  • Erreur logiciel lors d'une compilation FPGA

    Bonjour,
    Suite à un bug durant la compilation FPGA, j'ai installer la derniere version de LabView avec la derniere version du NI-RIO, et effectivement le bug est parti !
    Mais comme le bonheur ne dure qu'un temps, j'ai maintenant une erreur qui se produit lors de la compilation...
    En cliquant sur le bouton "Détails" de la fenetre de compilation, le message suivant apparait :
    Cette erreur peut elle etre due à mon code ou alors la raison est tout autre ?
    Cordialement
    Nathan

    Solution trouvé !
    http://digital.ni.com/public.nsf/allkb/5B8827503F7D90F386257BEA002D8E99
     

  • Code d'erreur -88302 lors de la reinitiali​sation d'une carte PCI-6229 dans soft d'automati​on

    Après installation de la carte et des drivers j'obtiens le code -88302 lors de la reinitialisation avec le logiciel Automation.
    Windows me confirme qu'il n'y a pas de conflit avec la carte - PCI-6229.
    Que veut dire le code -88302
    Merci

    Bonjour,
    Merci d’avoir utilisé le forum National Instruments.
    Ce code d’erreur interne est en rapport avec l’utilisation du driver NI-DAQmx par les logiciels du type de Measurement & Automation Explorer (MAX).
    Pour résoudre le problème, vous pouvez nettoyer la base de données de MAX en suivant la procédure suivante : How Do I Clean Corrupted MAX Database and Start With a New One ? 
    Vous pouvez également réparer le driver NI-DAQmx installé sur votre système ou réinstaller la dernière version du driver.
    J’espère que cela pourra apporter une solution à votre problème. N’hésitez pas à nous contacter à nouveau si le problème persiste.
    Guillaume H.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

  • Probleme avec le fichier 'cox32.obj' dans la compilation avec borland 5.02

    lors de la compilation d'un programme d'acquisition d'image, il y a le message d'erreur suivant:
    Error: Unresolved external '_main' referenced from C:\BC5\LIB\C0X32.OBJ

    Avez-vous essayé d'ouvrir un nouveau projet et sélectionné le type de projet comme étant une "Win32 Application" et non une "Win32 Console Application".
    N'hésitez pas à me tenir informée des résultats de cette modification.

  • Je vient de télécharger iTunes64Setup.exe Et vers la fin de l'installation on me dit sa : " Windows installer a rencontré une erreur inattendue lors de l'installation de ce package. Le code d'erreur est 2324. "

    Je vient de télécharger iTunes64Setup.exe Et vers la fin de l'installation on me dit sa : " Windows installer a rencontré une erreur inattendue lors de l'installation de ce package. Le code d'erreur est 2324. "
    I just downloaded iTunes64Setup.exe And towards the end of the installation I was told her: "Windows installation encountered an unexpected error installing this package. The error code is 2324."
    HELP ME!!
    AIDE-MOI !!

    Tu devrait essayer d'installer ton windows 7 via le bootcamp 5 (celui qui est avec Mavericks) mais a place de télécharger les Pilotes 5.0.5033 offert par Bootcamp télécharge Celui-ci , Par la suite décompresse le fichier sur une clef USB en ms-dos(fat) si c'est une clef de moins de 32Go sinon formate la en ExFat ! Sinon tu peux toujours Réessayer avec les Dernier Pilotes 5.0.5033, mais a place de lancer l'éxécutable installe les manuellement clique droit poste de travail et gérer, Dans le gestionnair de péripherique choisi des les updaters en choisissant le chemin (par example le pilote pour le bluetooth est très facile a trouver).

  • Erreur -69 lors de la mise à jour de l'ipod nano

    Cette erreur apparait lors de la mise à jour de l'ipod qui se trouve partiellement mis à jour. Des listes de lecture sont vides. Plus aucune possibilité de mettre mon ipod à jour. Idem après restauration.Que faut-il faire ?

    Salut Abelle,
    Lisez cette article:
    http://docs.info.apple.com/article.html?artnum=302684
    Bon chance,
    Maz

  • Is there anyone at all here who has successfully compiled and deployed an SSRS custom report item in VS2012?

    Is there anyone at all here who has successfully compiled and deployed an SSRS custom report item in VS2012?  Is there a demo out there that actually works in VS2012?  Is there anyone who has actually been able to compile and deploy that
    apparently obsolete Polygons demo?  (Pardon my impatience but I'm running a bit short of time here.)
    After much hacking and googling I was able to get Polygons to compile but I still can't deploy it to the toolbox.  ('The custom report item type PolygonsDesigner is not installed').   I've modified the RSReportDesigner.config
    as instructed but I have no rssrvpolicy.config file on my local machine and
    as yet I have no idea if that is necessary for local development.
    In order to get it to compile I first added the reference  C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportingServices.ProcessingCore.dll to both projects.
    To the PolygonsDesigner Project I also added the references:
    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportDesigner.Controls.dll
    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportingServices.Designer.11.0.dll
    C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\Microsoft.ReportingServices.Interfaces.dll
    Are these the correct references?  
    Exactly what software do you need installed on your local machine in addition to VS2012 in order to create a custom control?
    (Designer.11.0 was added per the instructions in reference: https://connect.microsoft.com/VisualStudio/feedback/details/783391/unable-to-integrate-previously-working-ssrs-custom-report-item-to-vs-2012s-toolbox  
    After that I added the alias RSDesigner to it's properties and   extern alias RSDesigner; at the top of the PolygonsDesigner.cs file. )
    As of now, the top of the PolygonsDesigner.cs is as follows.  I don't recall making any other changes to the code.  As far as I can remember this is all I did in order to be able to compile the code in VS2012.
        extern alias RSDesigner;
        using System;
        using System.ComponentModel;
        using System.ComponentModel.Design;
        using System.Collections;
        using System.Collections.Generic;
        using System.Diagnostics;
        using System.Drawing;
        using System.Windows.Forms;
        using Microsoft.ReportDesigner;
        using Microsoft.ReportDesigner.Design;
        using Microsoft.ReportingServices.Interfaces;
        using Microsoft.ReportingServices.RdlObjectModel;
        using System.Xml;
        using System.Xml.Xsl;
        using System.Xml.XPath;
        [LocalizedName("Polygons")]
        [Editor(typeof(CustomEditor), typeof(ComponentEditor))]
        [ToolboxBitmap(typeof(PolygonsDesigner), "Polygons.ico")]      
        [CustomReportItem("Polygons")]
        [ToolboxItem(typeof(RSDesigner::Microsoft.ReportDesigner.Shell.CRIToolboxItem))] 
        [System.CLSCompliant(false)]
        public class PolygonsDesigner : CustomReportItemDesigner
        {   etc...

    Just fixed this myself.
    It appears the documentation online is wrong and the sample code is missing a reference to a reporting services dll and an attribute.
    What you need to do to get it working in VS2012 is add a reference to: Microsoft.ReportingServices.designer.11.0.dll to the PolygonsDesigner project and then add the following attribute to the PolygonsDesigner class: [ToolboxItem(typeof(Microsoft.ReportDesigner.Shell.CRIToolboxItem))]
    I also removed the [System.CLSCompliant(false)] attribute.
    You then recompile and place both dlls in C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies directory and the PolygonsDesigner.dll into the C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin
    or what ever is you reporting services path.
    You also need to change the Microsoft example for the rereportserver.config file to:
        <ReportItemDesigner>
       <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsDesigner, PolygonsDesigner" />
        </ReportItemDesigner>
        <ReportItems>
       <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsCRI,PolygonsCRI"/>
        </ReportItems>
     Notice that I changed the namespaces and class to what is in the actual code so if you change it make sure you change it here.
    And here in the RSReportDesigner.config:
    <ReportItems>
          <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsCustomReportItem,PolygonsCRI" />
        </ReportItems>
        <ReportItemDesigner>
          <ReportItem Name="Polygons" Type="Microsoft.Samples.ReportingServices.PolygonsDesigner, PolygonsDesigner" />
        </ReportItemDesigner>
        <ReportItemConverter>
          <Converter Source="Chart" Target="Polygons" Type="PolygonsCRI.PolygonsConverter, PolygonsDesigner" />
        </ReportItemConverter>
    Notice I haven't changed the last part as I didn't know what the PolygonsCRI.PolygonsConverter was.
    And make sure the rssrvpolicy.config looks like this:
         <CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Description="This code group grants PolygonsCRI.dll FullTrust permission. ">
           <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS10_50.SQLSERVER\Reporting Services\ReportServer\bin\PolygonsCRI.dll" />
        </CodeGroup>
    After a restart of ssrs and relaunch of VS2012 I opened a test project and added the PolygonsDesigner.dll to the toolbox and it works.
    Jamie

  • Steps to compile and deploy files on jsap

    steps to compile and deploy files on jsap
    classpath that has to be set
    where to put the .class files
    (Where to fnd JNDI tab)

    jsas-sun java application Server
    I like to depoy servlet files on this server
    But it requires cloudscape to be started
    (database server)
    i have not even a single entry in the name of cloudscape

  • Mapping Input Parameter renders mapping unable to be compiled or deployed

    Hi there. I have an interesting issue I have not encountered before.
    I can create a new mapping with a Mapping Input Parameter (just one parameter of type Integer), map this to a table column of the same type and the mapping compiles and deploys without any issues.
    However, if I take an existing mapping (which already compiles and deploys without issues), add a Mapping Input Parameter to it (just one parameter of type Integer) and map this parameter through to a table column of the same type, when I compile the mapping I get a pop-up "Warehouse Builder Error" with a number 56 and a red cross. The mapping cannot generate any code and gives no explaination. Trying this on a different mapping causes the same issue but with a different number in the pop-up.
    I have tried changing the parameter from integer to another data type and this makes no difference.
    Removing the Mapping Input Parameter makes the mapping compilable and deployable again.
    Am I missing something here ?
    Thanks
    Paul

    Ok... this could be a bug, but I worked out how to resolve the issue.
    To get the issue:-
    1. Open a mapping which does not have a Mapping Input Parameter and compiles and deploys happily
    2. Add a Mapping Input Parameter object, add an output attribute to it and map it to a table column.
    3. Compile the mapping and you get a "Warehouse Builder Error" pop-up with a number, then a Validation Completed Successfully message. But no code can be generated and the mapping
    cannot be deployed.
    4. Slap your forehead and say "Doh!"
    To fix the issue :-
    1. Open the same mapping
    2. Resynch the tables you mapped the Mapping Input Parameter to. The mapping now compiles and deploys ok.
    3. Pat yourself on the back
    cheers
    Paul

  • EJB compilation and deployment problems

    Dear fellows
    I have good understanding of EJB development process, but the compilation and deployment process of EJB is very problematic for me. Please write me the complete steps which should include:
    1. Starting from class, interface programs creation
    2. Package creation and accessing it along with class path setting
    3. How and where to compile these classes and interfaces (app server details), JAR
    4.deployment details on any app server like SUN, web logic
    Kind regards
    Shahzad faisal

    Dear fellowsDear Shahzad faisal
    Start with the JEE5 tutorial:
    http://java.sun.com/javaee/5/docs/tutorial/doc/
    Part 3 discusses EJB stuff
    I would recommend going to a few samples, bundled with most of the appservers to see the appserver specific stuff.
    >
    I have good understanding of EJB development process,
    but the compilation and deployment process of EJB is
    very problematic for me. Please write me the complete
    steps which should include:
    1. Starting from class, interface programs creationSo you have the classes and interface implemented.
    Next thing is to create a ejb-jar.xml in which your EJBs are defined (optional for EJB3.0)
    2. Package creation and accessing it along with class
    path settingPackaging all in a jar file is enough for an appserver to find your classes.
    3. How and where to compile these classes and
    interfaces (app server details), JARCompilation usually needs the javx.ejb.* classes, most appservers have a j2ee.jar in which the javax.* classes you need are present.
    in jour jar file you package your classes and deployment descriptor
    4.deployment details on any app server like SUN, web
    logicDeployment to appservers is product specific, see the manual here.
    you may want to add some other , vedor specific, deployment settings which are not ejb specification defined, these go into a vendor specific DD, for Sun for example the sun-ejb-jar.xml.
    >
    Kind regards
    Shahzad faisal

  • Having problem in compiling and deploying servlet

    please tell me about environment variable because i m totally confused.i want to know why do i need to set environment variable.and how would it help me to compile and deploy my first servlet.
    i also want to know about Class path and path.
    please tell me this.
    i'll really appreciate

    thanks a lot.
    i got my first servlet compiled deployed and run.
    thanks againYou are welcome. If you think it really help, you can assign duke star to me :)
    Good luck to your web application.

  • VC - Compile and Deploy performance issues related to UserID

    Dear Guru's,
    I'm currently working at a customer where a small team of 4 is working with VC 7.0.
    One user has very long Compile and Deploy times. We first thought that it was related to his workstation.
    Then one of the other guys logged in on his PC and run the compile + deploy ant then it suddenly takes seconds again.
    So we created a new userID for this user who has the issues "<oldUI>+test" and suddenly all is back to normal for him.
    But, now here it comes that we deleted his old userID and created it again, but the issue is still there.
    So my assumption is that there is some kind of faulty record or index or something other strange linked to his userID.
    What can this be and how can we solve it?
    Thanks in advance!
    Benjamin

    Hi Anja,
    We use VC on 7.0 and we do not have any integration with the DTR.
    So in other words we use the default way of working with VC.
    The user had his models in his Personal folder then moved it to the Public folder so that other colleagues could see/try them as well. It doesn't matter where the model is stored (public or personal) as long if this specific UID is used compiling/deploying goes very slow... the log files do not give much info, why this happens...
    Cheers,
    Benjamin

  • "JSP-compiling" on deployment from JDeveloper

    Hi
    Can i remove compilation for JSP-files on deployment from JDeveloper 903?
    When I'm compiling and deploying a project from JDev it tries to compile my *.jsp source files.
    - Why?
    And JDevs jsp-error-checking has BIG holes. (The pages runs well then OC4J-compiles them...) Some projects don't get trough while other projects with the same code style works fine for some reason.
    I'm using JDeveloper version 9.0.3.10.35
    Thanks,
    -Erik

    Yes you can.
    Go into the "Settings..." of your deployment profile for your project. --> <yourprofile>.deploy
    Under the "WAR File" click on WEB-INF/classes.
    On the bottom right you'll see the option:
    "How should the selected source files be deployed?"
    Here you can select: "As source files only" and it won't
    compile and deploy your class files.
    Hope this helps,
    -Chris

  • Erreur 14018 lors du telechargement

    comment résoudre une erreur 14018 lors du téléchargement d'un film ?
    merci d'avance

    comment résoudre une erreur 14018 lors du téléchargement d'un film ?
    merci d'avance

  • Error code 1127 when using teststand deployment utility

    I'm have installed on my pc Teststand 3.0 and labview 7.0 -this error occurs during build
    Error Code:1127
    Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
    Open VI Reference in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

    >>>>>>>ok, I'm getting a different error code: error code 7 instead of a error code 1127 with the error:
    Error Code:7 Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW
    error: Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI
    Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI
    Distribution AX Wrapper.vi.ProxyCaller
    >>>>>>>>And I did a mass compile of the directory mentioned above and I got this error:
    #### Starting Mass Compile: Thu, Jul 15, 2004 9:44:04 PM
    Directory: "C:\Program Files\National Instruments\TestStand
    3.0\Components\NI\Tools\Deployment Utility"
    CompileFolder: error 13 at C:\Program Files\National Instruments\TestStand 3.0\Compon
    ents\NI\Tools\Deployment Utility\DeploymentUtility.exe
    #### Finished Mass Compile: Thu, Jul 15, 2004 9:44:17 PM

Maybe you are looking for