Common Issues - Disconnected Scanning - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

If the AutoFill Keyword Set you are attempting to work with, or the document you are attempting to upload, is large, you may need to configure your Disconnected Scanning client to allow more time for the data to be received from the server. Click Settings | Local Client Settings and increase the value of the Request timeout (seconds) option.

Users who are expected to scan documents into OnBase need rights to all Document Types associated with the scan queues to which they have been assigned. If a user was to encounter a batch of fully or partially-indexed documents to which he did not have rights while working in a scan queue, those documents would be stripped of their Keyword Values, becoming unindexed documents.

If a user was to try to upload this batch into OnBase, it would be sent into the Incomplete Upload batch status queue until it could be re-indexed. This is a data safety feature intended to prevent unindexed documents from unintentionally being imported into OnBase.

If the server-side Disconnected Scanning code is being run as part of an application pool, Active Directory authentication will not operate as expected because the application pool-assigned account is used instead of the current user's account.

In this case, to use the current user's credentials for Active Directory authentication, you must open the Server Communication Settings dialog box (Settings | Server Communication...) and select the Override User Account for domain authentication check box.

Like other modules that depend on the OnBase Web or Application Server, Disconnected Scanning requires additional steps to be taken before changes made in the OnBase Configuration module are reflected in the Disconnected Scanning client. See the Web Server Admin documentation for more information.

If your Disconnected Scanning client is taking an unusually long time to launch, you can speed it up by disabling the Authenticode signature verification check that is performed each time the Disconnected Scanning client is launched. For information on disabling the signature verification, see Authenticode Signature Verification.

In order to use an auto-logon across multiple domains, your Application Server's virtual directory must be configured appropriately for your auto-logon method in order for it to work correctly.

For trusted domains:

• When using a non-interactive auto-logon method (i.e., the -INTERACTIVE command line switch is not applied to the shortcut to the Disconnected Scanning client), Anonymous Access must not be selected for the Application Server's virtual directory.

• When using an interactive auto-logon method (i.e., the -INTERACTIVE command line switch is applied to the shortcut to the Disconnected Scanning client) the auto-logon will work correctly if Anonymous Access is selected or if it is not selected for the Application Server's virtual directory.

For non-trusted domains:

• When using a non-interactive auto-logon method (i.e., the -INTERACTIVE command line switch is not applied to the shortcut to the Disconnected Scanning client), Anonymous Access must not be selected for the Application Server's virtual directory.

• When using an interactive auto-logon method (i.e., the -INTERACTIVE command line switch is applied to the shortcut to the Disconnected Scanning client) the auto-logon will work correctly only if Anonymous Access is selected for the Application Server's virtual directory.

For more information, see the Authentication documentation.

If your TWAIN scanner does not end the scanning operation after all documents have been scanned, one of the following command line switches can be added to the Disconnected Scanning shortcut.

• Use the -AUTOTWAIN switch to ensure that Disconnected Scanning returns to an idle state after scanning, instead of locking.

• Use the -NOTWAINUI switch to prevent the scanner's user interface from being displayed altogether.

The Kofax hardware or software used to read bar code values in the Disconnected Scanning client sporadically has an issue reading the %SELFCONFIG% string that identifies a self-configured bar code sheet.

To resolve this issue, generate self-configured bar code sheets using the string OBSELFCONFIG instead of %SELFCONFIG%.

When performing a Server logon to log on to Disconnected Scanning, the OnBase Application Server checks to ensure that the user's password meets all password restrictions (e.g., the password has not expired, the password did not expire after first use, etc.). If the user's password has expired, he/she is prompted to reset it.

However, when performing a Local logon, the Disconnected Scanning client does not connect to the OnBase Application Server to perform these checks; if the password restrictions were met at the time of the last Server logon (i.e., the last configuration file update), then the user's log on credentials will remain valid for Local logons until the next Server logon is performed and the OnBase Application Server is able to determine that the user's password no longer meets the password restrictions.

By default, Microsoft Office documents are opened in an external viewer rather than within the Disconnected Scanning client. If the documents are still open in the external viewer when the Disconnected Scanning client is closed, and Encrypt local diskgroup is enabled, those documents will not be deleted from the temp folder in the local Disk Group. To prevent this behavior, you must modify the registry to allow the documents to be viewed within the Disconnected Scanning client. For more information on modifying the registry for Microsoft Office documents, search the Microsoft Support documentation for Microsoft Office documents open in a new application window.

When switching between system locales on the same workstation (e.g., moving from one language DLL to another), the previous language values are not cleared. The previous values for the <Default> option, such as <Predeterminado> (for Spanish), are displayed.

There is a known issue with Kofax SVRS that causes the Disconnected Scanning client to close after click OK in the Modify Scan Format dialog box and clicking Scan immediately after.

To prevent the Disconnected Scanning client from unexpectedly closing, wait a few seconds after clicking OK in the Modify Scan Format dialog box before clicking Scan.

Typically, the Windows user that is logged on when the Scheduler service is installed must be logged on when the Scheduler service is running to automatically upload batches to OnBase.

However, if needed, the Scheduler service can be installed and run using the Windows LocalSystem user account, but this will require you to use standard OnBase security (i.e., an OnBase user name/password must be provided in the Schedule item dialog box). Active Directory and LDAP authentication cannot be used when running the Scheduler service using the Windows LocalSystem user account.

Automatic processes, such as Auto OCR Batches, Auto Commit Batches, Auto PDF Conversion, Auto-Perform Image Processing, and Auto-Run after Scan, are only initiated when batch activity (indexing, scanning, etc.) is performed in the OnBase Client module.

If batch activity is taking place outside the OnBase Client, and automation is needed, the desired processes must be performed on a workstation running the OnBase Client module with one or more Auto-Processing Command Line switch(es) or they must be scheduled to occur on a workstation running the OnBase Client module.

This does not apply to the Auto-Foldering and Auto-Naming options, as they take place on a document level rather than based on batch activity.