"Could not validate the NIST database" error connecting to NIST database in eCapture Controller
Applies to: eCapture
Version: Any


Symptom:
When attempting to connect to the NIST database in eCapture Controller, an error occurs:

Could not validate the NIST database. Verify the database name is correct, it exists on the same server as the eCapture configuration database, and matches the NIST schema
Warnings
Some of the resolutions below require knowledge of T-SQL and/or SQL Management Studio; consult a qualified SQL administrator for assistance with these procedures. Back up any targeted SQL databases before executing any SQL statements.


Possible resolution 1:
The eCapture SQL user is not the owner of, or does not have permissions to, the NIST database. To resolve the issue, set the eCapture SQL user as the owner of the NIST database.
Possible resolution 2:
The NIST database does not contain a sufficient number of records in the NSRLFiles table. eCapture considers any database with fewer than 10,000,000 rows in this table to be an invalid or incomplete NIST database. To resolve the issue, use the NIST Database Loader to reload the NIST database and ensure that all tables are properly populated. Ipro Technical Support can assist with questions or problems with the NIST Loader utility.
Possible resolution 3:
The MD5 index does not exist on the NSRLFiles table in the NIST database. This index must exist for eCapture to read the table properly. The following script can be executed to create the index:

Code:
CREATE CLUSTERED INDEX [MD5] ON [dbo].[NSRLFiles]
(
[MD5] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON, FILLFACTOR = 100) ON [PRIMARY]
GO