News and events
Working Device List
Mar 28, 2008
Working Device List
OCR in open beta
Sep 17, 2007
OCR in open beta
 

Troubleshooting

Solving trouble with DocumentScanning

If you have problems concerning installation, configuration and usage of DocumentScanning for Lotus Notes, you can find advice to get up and running (again) here.

During standard installation, setup complains about "There is a Notes Extension already registered. Password Plugin not possible":

DocSLN is back-end orientated. Running in server mode (destination database and config database reside on a domino server) DocSLN always establishes a new notes session to the server on a newly initiated scan procedure. But the client has to authenticate itself every time by user.id and password. To set this password the LNPass.dll is needed by DocSLN. The DLL is registered to the client during installation procedure. The entry EXTMGR_ADDINS=LNPass.dll has to be set in the notes.ini of the client. If any other addin entry exists already, the password plugin can neigher be registered nor be installed.

After clicking on the newly installed action button, Lotus Notes complains "Program not found":

The method of the action button tries to start an external program called "DocSLN.exe". If Notes can not find the file it displays this message. Make sure you have installed DocSLN in the correct path of your Notes installation during setup. Notice that DocSLN setup proposes the paths of a Notes 6 installation if there are both Notes R5 and Notes 6 clients installed.

DocSLN exits with an error message:

After encountering a serious problem, DocSLN stops proceeding and supplies an error message to the user. If you find the message to be too unspecific search for the logfile, DocSLN writes every time it has been executed. The file is named "DocSLN.log" and resides in your local temporary directory (usually c:\Documents and Settings\%username%\Local Settings\Temp). You can find out where your temporary directory resides by executing "set temp" on the commandline of your operating system. Search for the first appearance of ">> FATAL <<" in the left column. This line probably gives more information about the error.

After using DocSLN you get save conflicts in your databases which you scanned to:

DocSLN is fully back-end orientated. That means all attachments and embedded documents are directly stored in the database you scanned to without using the front-end (the Notes Client used for activation of the scan procedure). If you change only one item in the same document to which DocSLN currently wants to attach the scanned image, the Notes Client will mark it dirty and asks for saving it. Now there are two documents with the same doc id present one with the scan attachment and one without it but with the changed item. To avoid these save conflicts you can close the active document in the front-end after initiating the scan procedure. In the quickstart example we use the @Command([FileCloseWindow]) to ensure there will be no save conficts.

Document Actions