"Scan Operation Failed..." When Scanning From

(Last modified: 01Jul1995)

This document (618467) is provided subject to the disclaimer at the end of this document.

Symptom

In WP Draw, the user selects File|Acquire Image and receives the error message "Scan Operation Failed. Make Sure That Search Path Contains Directory Where Scanning Software Is Installed." Sometimes this error message occurs as soon as the user chooses File|Acquire Image, and other times the error occurs after the scan is completed. Following the message, the image may still come into Draw. The path is correct in the AUTOEXEC.BAT file and in the [Twain] section of the WIN.INI file.

Solutions

This problem has been reported to Development concerning the following scanners: Logitech 256 gray-scale (version 2.2 or 2.21 drivers), Mustek HT 800 Turbo (version 2.0 drivers), and MarsTech CG6000 (version 2.2a drivers).

With other scanners, the problem can be solved by following proper troubleshooting steps. For users reporting this problem, please perform the following steps:

1. Make sure the path to the scanning software is included in the AUTOEXEC.BAT file. Make sure that the following items are included in the path: WINDOWS, TWAIN, and the directory for the scanning drivers. If the paths are not in the AUTOEXEC.BAT file, add them. FYI: One customer had appended the path to the TWAIN driver in the AUTOEXEC.BAT and was receiving the "Scanning Operation Failed" error when acquiring an image. After the customer re-entered the path, including the path to the TWAIN driver as part of the original path, the problem no longer occurred.

2. Make sure that the [Twain] section in the WIN.INI file contains the correct path to the scanning software. If it is incorrect, change it. If there is not a [Twain] section, then it may be that the user's software is not TWAIN compliant. In this case, refer the user to the scanner software manufacturer to determine this.

3. Check in REGEDIT to make sure that the paths for WP Draw and Presentations for Windows are correct (File|Run|REGEDIT/V|OK). If they are not correct, delete these lines and re-merge the registration file (see Folio memo 29813C in the WPWIN60 infobase) and retry the scan.

4. Exit Windows, RENAME the REG.DAT file, restart Windows, and try scanning again. NOTE: The REG.DAT file is automatically re-created when restarting Windows. If renaming the REG.DAT file corrects the problem, please have the customer send in a copy of the original REG.DAT file and then submit an STR regarding the situation.

5. One customer was using Deskscan software in accordance with the TWAIN drivers. The customer was able to correct the problem by making sure the PATH statement in the AUTOEXEC.BAT file contained the pathnames to the Deskscan and TWAIN software. If an APPEND statement was used in the PATH, and Deskscan and TWAIN were in the appended portion, then WP Draw could not "see" the drivers.

6. If none of the above steps resolves the problem, send the customer the Printer Conversion Update diskette (D5USWWP60X5X or D3USWWP60X3X). This will solve the problem for some scanners.

7. If none of the above steps solve the problem, please have the user check the version of the scanning drivers they are using (File|Acquire Image, click on the Close box in the upper left corner, and choose About). This step may not be possible from WP Draw if the problem occurs when the customer starts to acquire an image. The customer can try to get this information by acquiring an image from other TWAIN compatible software. Have the customer check with their scanner manufacturer to assure that they have the latest version of the TWAIN drivers.

This problem is corrected with the 04/20/94 (6.0a) release.

document

Document Title: "Scan Operation Failed..." When Scanning From
Document ID: 618467
Creation Date: 21May1994
Modified Date: 01Jul1995
Revision: 1
Novell Product Class:Groupware

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.