Why is database validation returning the following:
“Error 9020: DBLMgr: Unable to connect to the validation database. ERROR [42S02] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name '(<tablename>)'. -2146233088”?
This error should produce an error message similar to the following within the Kofax Capture error log (ERR_YYMM.TXT):
2006-08-10 16:35:18, 0x00000018, 0, 0x0000233C, 0x00000000, 0x00000000, C:\Program Files\Ascent, Validation, WKS053081209, 7.50.139, DoDatabaseLookup DbValPluginRuntime.DoDatabaseValidation, 0, DBLMgr: ERROR [42S02] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name '(tablename)'. -2146233088
This would indicate that the drivers are not able to access the table '(tablename)'; that this table, "object", either does not exist, does not belong to the dbo (database owner) or that it is not in the expected format.
When using SQL Server, along with other databases that may be accessed through ODBC, it is possible to assign an owner to a table. Unfortunately, the standard Database Validation setup will not allow for a specific account and password to be assigned to a particular table, only to the Database itself. If restrictions are placed on a table within the database, it may produce this result.
The Database Validation feature does not allow for an owner name to be specified. This should not be a problem if the log in name is the same as the owner name. However, if the names do not match it will result in this error or one similar to it.
Database Validation behaves as though table is owned by the database owner (dbo).
This problem may also occur if Security Boost is being used and the database is accessed via a mapped drive and not a UNC path. Please see KB 7033 for additional information on possible issues with Security Boost in this case.
Level of Complexity
Add any references to other internal or external articles