NI 4060 Procedure SQL-Error in Calibration Executive 2.0

[eszteam]

hi,

while trying to calibrate a PXI-4060 DMM module (procedure version 2.0) under calibration executive 2.0 following error is screened and the calibration fails:

Error executing substep 'Post'. The following SQL command failed: 'SELECT RESISTANCE.ID, RESISTANCE.Resolution, RESISTANCE.Delay, RESISTANCE.AutoZero, RESISTANCE.Range, RESISTANCE.Test_Point, RESISTANCE.Error_24_Hour, RESISTANCE.Offset_24_Hour, RESISTANCE.Error_1_Year, RESISTANCE.Offset_1_Year, RESISTANCE.Error_Temp, RESISTANCE.Offset_Temp, RESISTANCE.TempFactor, RESISTANCE.Lower_Limit_24_Hour, RESISTANCE.Upper_Limit_24_Hour, RESISTANCE.Lower_Limit_1_Year, RESISTANCE.Upper_Limit_1_Year FROM RESISTANCE...'
Native error code -2147217904 0x80040e10
Mi
crosoft OLE DB Provider for ODBC Drivers:
[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 8.

NI-DAQ 6.9, IVI-engine 1.83 and Test-Stand 1.0.3 are installed on the system. Even the calibration with an older version (1.1) of the procedure fails (ividmm.dll error message).

When using calibration executive with E-Series modules the calibration can be performed without any error messages.

How can we fix this problem? We appreciate your help.

Best regards,

Dipl.-Ing. Philip M. Fleischmann - CTO
esz Elektronik-Service GmbH
Max-Planck-Str. 16
D-82223 Eichenau

Phone: +49-8141-88887-39
Fax: +49-8141-88887-77
e-Mail: p.fleischmann@esz-gmbh.de

http://www.calibration-support.com

[DiegoF]

Hi,

I'll have to research on this problem. I have seen it only once and haven't been able to reproduce it. What version of MDAC (Microsoft Data Access Components) do you have installed?. You can find an utility called Component Checker in the microsoft web site:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q307255&

Is this the first time you're trying to run this system?. Or, was it a running system?, if so, What changes were made?. Was LabVIEW or any other program installed?. What OS are you using?

I did a search for "ividmm.dll" at www.ni.com. Try the solution presented here for the ividmm.dll error.

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/a22034dca3da035a86256a1b00641e2b?OpenDocument

I'll let you know wh
en I get more info.

DiegoF.

National Instruments