Improper Format error while saving for previous version

Hi all,
I have been developing some Daq code with LabView 8.5. Recently I needed to open the vi on a computer which has Labview 8. I used the save for previous version option. I used low-level vi's in my code which are both available to 8.5 and 8 instead of using new express vi's. LV warned me about converting fixed point numbers to double precision while saving, which in my opinion should not cause a problem.
I have also enabled "Show front panel when called" and "Show front panel when loaded" options from VI Properties dialog (as adviced by previous threads http://forums.ni.com/ni/board/message?board.id=170&thread.id=369331).
However I was not able to solve the problem. Are there any suggestions to solve my problems?
Thanks.
Gokcen

I dont understand exactly what the problem is.
Have you used fixed point numbers in your code? and if so does it matter if LabVIEW converts them to DBL? If not then dont worry about it.
What problem do you have with the 'show front panel when called' as it isnt clear from your message.
Also, if you can post your problem code as it makes it easier for people to see the problem
David
www.controlsoftwaresolutions.com

Similar Messages

  • LV2011 bug - Error wired to boolen function breaks when saving for previous version

    I just downloaded LabVIEW 2011 this morning. I created this VI and saved it for LV2010 to see how it would deal with it. I opened the VI in LabVIEW 2010SP1 and the error wire is broken. There were no warnings about problems saving this VI as an earlier version.
    =====================
    LabVIEW 2012
    Solved!
    Go to Solution.

    I would not consider this to be a "bug".
    I would call it rather an "incomplete feature" were the extra-mile (backwards compatibility) is not fully implemented. So filing a suggestion is really the best thing to do (i will not file one since it is your idea, but i will kudo it!).
    Saving VIs to previous versions does not change the BD itself. The requested functionality would require BD analysis and inserting (per scripting) an unbundle into the error wire. This is a complete new functionality, at least i am not aware that this is happening anywhere else....
    As a "part time solution" i would like to see a BD analyzer which warns you about possible issues during downconvert. So in your case an "errorlist entry" like:
    Warning: Connecting the error cluster to boolean functions is a new feature to LV 2011. Saving for previous version will lead to a broken VI.
    just my 5 cents,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Error saving for previous version 2009 to 8.5

    I have a project with a VI containing DAQmx Data Acquisition VIs, timed loops and other standard conrols and indicators.  When trying to save for previous version (from LV2009 to LV8.5) an error occurs.  All of the dependencies can be saved to previous versions but the main VI cannot.  Can anyone help with this problem?
    The error message can be seen in the image attached.
    Attachments:
    error.JPG ‏18 KB

    Backsaving creates a folder structure with the backsaved VI and all support files in their relative locations. This might be useful in most cases.
    Very often I just need a single VI (without SubVIs) backsaved. I do this programmatically using VI server (open VI reference, then call the "Save For Previous" method, then close the reference). See image below.
    To do this for a project you could of course use a recursive file list and go through the whole list (programmatically), saving the VIs in a parallel folder structure (create destination folder before saving the VI).

  • Error while saving Reward rule version

    Hi When trying to save reward rule after creaion of rule version , error while saving rule version U-00000062 001 , contact technical support. I have attached document below. Kindly advice what needs to be done.

    Thanks for your fast reply.
    This error is occurring in our development environment as well. Production is fine.
    I had the users get out of the system last night and I tried restarting services and eventually restarting each server but nothing has cleared the error yet.

  • Error while saving for Objective setting

    Hi,
    While saving the Objective setting templates i am getting the error as "Table HRPAD605 is not part of the Customizing object PDST T "
    <u>Error documentation is as follows</u>
    <b>Diagnosis</b>
    Entries in table HRPAD605 cannot be edited in connection with customizing object PDST      T as table HRPAD605 does not belong to customizing object PDST      T, according to the object definition.
    <b>System Response</b>
    The function terminates.
    <b>Procedure</b>
    Check whether the entered objects and keys are correct.Then check in the Implementation Guide whether the object was created correctly.
    Correct the object definition or the entry for the Transport Organizer interface.
    Thanks

    Hello,
    Most likely the is an inconsistency with the transport objects PDST and PDWS. Please run RHSOBJCH to correct this inconsistency.
    Afterwards you should be able to transport the templates via the catalog or via RHMOVE30. Please make sure that the category ID in the target system is the same otherwise you won't be able to locate the template.
    The report RHSOBJCH corrects the missing HR entries in the OBJS table.
    This step you need to perform only once. For OSA you need to overtake
    *5020 up to *5026, also PAD605,606 and 607 references.
    When you have done this (as said, only need to do it once) you can transport the categories and templates via the phap_catalog_pa transaction (righ-mouse click on the to be transported object).
    Hope this helps,
    Regards and Groetjes,
    Maurice

  • Error while saving for Objective setting using tcode phap_catalog_pa.

    while executing tcode phap_catalog_pa, i get the error "Table HRPAD605 is not part of customizing Object PDST T. 
    However, when I proceeded further to use the catalog, I am not able to make any changes and the error message i get is "Data was not saved Message no. HRHAP00_TEMPLATE003".
    I also executed the solution mentioned in previous threads on the same problem i.e.  run the program "RHSOBJCH" and executed the adjusting entries but to no avail.
    I have SAP_ALL authorization profile assigned to me. 
    Would be really helpful if someone could share their insights on solutions to rectify this problem.
    Regards,
    Kalpana

    Hi Kalpana,
    Check the configuration whether you have done it correctly or not.
    And try to upload one template which is existing on the system. Download it and upload it as a template.
    If the problem is still there then it will be some configuration issues.
    Thanks & Regards,
    Ganesh R K

  • 8.2.1 save for previous version

    I have a few problems with Labview 8.2.1 "Save for Previous Version" for use with a computer with Labview 8.0.
    1-Labview 8.0 does not see the VI (created by 8.2.1 that was saved for previous version 8.0) as an 8.0 VI.
    it complains:
    "The VI, last saved with LabVIEW 8.0, has been converted to version 8.0.  After a VI has been saved with LabVIEW 8.0 it can only be loaded by LabVIEW 8.0 or later.  Use Save for Previous Version... to save VIs for older versions of LabVIEW."
    2-I can't Reset the History to zero.  The history resets only down to 1.
    3-Save for Previous Version will not save only the one VI specified, it saves a bunch of VIs.  I have to pick out only the changed VIs and place them with the unchanged 8.0 VIs.  Is there a way to just save a single changed file as 8.0?
    Are these problems that were fixed in later versions of Labview, such as 8.5.1, 8.6 etc?

    Gaslight wrote:
    So keeping a copy of Labview 8.0 for an unspecified length of time means keeping one or more computers running Windows XP for an unspecified length of time.  Labview 8.0 will NOT run under Vista or Windows 7.  This also means the computers runing Labview 8.0 will no longer remain on out company LAN.  They are eliminating all computers running XP.
    I will be forced to order fewer copies Labview 2010 upgrade.  Less money for National Instruments.
    You could use the included VM version of xp in windows 7 if you needed to, but it runs really horribly.
    You could also keep a VMware image of XP on a computer.

  • Error While Saving Mapping For A Dimension

    I am getting The Error While Saving The mapping For a Dimension
    Any Clue?
    An error occurred creating DimensionMapGroup BROKERS.MAPGROUP1.DIMENSIONMAPGROUP : ***Error Occured in
    DELETE_MAPPING_GROUP: Analytic workspace object __XML_STARTUP_CALCMMBRS does
    not exist.
    Thanks
    Raghu

    Check the OSS note 550760 regarding the issue.

  • Error while saving new Version

    Hi,
    I am creating a new version in DRM by using Copy to New feature but I am getting an error while saving that version.
    The version gets created successfully but it does not allow me to save the same and gives the following error.
    Serve was unable to process request--->ORA-02291:Integreity constarint (MDM_SYS_C0047065)-violated - parent key not found
    Please help.

    Hi,
    I am creating a new version in DRM by using Copy to New feature but I am getting an error while saving that version.
    The version gets created successfully but it does not allow me to save the same and gives the following error.
    Serve was unable to process request--->ORA-02291:Integreity constarint (MDM_SYS_C0047065)-violated - parent key not found
    Please help.

  • Error while saving Prod order - "Class for order classification"

    Hi all
    I am getting the following error while saving the Production Order -
    "Class for order classification has not been generated".
    I went into the custiomization settings and tried to generate the class. But I get another error "No batch input data for screen SAPMSSY3 0131". The line items are also all in red and green.
    Any help would be highly appreciated.
    Thanks in advance.
    Hrishi

    Solved

  • Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

    I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1.  The code was saved with the 'Save for Previous Version' option available in Labview 8.  When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes).  Are there any ideas what's going on and how to fix this?
    Thanks for your help!
    Mike

    I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
    If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
    Try to take over the world!

  • How To Build exe for Previous Versions

    I'm new to LabView and still struggilng a little with all the files associated with a project, so I'm sure this is a simple question.
    I'm running LabView v10 for development, but wish to create an exe that can run on a v8.5 runtime version. I've seen the threads that suggest that this is as simple as 'Save For Previous Version'... but for some reason I cannot seem to make this work. I have tried saving the vi for 8.5, then choosing to build the exe, but upon being prompted to create an associated project, I'm told there are unsaved changes - that the subvi's have been converted to version 10. I've tried declining the changes and opting to use those in memory, but this also doesn't work; the built exe then gives me a runtime error, complaining it does not have LV Runtime 10.
    I've tried saving the project with 'Save for Previous Version', then building. Again, this doesn't work - even though when i open, then immediately close either the project or it's contained vi's, I'm told there are unsaved changes where it has been converted to LV10 - implying the saved files were indeed saved in LV8.5 format.
    I seem to be going round in circles here. Would someone mind laying out the necessary steps to build an exe that can run on a previous runtime environment?
    Thanks in advance
    Solved!
    Go to Solution.

    To my knowledge, none of NI's device drivers can have multiple versions co-existing.  Now, that doesn't necessarily mean if you use any hardware that you will run into problems.  If the hardware is NI hardware, then they will also have specific drivers which can be in conflict, but if they are another manufacturer, it'll come down to NI-VISA probably.  If you are using any NI data acquisiton cards, then you have DAQmx installed.
    As long as your program doesn't access these devices, you are OK.  You are not required to update the drivers if you don't use the hardware.  You need to look in the relase notes for each of the drivers you need to update and see if you can find a version that supports both 8.5 and LV2010.
    Even if you do this, it is not a 100% guarantee that you won't have problems.  I had written an application for a customer once that used NI-RFSA.  I had a control on the front panel based on a typedef in the driver.  I updated my laptop for a new project, but later had to come back and make an update for the original project.  The typedef had changed and caused a recompile.  Nothing broke on my end.  When I sent the update, it crashed on the customer PC because of the typedef change.  I ended up getting them to upgrade the driver on their machine.

  • Error while saving FYV : Gaps in financial year variant periods

    Hello Experts,
    We are getting an error while saving  a new FYV as:
    Gaps in financial year variant periods XY
    Message no. FGV556
    Diagnosis
    The period specification has gaps. The periods must be sequentially numbered without any gaps.
    System Response
    Only a correctly defined period assignment can be saved.
    Procedure
    Define the periods with consecutive numbers.
    Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
    For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
    Month-Day-Period-Yearshift
    11     ---     7     ---     1     ---     +1
    11     ---     14     ---     2     ---     +1
    11     ---     21     ---     3     ---     +1
    11     ---     28     ---     4     ---     +1
    12     ---     5     ---     5     ---     +1
    12     ---     12     ---     6     ---     +1
    12     ---     19     ---     7     ---     +1
    12     ---     26     ---     8     ---     +1
    12     ---     31     ---     9     ---     +1
    1     ---     3     ---     9     ---     0
    1     ---     10     ---     10     ---     0
    1     ---     17     ---     11     ---     0
    1     ---     24     ---     12     ---     0
    1     ---     31     ---     13     ---     0
    2     ---     7     ---     14     ---     0
    2     ---     14     ---     15     ---     0
    2     ---     21     ---     16     ---     0
    2     ---     28     ---     17     ---     0
    3     ---     7     ---     18     ---     0
    3     ---     14     ---     19     ---     0
    3     ---     21     ---     20     ---     0
    3     ---     28     ---     21     ---     0
    4     ---     4     ---     22     ---     0
    4     ---     11     ---     23     ---     0
    4     ---     18     ---     24     ---     0
    4     ---     25     ---     25     ---     0
    4     ---     2     ---     26     ---     0
    5     ---     9     ---     27     ---     0
    5     ---     16     ---     28     ---     0
    5     ---     23     ---     29     ---     0
    5     ---     30     ---     30     ---     0
    6     ---     6     ---     31     ---     0
    6     ---     13     ---     32     ---     0
    6     ---     20     ---     33     ---     0
    6     ---     27     ---     34     ---     0
    7     ---     4     ---     35     ---     0
    7     ---     11     ---     36     ---     0
    7     ---     18     ---     37     ---     0
    7     ---     25     ---     38     ---     0
    8     ---     1     ---     39     ---     0
    8     ---     8     ---     40     ---     0
    8     ---     15     ---     41     ---     0
    8     ---     22     ---     42     ---     0
    8     ---     29     ---     43     ---     0
    9     ---     5     ---     44     ---     0
    9     ---     12     ---     45     ---     0
    9     ---     19     ---     46     ---     0
    9     ---     26     ---     47     ---     0
    10     ---     3     ---     48     ---     0
    10     ---     10     ---     49     ---     0
    10     ---     17     ---     50     ---     0
    10     ---     24     ---     51     ---     0
    10     ---     31     ---     52     ---     0
    The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009  is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
    Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
    Please help!
    Susan

    Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year -  2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
    Month
    Day
    Period
    Year Shift
    1
    7
    1
    0
    1
    14
    2
    0
    1
    21
    3
    0
    1
    28
    4
    0
    2
    4
    5
    0
    2
    11
    6
    0
    2
    18
    7
    0
    2
    25
    8
    0
    3
    4
    9
    0
    3
    11
    10
    0
    3
    18
    11
    0
    3
    25
    12
    0
    4
    1
    13
    0
    4
    8
    14
    0
    4
    15
    15
    0
    4
    22
    16
    0
    4
    29
    17
    0
    5
    6
    18
    0
    5
    13
    19
    0
    5
    20
    20
    0
    5
    27
    21
    0
    6
    3
    22
    0
    6
    10
    23
    0
    6
    17
    24
    0
    6
    24
    25
    0
    7
    1
    26
    0
    7
    8
    27
    0
    7
    15
    28
    0
    7
    22
    29
    0
    7
    29
    30
    0
    8
    5
    31
    0
    8
    12
    32
    0
    8
    19
    33
    0
    8
    26
    34
    0
    9
    2
    35
    0
    9
    9
    36
    0
    9
    16
    37
    0
    9
    23
    38
    0
    9
    30
    39
    0
    10
    7
    40
    0
    10
    14
    41
    0
    10
    21
    42
    0
    10
    28
    43
    0
    11
    4
    44
    0
    11
    11
    45
    0
    11
    18
    46
    0
    11
    25
    47
    0
    12
    2
    48
    0
    12
    9
    49
    0
    12
    16
    50
    0
    12
    23
    51
    0
    12
    30
    52
    0
    12
    31
    1
    +1
    Thanks
    Deepankar

  • Error while saving any workflow in database

    hi
    i had created a simple workflow and i was trying to save in database, but i faced following problem while saving...
    plz help for this
    1700: Could not connect with username/password 'system/myadmin@orcl' ('ORA-12154: TNS:could not resolve the connect identifier specified
    -----------------------------------------------------------------------------------------------------------------------

    You need to install updated version of SharePoint designer.
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/f255f4b4-1828-4ccb-983a-5efbf0e020ae/sharepoint-designer-2013-server-side-activties-have-been-updated-prompt?forum=sharepointcustomization
    Try below:
    http://stackoverflow.com/questions/19652391/error-while-saving-a-workflow-via-sharepoint-designer-server-side-activities-ha

  • Error while saving BPM Project to MDS: BPM-70801 : Metadata operation failed

    Dear All,
    I am working on BPM 11g.
    I installed the following products for BPM 11g
    OS: Windows 7 SP1 Professional Edition all with 32 bit
    Installed s/w:
        JDeveloper 11.1.1.6.0 Generic Version
        OracleXE 11.2 Win32
        ofm soa generic 11.1.1.6.0
        wls 10.3.5
        RCU 11.1.1.6 for schemas dev_soainfra, dev_sdpm and dev_mds  - Utility run successfully.
    Overall Installation is successful wth no issues.
    Configuration of Weblogic server for domain is ok with admin server, soa_server1 and bam_server1 with test connections is ok.
    I am using browser as Internet Explorer 9
    In Jdeveloper 11.1.1.6.0 after creating application, project and process
    From BPM MDS Navigator I configured the connection for Database 11g XE as well using
    Override Application Server user/password
    For SOA MDS I included the dev_mds user with MDS partition as obpm
    tested connections all ok (weblogic and soa_server1 up and running)
    In Jdeveloper I am able to export the BPM successfully.
    In the BPM Project Navigator when I use the Project --> SalesQuote.jpr --> right clicking with
    option as  Save to BPM MDS the following error is occured as
    "Error while saving BPM Project to MDS: BPM-70801 : Metadata operation failed".
    If the error is resolved than I can see the project in BPM composer.
    My queries on this error are
    1) Has soa_server anything to do with this error
    2) Is dev_mds schema to be reviewed
    what can be the possibility to resolve the BPM-70801 error.
    Please provide the solution ASAP or send me the reply to my  [email protected]
    Regards
    Ajaz Ahmed

    Hello Ajaz,
    BPM-70801 is a very generic error that can have multiple causes. Please provide the error log from servers log file. From what I understand, you are using a separate soa_server1, so watch out /your_domain/servers/soa_server1/logs/soa_server1.log
    Regards
    km

Maybe you are looking for