Missing Stored Procedure for SQL Server

[Brian_Esque]

Hello,

I'm trying to create the standard TestStand 4 schema for SQL Server. I get the following error when I run multiple numeric test cases:

An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
An error occurred executing a statement.
Schema: SQL Server Stored Proc (NI).
Statement: MEAS_NUMERICLIMIT.
Could not find stored procedure 'InsertStepMeasNumericLimit'.
Description: Could not find stored procedure 'InsertStepMeasNumericLimit'.
Number: -2147217900
NativeError: 2812
SQLState: 42000
Reported by: Microsoft OLE DB Provider for SQL Server

Source: TSDBLog

-2147217900; User-defined error code.

Step 'Log Results to Database' of sequence 'Log To Database' in 'Database.seq'

My process for creating the database is to create a .sql file from the TestStand database configuration window. I have selected SQL Server Stored Procedure. I then build the database by running the script in the Execute SQL window of the Database viewer. I don't get any errors when creating the database or the stored procedures. I have noticed that a stored procedure, called InsertMeasNumericLimit does exist. When I rename this procedure to InsertStepMeasNumericLimit, the sequence with the multiple numeric executes without error, and my data is in the database.

Now to my questions>

1. Am I doing something wrong in my procedure to create the database schema, that would cause this?

2. Have the NI schemas or DB calls in TS been changed since 3.5 and validated?

3. Has anyone else run across this problem, and what others can I expect to encounter with the SQL server stored procedure schema?

Thanks in advance for the help,

BCE

[Song_D]

bce,

1. What you are doing is correct. There is a bug with the SQL Server Stored Procedure. Apparently

2. The schemas hasn't changed since 3.5? Were you able to go through the same process in TS 3.5 without running into this error?

3. It looks like you have found the way to solve this problem. There are a few other step types that have similar error. Specifically the IVI steps. Before the bug is fixed, you can use validate to determines whether the statement and column information for the selected schema matches the tables and columns in the database. Alternatively, you may look at the file below to find out the correct spelling of the stored procedures.

<TestStand 4.0>\Components\NI\Models\TestStandModels\Database\SQL Server Create Stored Proc Result Tables.sql