TestStand database on vista

I  select open database logging,but it can't work.The Acess file is empty. I can sure all of the configure is right.So I copy .seq to another computer which is install windows XP,it's OK.
My TestStand version is 4.0.Is this a bug when using Vista?

Denny,
TestStand 4.0 does not officially support Windows Vista, so there is no guarantee that any features of TestStand will work.  TestStand 4.1 (evaluation available here:  https://lumen.ni.com/nicif/us/teststand3/content.xhtml) is completely compatible with Vista, so will work.
In your case, I'm betting that the problem is that the access database is in the Program Files directory.  On Windows Vista, the Program Files directory is not writable except by administrators.  If you launch the TestStand Sequence Editor with administrator access, it will be able to write to the database.  Although this might fix your problem, I really don't recommend using TestStand 4.0 with Vista as we had to make many changes to ensure compatibility.
Josh W.
Certified TestStand Architect
Formerly blue

Similar Messages

  • How can I query TestStand Database quickly?

    Hello everybody
    I have a performance issue with default TestStand database what puzzled me for long time.
    In default database TestStand organize the different test item to different table, if I want to query a test record according to a special Serial Number, the query will look into UUT_RESULT at first to find a GUID then forward to the other table to find a series of GUID bound with this SN which will be used to go into different tables like a numeric values table or pass_fail table to find out the result of each test step.
    Half a year ago, we have a small tool embeded with customized TestStand Interface to access this SQL Server 2005 Express database to fetch a SN and all its test results details for faulty analysis. Recently I found it will cost me more than 2 minutes to fetch all related test results of one SN, I tried to write some query in SQL SERVER management studio to get the same thing, the case is still there. And also I check the tables, all tables are already indexed, so I'm quite confused.
    Did someone meet similar thing with me? Can you provide some suggestion on this?
    *The best Chinese farmer*

    What exactly is the query that you are using? Depending on how many records you are attempting to retrieve, two minutes may not be unreasonable. If the database is on a network share, if others are attempting to do similar, large queries, can also affect performance. Making your query into a stored procedure could save some time.

  • An error occurred calling 'LogMultipleResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'

    A test rig that worked fine started thowing the floowing error for me.
    See screen capature.
    Problem doesn't appear on the development PC.
    The code that I'm using is using the default settings for logging to the access database that ships with TS. All worked fine for a few weeks now it keeps ... breaking.
    An error occurred calling 'LogMultipleResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
    An error occurred executing a statement.
    Statement: STEP_RESULT.
    Description: The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.
    Number: -2147217887
    NativeError: -105121349
    SQLState: 3022
    Reported by: Microsoft JET Database Engine
    Source: TSDBLog
    Attachments:
    NIDBerror.png ‏17 KB

    Hello,
    As far as I remember the DB size was approx ~ 1.5 GB, I don't have access to that test station till Wednesday so I'll double check but it could be as simple as exceeding the DB size, I'll verify that when I'm on-site again.
    To answer a few questions from Scott:
    1) I'm using TestStand 2012 ( as it came with the installation disks shipped in the first quarter of this year ).
    The test station is offline so no updates have been applied since the install.
    2) I'm using the default NI Schema and an Access DB. ( No modifications have been made )
    3) I'm using the On-The-Fly feature logging feature both to ATML and the DB.
    ATML works with no issues, DB used to work fine until it refused.
    4) Fails every time when I start the sequence, disabling logging to the Database sorts the issue out.
    5) I originally used the BatchUUT.seq example that ships with test stand.
    I have developed a test that has three test sockets that have a common Initialize, Run Tests in parralel and have a sequence of common test steps.
    Scott:
    The issue you've sent speaks of UUIDCreate; I'm gettin issues with the STEP_RESULT .... I think these things are not related.
    Secondly I'm suing TS 2012 so a fix should have been propagated to my version.
    So to answer your question I'm using multiple processes on one computer.
    I will emphasize that everything worked fine up to a certain point ... so I'm guessing Doug might be right on the money with the fact that I've chosen a misfortunate Database ( Access ) for the job.
    Regards,
    Maciej

  • "catastrophic failure" in Teststand database viewer using mySQL

    Hello all,
    I am using Teststand 3.1 and mySQL version 5.0.3 I have everything set up and teststand seems to be logging results to the database. The reason I say this is because I can see the data using a mySQL query browser. The problem is when I try to use the Teststand database viewer I get a "Catastrophic Failure". I right click on a field from the database and say view data and I get the failure. Any ideas on what this problem is and/or how to fix it?
    Thanks in advance.
    EHat

    EHat -
    I just debugged this problem last week using MYSQL source for their ODBC driver. This appears to be a bug in their ODBC driver.
    Basically the MS DataGrid control is trying to access catalog info from a handle that has not yet been connected to the database. Internally in MYSQL a function table is null and a dereference occurs which causes an access violation. Even though the MS control should be better behaved, the MYSQL driver should be returning an error if the table is null, not crashing.
    For the next version of TestStand we will workaround this problem. I have an updated DatabaseViewer that you can try attached to this posting.
    Scott Richardson
    National Instruments
    Attachments:
    DatabaseViewer.zip ‏138 KB

  • Download not working for 10g Database for Vista

    Hi
    I am trying to download the Oracle 10g Database for Windows Vista,
    After 20% the download suddenly ends and i am not able to download properly,
    Please correct the issue ASAP so that i can download the Software
    Thanks and regards
    Cindy
    [email protected]
    (On behalf of Cindy)

    Can anyone pls. help me ? I tried all options from disbling firewall to uninstalling Bonjour.. But nothing works. Had I known that Apple makes such worst software I would never have bought iPhone !!!! Apple really *****!!!!!!!

  • TestStand database schema, Command Text

    Hi,
    I made a copy of Generic Insert schema and began to modify it.
    I deleted 2 fields from the UUT_RESULT table, and also from the table in my database. When I check the 'Validate' I get an error "Number fo Columns in the SQL text for statement UUT_RESULT does not match number of columns/parameters defined in schema".
    I modified the text in the 'Command Text' to reflect the change that I had made, but it is recreated either when executing 'Validate' or when exit and re-entering the database configuration.
    1) How to modify the schema to remove the fields?
    2) Why is this schema uses INSERT where the 'Generic Recordset' uses SELECT?
    3) The schemas provided by NI can not be modified. ONly their copy can. Also, the original sc
    hemas do not have any text in the Commnad Text. Can you explain that please?
    Thanks
    Rafi

    Rafi -
    1) The SQL statement must match the number of columns specified. If you delete a column from the Columns tab, you must alter the SQL statement by deleting the corresponding field name from the text and you must remove the "?" from the VALUES() section of the text.
    2) Most SQL databases support both SELECT and INSERT statements. A SELECT statement opens the table(s) and allows the client to fetch and create new records. This is a lower performance method to access a database. An INSERT statement is only allowed to create new records and typically has better performance. TestStand offers both ways as an example to end-users.
    3) We attempt to protect the NI schemas so that when a new release comes out and NI updates the schema, TestStand does
    not overwrite any edits that you could have made to an NI schema.
    Regarding the text not showing up for the Command Text control when dimmed, TestStand 3.0 had this behavior. TestStand 3.1 does not exhibit this behavior. For TestStand 3.0, all you have do it either copy the schema and look at the editable copy or temporarily check the Allow Editing of Schema on the Schemas tab and you can look at an NI schema.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • Teststand database RI problem against Sybase ASA 8.0 database

    When running our Teststand application against the SyBase Adaptive Server Anywhere 8.0.1 database,
    test results are saved to the parent table UUT_RESULT, but then I get the following Run-Time Error dialog:
    Details:
    An exception occurred calling 'LogResults' in 'ITSDBLog' of 'DBLog 1.0 Type Library'
    An error occurred executing a statement.
    Schema: Adaptive Server Anywhere 8.0.
    Statement: STEP_RESULT.
    Error in rowIntegrity constraint violation: No primary key value for foreign key 'UUT_RESULT_FK' in table 'STEP_RESULT'
    Source: TSDBLog
    -2147467259; User-defined error code.
    Location:
    Step 'Log Results to Database' of sequence 'Log To Database' in 'Database.seq'
    (code -2147467259 => 80004005 hex)
    Attachments:
    ASA_Generic_Recordset_Result_db.sql ‏10 KB
    TestStandDatabaseOptions.ini ‏201 KB

    Olafjell -
    Which schema are you using, recordset(SELECT) or command(INSERT), and are you using and ODBC driver or a specific OLE-DB provider?
    If you are using a select statement then when the UUT record is created, the database logger tries to find out what the value was so that it can write that value for the foreign key for the steps. Make sure that the statements in the schema are using a server side cursor for your tables so that if the database ODBC driver or provider that you are using can retrieve the key value from the database right after it creates the UUT record. If you are using server side cursors and this problem still occurs, it may be that the database ODBC driver or provider does not support getting the key value after the record is cre
    ated.
    Your only option might be to use command(INSERT) schema that generates key values in someway. The built in support is using an generated GUID value.
    Also with some work, if supported, you could use stored procedures to generate the key.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • TestStand database logging problem: only the first character is put in the table.

    I am using TestStand 2.0.1 and Microsoft SQL server database. There is a weird problem when I use database logging. At first, all the database logging ran good.
    Then one day after I moved the test equipment to production line, TestStand only logs the first character of each string field in the tables! There is no error message.
    I setup another SQL server running locally on the same machine as the TestStand is and move the database to the local server, database logging has no problem. Schemas in TestStand Dabasebase Options are the same.
    I tried to run TestStand from another computer on the network. There was no problem before, too.  But now, TestStand always shows a Run-time error message like this:
    Details:
    An exception occurred calling 'LogResults' in 'ITSDBLog' of 'DBLog 1.0 Type Library'
    An error occurred executing a statement.
    Schema: New.
    Statement: STEP_RESULT.
    Connection failureMultiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
    Source: TSDBLog
    Error Code:
    -2147467259; User-defined error code.
    Location:
    Step 'Log Results to Database' of sequence 'Log To Database' in 'Database.seq'
    I have checked that the connection is good and also the table UUT_RESULT has been logged correctly.
    Anyone can help?
    Thanks.

    Thank you very much, Santiago.
    Yes, I have a customized schema, but it is based on the pre-existing schema. I tried the schema:TS 1.x Access/SQL (NI), which  came with TestStand, the results were the same. 
    I have tried to run different sequences. On one computer, I always get only the first character of each string entry logged in the remote database, however for the local server, everything is fine. On the other computer, there is no local SQL server, I always get similar error message as I mentioned in my post. The sequence step reports error is  "Log Results to Database".
    Any more suggestion?
    Thanks again.
    Best regards,
    Jaso

  • TestStand Database

    Hello,
    I would like to merge two tables UUT_RESULT and STEP_NUMERICLIMIT in one table to be able to reach all these data in the same line.
    Is it possible to do that? and how to do it?

    It can certainly be done by adding additional columns in the UUT_RESULT table and creating your own schema but you might be better off creating a report (I'm assuming you're using Access) to present the data. What you want to do is frowned upon in database design because the data is not normalized. The original schemas in TestStand were like this with a UUT_RESULT table and a STEP_RESULT table. It was not normalized because there were columns always unfilled. For a pass/fail test step, the numeric limit and string limit columns were unfilled, for a numeric limit test step, the string limit and pass/fail columns were unfilled, etc. This results in inefficient writes, database size, searches, etc.

  • TestStand 4.2: error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database'

    Can anyone explain what could possibly be causing this to occur randomly?
    Attachments:
    Database Initialization Error.PNG ‏75 KB

    Usually I see that error when I try to log a step in a model or engine callback.  Some of the callbacks that are already in the model have logging turned off for the sequence but if you create your own callbacks then you may need to turn that off for them or just don't have any steps log data when clients override.
    Hope this helps,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • How can I convert a Database Handle from TestStand to LabVIEW?

    I want to use a Database Handle (already created in TestStand by an Open Database step) in a LabVIEW-VI (called from TestStand) to connect it with the "Connection Reference" input of the "Easy SQL.vi"? If I use a directly connection via the "TestStand - Get Property Value (Number).vi" I get back the error message 4101 in LabVIEW. How can I convert the Database Handle?
    Test Engineering
    digades GmbH
    www.digades.com

    The TestStand database step types use the CVI SQL Toolkit to talk to databases. The handle that you are referencing is an internal memory location and not a actual handle that you can directly use. Currently as implemented the handle that is stored in a numeric TestStand property for the connection and the SQL statement are the handle values returned from the CVI SQL Toolkit. So for the connection handle, you could call the CVI SQL Toolkit function
    DBGetConnectionAttribute (
    int Connection_Handle,
    tDBConnectionAttr Attribute,
    void *Value);
    and get the CVI CAObjHandle reference. With this you could then call the CVI ActiveX function
    CA_GetInterfaceFromObjHandle(
    CAObjHandle Object_Handle,
    const IID *Interface_Id,
    int Force_AddRef,
    void *Inte
    rface_Ptr,
    int *Did_AddRef);
    to get the actual ActiveX interface reference. This would have to be converted into a LabVIEW reference.
    You may want to consider just using LabVIEW to open a new parallel reference only using the toolkit.
    Scott Richardson
    National Instruments

  • 10g Database Installation in Windows Vista

    Hi,
    I have downloaded 10g database for vista from Oracle site. When i tried to install,i.e, after clicking on setup/OUI a command prompt appears and nothing else is happening.
    Mine is a new laptop Vostro series.
    Could somebody provide me steps in getting 10g db installed.
    Regards
    Sudhakar T

    The steps are described in detail here
    If your setup.exe does not start, check your Vista security setting (also described same place).

  • MySQL syntax error with TestStand 4.0 database logging

    I had been using MS Access database to log results which worked fine but the access database is too limited. Switched to MySql. Database works fine and I can query it from Visual C++ and was able to create all my result tables fine from TestStand.
    I get a syntax error when actually trying to log results and it has to do with either a missing quote or and extra quote, I can't quite tell. I thought I saw a post on this somewhere but can't find it now. Here is the complaint from TestStand:
    An error occurred calling 'LogOneResult' in 'ITSDBLog' of 'zNI TestStand Database Logging'
    An error occurred executing a statement.
    Statement: UUT_RESULT.
    [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT VALUES' at line 1
    Description: [MySQL][ODBC 3.51 Driver][mysqld-5.0.45-community-nt]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT VALUES' at line 1
    Number: -2147467259
    NativeError: 1064
    SQLState: 37000
    Reported by: Microsoft OLE DB Provider for ODBC Drivers
    Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
    Number: -2147217887
    NativeError: 0
    SQLState: 37000
    Reported by: Microsoft OLE DB Provider for ODBC Drivers
    Source: TSDBLog
    And here is all that appears in the MySql logfile:
    INSERT INTO UUT_RESULT DEFAULT VALUES
    070914
    You can't see it here but the string is truncated after the word VALUES. The next line starts with the odd number.
    Any ideas?
    Thanks,
    Bill Peters
    BAE SYSTEMS

    Sure. There were two bugs in the ini file that contains the default TS schemas (I think it was Default_Database_Options.ini or like that...).
    Anyway the table description for STEP_NUMERICLIMIT had for it's command line INSERT INTO MEAS_NUMERICLIMIT. I guess TestStand looked at that and said hmm I better create that table too. Then later down the page when you try to create MEAS_NUMERICLIMIT it says the table already exists even though it is empty. The generate SQL button builds a bad file and then the database viewer creates a bad database. I would have to go into MySql and drop the database. I had to save the schema under a custom name, edit it read it back in, generate a new SQL file, but then it would still fail validation because the ini files don't get updated until you exit TestStand. So basically I did this process 3 times before I got it right.
    It's wasn't a big deal but it's amazing how a little thing can cause a lot of work.
    The second bug, I'm not certain was initially in the file or somehow got set on the fly. There was a random int statement at the very end of the SQL table description for UUT_RESULT. It was also in the schema INI file. Since the int had no name and occurred in a odd place, it created a syntax error in MySql. Same fix as above.
    But like I said it's working great now. I like this approach because I serve it to the net with Apache and parse the database with simple PHP scripts.
    Thanks,
    Bill Peters
    BAE SYSTEMS

  • TestStand 2014 Database Problem

    Hi. I have no experience about logging results to database. I want to learn and do it. I want to use mssql. Could you help me about this situation?

    Hi all,
    I am attempting the same as the OP; I believe I have the tables set up correctly (can see all desired fields in SQL Management and Database Viewer) but when I run the sequence I always get this error:
    An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
    An error occurred executing a statement.
    Schema: Generic Recordset (NI)
    Statement: UUT_RESULT.
    Description: Cannot insert the value NULL into column 'ID', table 'TestAutomation_BBv2.dbo.UUT_RESULT'; column does not allow nulls. INSERT fails.
    Number: -2147217873
    NativeError: 515
    SQLState: 23000
    Reported by: Microsoft OLE DB Provider for SQL ServerDescription: The statement has been terminated.
    Number: -2147217873
    NativeError: 3621
    SQLState: 01000
    Reported by: Microsoft OLE DB Provider for SQL ServerDescription: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
    Number: -2147217887
    NativeError: 0
    SQLState: 01000
    Reported by: Microsoft OLE DB Provider for SQL Server
    Source: TSDBLog
    Any help is much appreciated
    _A

  • What is the best way to use TestStand/Labview to access database?

    Is it best to use the TestStand database step types or use existing Labview database connectivity code to access database?
    The database will contain configuration data and results data. I am also not using the standard results collection feature. (Test procedure will possibly last days so I think it is inappropriate to use results collection feature.)
    I'm just trying to make my code "future proof".
    Thanks

    tbob wrote:
    I have used both and I find that it is easier to use the Labview Database Connectivity Toolset. One step in a TestStand sequence can call the Labview vi. If done in TestStand, it takes many steps which I find harder to read and understand compared to Labview code. If it is just a simple one time access, TestStand may be a little easier, depends on one's preference.
    Thanks.
    I was thinking it would be easier to use the Labview code. I was just trying to sense if the community thought it was old hat and I should be using the TestStand code.

Maybe you are looking for