Login / Register
Change Your Country
A

Performance Issues PRB: Can not import EC/IR-II test records exported from another IntoxNet After exporting test results from one IntoxNet host PC in ‘EC/IR-II Relational Export’ format (*.E2R), attempts to import those test records into the database of another IntoxNet host fail with the error message, “Import not performed. Not all records in the <ImportFileName> have valid tamper-evident stamps. Would you like to see a report?” Upon viewing the report, one or more lines like the following are displayed: “EC/IR II SN# 123456 Test number 567890: Can not validate the Tamper Evident Stamp in this record.” Background: The EC/IR-II transfers an electronic signature to the IntoxNet host with each test record uploaded. IntoxNet validates these signatures (also called ‘tamper evident stamps’) upon: A) Receipt of those test records B) Any subsequent electronic transfer of those results to another IntoxNet host (modem or network / internet) C) Any attempt to import those results to its database. D) Demand. A demand signature validation is performed when “Validate” is selected from the Records menu of the database context menu in IntoxNet which appears when any EC/IR-II test result database is selected in the IntoxNet main program window. IntoxNet will not allow the import or host-to-host transfer of a set of test results if any test within that set has an invalid electronic signature. Upload fields within EC/IR-II test results records are never supposed to contain trailing spaces. An implementation issue in early versions of the EC/IR-II could lead to certain circumstances under which a test result data field would be transmitted with a trailing space. This results in an electronic signature that will validate for the purpose of initial transmission from the instrument to the IntoxNet host, but will later fail validation when IntoxNet attempts to check that record’s signature subsequent to initial receipt. Keywords:”Import failed” “Import not performed” IntoxNet E2R tamper-evident stamps

Question ID: 
562

A workaround fix for this problem is available in IntoxNet 5.3.8 and above.  A signature repair utility has been included in IntoxNet such that correct test records electronic signatures (tamper-evident stamps) can be re-assigned to results that have invalid signatures as a result of the above described scenario. 

To repair your signatures, launch IntoxNet on the computer that will be exporting (or uploading) the test results with the command line parameter /EC2CRCREPAIR, and perform a validation of your database.  When the validation has completed, the following message will be displayed:

Not all records in the database have valid tamper-evident stamps.  Would you like to see a report?”

Upon viewing the report, one or more lines like the following are displayed:

EC/IR II SN# 123456 Test number 567890: Can not validate the Tamper Evident Stamp in this record.
*** Repair Succeeded ** The tamper-evident stamp on test record #123456 of instument SN#567890 in database ‘desktopGeneric EC-IR II Test Resultsmaster’ was repaired.  Old stamp value: c0646c84; New stamp value: 74CB9274.  The transmitted tamper stamp results by appending 1 space(s) to composite test record field #40 (‘STDVALUE’) resulting in string value ‘.081 ‘.

Subsequent validations fo the database should now succeed, you should be able to export records that are importable on other IntoxNet hosts as well as perform host-to-host transfers of your data.

Categories: IntoxNet CPU License, Software
0

Your Cart