Tips and tricks for Océ IntraLogic

Size: px

Start display at page:

Download "Tips and tricks for Océ IntraLogic"

Noel Gordon
6 years ago
Views:

Tips and tricks for Océ IntraLogic Printing Job import Size and performance Settings Print-to File formats TCP/IP printing Standard printer Information (tray/paper) State

1 Tips and tricks for Océ IntraLogic Printing Job import Size and performance Settings Print-to File formats TCP/IP printing Standard printer Information (tray/paper) State (paper jam) State ( unknown ) Mailbox name vs. Océ IntraLogic login name 31X5 printer, no job information (no license) 31X5 added as standard printer Incorrect printer information

2 Scanning Viewing scan jobs failed Conversion of document may fail due to timeout Scanner settings i.c.w. multiple servers with same scanner device Scanprofiles i.c.w Multiple servers with same scanner device Multifunctional device Generic scan profile Administration Devices & Groups modification (remove) Documents & Links Administration (remove) Device not supported by Océ IntraLogic Username may change when re-routing saved scanned documents Retrieving counter log files may fail (file type/browser) Océ IntraLogic server and Océ PrintLogic (SNMP port) Installation destination directory Timeout of import user list, apply template and cleanup Cleanup expired users does not give feedback Backup and restore Log files Microsoft IIS LockDown tool may prevent Océ IntraLogic from correctly operating Cleanup Temporary Directory Browser Settings Refresh times Not able to login Automatic login does not work Login is not possible Login sessions closed due to server timeout No access/login, incorrect bookmark Partial view/incorrect layout Timing error during automatic reload Internet Explorer memory usage Netscape crashes Netscape resize Acrobat Reader view Netscape/Internet Explorer problems

3 Print Job import Size/performance When importing a print job into Océ Intra Logic, the file will be transferred from the browser (client) PC to the Océ Intra Logic Server PC. When importing large print files (e.g. > 10 Mb) the performance will be decreased. Further, due to the copy action, temporary double amount of memory should be available on the Océ Intra Logic server, for importing the print job. Print Job import Settings When importing a print job, the job setting can be modified on request. These settings modifications are added by adding an Océ JEC ticket. The new Oce JEC ticket contains only the Océ Intra Logic settings. This implies that other JEC attributes are lost. Further, no checking is done for printer capabilities. Always an Océ JEC ticket is created and added at the beginning of the print job. This implies that you cannot modify job settings for standard printers which do not support Océ JEC tickets. Print-to file formats The print-to functionality does not check the capabilities of a specific printer. E.g. it is possible to re-route (print-to) a PostScript print job to a PCL-only printer. In this case rubbish will be printed or the printer has to skip the print job. This is also applicable for other print job settings (e.g. stapling). For the print-to functionality, it is advised to add similar printers (release versions) in the same group. Print-to TCP/IP printing The print-to functionality is based on lpr, which is provided by Microsoft TCP/IP printing service. As pre-condition, the Microsoft TCP/IP printing service has to be enabled, which is checked during the installation. If this service (and/or lpr) is removed after installation, the print-to functionality will fail. Further, if additional network software is installed (e.g. NFS Maestro), which installs a different version of lpr.exe (including first entry in PATH) the print-to functionality may fail.

4 Standard Printer information (tray/paper) The supported standard printer mib does not use the MIB attributes paperstrings and traynumberstrings, but use papersizes (in mm) and the order of retrieved trays. This implies: traynumber depends on the retrieval order: first retrieved tray, is numbered as 1. Depending on the retrieved paper size (in mm), the corresponding format and feed direction is calculated and set (e.g. A4 portrait). Standard Printer state (paper jam) Océ Intra Logic always displays the most important error / warning message, which is retrieved from standard printers. E.g. a paper jam on a HP is displayed within Océ Intra Logic as down / offline, because the retrieved device status is down. Standard printer state unknown Some printer controllers return an incorrect printer status, which results in an Océ Intra Logic state unknown (e.g. Océ850c,..). Printer Mailbox name vs. Océ Intra Logic login name For viewing your mailbox jobs via Océ Intra Logic, the mailbox name and the login name should be the same. 31x5 printer, no job information (no license) If an Océ31x5 R3/R4/R5 printer (without Océ Intra Logic license) is added to Océ Intra Logic, no job information is displayed. To configure an Océ31x5 R3/R4 printer, you have to: Enable PrintLogic license Add the ADPuser (!@#ADP#@!) Mark ADPuser as operator To configure an Océ31x5 R5 printer, you have to:

5 31x5 added as standard printer Enable / configure Océ Intra Logic. When Océ Intra Logic does not show the correct information (e.g. after changing the printer settings/configuration), you can perform the following action: Delete device and add again Restart the web server by restarting inetinfo or restarting the server PC If an Océ31x5 printer is added to Océ Intra Logic and is represented as a standard printer, you have to remove and add the printer again. This problem is caused by a slow network and/or slow printer response time. Incorrect printer information When Océ Intra Logic does not show the correct printer information (e.g. after changing the printer settings/configuration on the printer), you can perform the following action: Viewing scan jobs failed Delete device and add device again Restart the web server by restarting inetinfo or restarting the server PC Due to the installation of DISTILLER (activated) it is possible that viewing of scanned jobs failed. Problem is detected on Windows NT4 workstation with Adobe Acrobat 5.0. Viewing a scan job works fine the first time only. A second attempt results in a failure. Stopping DISTILLER can solve problem. Conversion of document may fail due to timeout The conversion of a scanned document may fail due to a timeout. The timeout is currently set to 15 minutes. This problem may occur when converting complex or large documents. This timeout-value can be changed by the administrator only (registry key: FRTimeOut).

6 Scanner settings i.c.w. multiple servers with same scanner device When running Océ Intra Logic on multiple servers, using all the same scanner device, you will have a problem with the scanner settings. When you add the same scanner to a second OIL server, the scanner settings of this OIL server are downloaded. All scan jobs are sent to the second OIL server. If the scan job was created with a scan profile (generated on the first server), the scan job will not appear in the scanner mailbox. Scan profiles i.c.w. multiple servers with same scanner device When running Océ Intra Logic on multiple servers, using all the same scanner device, the scan profiles will be undefined. Each time when a user activates / deactivates a scan profile, the list of all scan profiles will be updated. Performing this action from two different OIL servers, incorrect scan profiles are downloaded and scan jobs will not appear in the scanner mailbox. Don t add one scanner to multiple OIL servers. Scan profiles i.c.w. multifunctional device When adding a multifunctional (Océ31x5) to Océ Intra Logic, the available device functionality is checked. If OIL detects a scanner, the scanning option is enabled. This implies that a public scan profile is downloaded to the device. Already available scan profiles (of a different OIL server) are removed. You can restore the original scan profiles by activating / deactivating one scan profile on the original OIL server. Generic scan profile Intra Logic 2.4 has rudimentary support for single-profile scanning using the 31x5. To enable it, perform the following actions: Configure the 31x5 for scanning to Intra Logic Create a scan profile on the device using Océ Print Logic that specifies oil_ as the application prefix, and that requires the user to input a number Have each user enable then disable their Intra Logic scan profile When this has been done, the device will have two profiles: the Intra Logic Public profile, and the generic scan profile that was just created. After the user has enabled and disabled their personal scan profile, the header of their scan mailbox will have a number in parenthesis. This is the number they must input when scanning

7 using the generic profile. Scans made with this number will appear in the users scan mailbox. Devices & Groups modification (remove) It is best to perform devices administration when few users will be using Océ Intra Logic. In some cases this may cause strange behavior for end users: A user views a device group, but the group has just been deleted by the administrator. The user will be redirected to the default device group (first one in the list) A user views a device in a group, but this device has just been removed from the group by the administrator. The user will be redirected to the all devices view. A device is removed and a user views an "all devices" page containing this device. The icon for the specific device will no longer be updated. The list of jobs of the user will no longer contain information about the specific device. Reloading the web page will show a correct situation again A device is removed from a group See other remarks of "A device is removed..." Documents & Links Administration (remove) It is best to perform this administration when few users will be using Intra Logic. When administering documents, one strange situation can occur when: - a user requests "Corporate documents" - the administrator removes a corporate document - the user tries to select (click on link in browser) the document

8 The browser will show something like: HTTP Error Not Found The Web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct. Please contact the server's administrator if this problem persists. Note that the language setting of this message is dependent on the web server's (not IntraLogic's!) language setting When the user presses reload all is well again Device not supported by Océ Intra Logic When adding a new printer to Océ Intra Logic, the message box Device not supported by Océ Intra Logic can be displayed. This implies that the device is not recognized by Océ Intra Logic. Possible reasons: SNMP not configured on printer possible timeout on network (re-try the add action) incorrect hostname incorrect hostname ipaddress Further, it is not possible to add devices which are not recognized by Océ Intra Logic. Username may change when rerouting saved scanned documents The username of a re-routed document may change to IWAM_<system_ name> when using the following scenario: Scan a document and save it as PDF to your local disk. Then using the import functionality to import the PDF into your personal print mailbox. The PDF job appears under the name of the OIL user. Next re-route the PDF job to another Océ31x5 printer. Now, the job appears under the name of IWAM_<system_name> instead of the OIL user.

9 Retrieving counter logfiles may fail (file type/browser) When trying to download the counter logfiles and nothing happens, the problem could be related to missing file type association. In general, the file type association is set to notepad for downloading the counter logfile (csv). If the downloading fails (nothing happens), you can set the file type association (notepad for csv-filetype). In general, the System Administrator will perform this kind of actions on a client PC, which contains normally the correct file type associations. Similar problem (nothing happens) was detected when using IE5.5 (see on Microsoft support site problem numbers: MS Q and MS Q281119). To solve this problem, you have to install IE5.5 SP2. Océ Intra Logic server and Océ PrintLogic (SNMP port) When running Océ Intra Logic on the server, it is not possible to run Océ Printlogic simultaneously because both applications use the same SNMP port. You have to stop one of the applications to run the other one. Installation destination directory Windows2000 has defined reserved directory names. When a directory is created on the system drive with the name Program and the system is rebooted, a warning message box is displayed: File name warning: There is a file or folder on your computer called "C:\Program" which could cause certain applications to not function correctly. Renaming it to "C:\Program1" would solve this problem. Would you like to rename it now? During installation of Océ Intra Logic, several registry settings are created. When renaming the destination directory after installation could cause problems. So don t use reserved directory names. Further, don t use UNC paths (e.g. \\pc4-lorentz\c$\application ). This may cause problems with registry settings.

10 Timeout of import user list, apply template and cleanup The functions, import user list, apply template, cleanup operate on all users (or a large group of users). Depending on the function settings and the number of users involved an ASP timeout of the web server may occur. This timeout is set to 600 seconds for these functions. When the action is not completed in this time, the timeout occurs. The functions are implemented in such a way, that they skip users for which no action is needed. After a timeout it is possible to start the same action again. It will skip the users already processed and complete the action. Note that in the case of importing a user list the users that were added before the timeout occurred, are marked as "duplicate" the second time. Cleanup expired users does not give feedback After confirming the cleanup action a popup window appears. The content of the window remains empty (white or grey) until the action is completed. Only then the feedback is shown. This is observed in a number of configurations (esp. Windows NT Server). Backup and restore To backup the Océ Intra Logic settings (databases and documents), the administrator has to use standard tooling. It is advised to use the backup / restore procedures as described in the OIL documentation (see oil_backup_restore.doc). Some tips: Don t mix files of different systems / backups Don t edit backup files manually For Win2000 servers, be aware of the directory permissions Backup general OIL settings manually (see OIL documentation)

11 Logfiles In case of an error situation, specific information is written to a log file. OIL creates three different kind of logfiles (adp*, web*, install*), which are located in the directory <IntraLogic/logfiles>. In required logfiles can be inspected and forwarded to R&D for further investigations. During de-installation, all files and directories are removed. Logging information of de-installation is stored in a separate directory located in c:\oiltemp. Microsoft IIS LockDown tool may prevent Océ Intra Logic from correctly operating During function testing the MS IIS lockdown tool was used to enforce stricter security settings on the web server. This tool was introduced at the end of last year in response to all the security vulnerabilities of IIS. It can be expected that server administrators use this tool to better protect their server. When using this IIS LockDown tool, Océ Intra Logic may not functioning correctly. To prevent problems, de-install the IIS Lockdown tool. Cleanup Temporary Directory Océ Intra Logic uses temporary directories (<IntraLogic>/temp and <IntraLogic</Smbx/temp) for storing files uploaded to the web server. If a user sends a file to the web server (for instance, job import) but cancels the transmission, it is possible that this directory is not cleaned completely. After longer periods of time, it may be possible that this directory contains a lot of "debris". In that case, it may be advisory to empty this directory. It is best to stop the web application before such a cleanup. Browser settings The following browser settings are required: "Accept cookies" must be enabled. For Internet Explorer both per-session and persistent cookies. For Netscape the option "Accept only cookies that get sent back to the originating server" is sufficient. "Scripting" must be enabled. In Internet Explorer this is the option "active scripting". In Netscape this is the option "enable JavaScript". "Style sheets" must be enabled (Netscape only).

12 Océ Intra Logic expects a display size of at least pixels and small fonts in the display settings. The application specifies its own fonts and colors. In Netscape the option "use document specified fonts, including dynamic fonts" must be enabled. It is possible to override the application fonts and colors, both in the browser and in the display settings. Although the application will still function the layout may be severely effected. Buttons may fall outside the scope of the windows (all windows can be resized manually). Browser Refresh times The following browser refresh times are specified: Browser Not able to login In all printers view: the printer icons are updated each 5 secs the queue will be updated each 15 / 60 secs depending on personal jobs in queue In detailed printer view: the queue will be updated each 15 / 60 secs depending on personal jobs in queue To use Océ Intra Logic, you should enable / accept cookies. If this option is not enabled, you are not able to login. Enable this browser setting before using Océ Intra Logic. See also browser (incorrect bookmarks). Bowser Automatic login does not work To enable automatic login, information has to be written in the COOKIES file. If this file is read-only, you are not able to login automatically (Netscape only).

13 Browser Login is not possible Login is not possible, although username and password are correct. No error message is shown, just the login screen again. This is caused by a caching problem. ASP pages should not be cached by the browser. Therefore the web server sets the expiration time of an ASP page explicitly to 1000 minutes before the current system time ON THE SERVER. When the system time of the client PC is more than 1000 minutes (> 16 hours) behind the system time of the server, the ASP page (in this case the login screen) is still cached. The problem can be solved by adjusting the system time of the client PC or server. Browser Login session closed due to server timeout If an user does not use Océ Intra Logic for a long time, the session can be closed due a timeout on the server. The user has to login again. The web server has a timeout for ASP sessions. If the timeout expires without a page request from the application, the session will be closed by the web server. You have to login again to rebuild the session. This timeout on the web server is set to 20 minutes by default. The Océ Intra Logic application refreshes the banner page each 19 minutes to keep the session with the web server. If the timeout on the web server is changed (< 20 minutes), this mechanism does not work anymore. To solve this problem, reset the timeout to the default value. Browser no access/login, incorrect bookmark After upgrading OIL, some users could report that they cannot login anymore with their old R2.1 bookmark. This is mostly the case when they didn't bookmark the login page, but some arbitrary other page within the application. Apparently the browser stores some other information in the bookmark as well. A result of this problem is that the total number of ASP sessions (see performance monitor) explodes with several thousands. Some additional information: when the bookmark is set to the OIL login page, everything works fine. when the bookmark is set to a page inside OIL, files on this page could be changed / removed which results in errors during opening the session. Opening the session will be retried (100 times/sec), which can result in some additional server load.

14 Problem can be solved by stopping the browser, or using the URL of the OIL login page. The problem can be solved by removing all bookmarks and using the correct OIL URL. Browser Partial view / incorrect layout Due to bugs in browsers and/or differences between browser versions, sometimes the layout is not fully correct. Often after a refresh / reload the view/layout is rebuild correctly. Depending on the system load, the JAVA SCRIPT processor could be busy for a moment which can result in an incorrect layout (e.g. roll-over stays visible). If the problem is related to a specific version of the browser, use a different version of the browser (e.g. newer). Browser Timing error during automatic reload Due to timing problems, it is possible that an error message ( object/method not found or supported ) is displayed. This problem occurs when the user performs an action on an object that is being refreshed by the automatic reload. This automatic reload is performed each 60 seconds to update / refresh the page. The displayed error could be ignored. Browser Internet Explorer memory usage If the browser (IE) stays open in the Printing Services view, the size of used memory grows slowly. After several days a huge amount of memory is used. To prevent this problem, close the browser periodically (e.g. every day). Browser Netscape crashes Sometimes the browser (NS) will crash. There is no direct relation to Océ Intra Logic. It seems that clearing the history file will reduce the number of crashes.

15 Browser Netscape resize Acrobat Reader view When using the Netscape browser and viewing a scanned image, by pressing on the view-button, the image is displayed with Acrobat Reader in a NS window. After resizing this window, the image is not re-displayed again (empty window). After clicking on reload frame in Acrobat Reader, the image is displayed correctly. Browser Netscape/Internet Explorer problems In some cases, problems (e.g. viewing/saving scanned images) are related to specific browser versions. Detailed information can be retrieved via the Microsoft support site. It is advised to use the latest release / version of the browser (preferable IE5.5 or IE6.0).

Release Notes Fiery X3eTY 35C-KM version 2.01 and Fiery X3eTY 30C-KM version 1.01

Release Notes Fiery X3eTY 35C-KM version 2.01 and Fiery X3eTY 30C-KM version 1.01 This document contains information about the Fiery X3eTY 35C-KM version 2.01 and the Fiery X3eTY 30C-KM version 1.01. Before