CIR AXIS - Technical Support Home Page
 CIR AXIS KnowledgeBase
In all cases, the following files/information should be provided:
· OS
· Versions of Domino, Notes, and Internet Explorer
· AXIS device firmware version
· CIR.INI (found in \Winnt or \Windows, OS-dependant)
o CIR.INI provides a multitude of information, including the versions numbers of the database template, version numbers of all executables (e.g. CIRHP.EXE, CIROCR.EXE, etc.), and valuable path information.
· CIRAXIS.NSF – zipped
· CONFIG.INI and CobraXMLDD.XML (from FTP directory) – may need to deactivate AXIS FTP service to locate
If the support issue appears to be related to a specific service (e.g. OCR, Barcode, Imaging, or DDoc) the following should also be provided:
· All files (TIF/PDF, HPS) from the service-appropriate directories:
o CIR OCR Service: \Cobra\OCR or \Cobra\ICR\Errors
o CIR Bar Service: \Cobra\ICR or CIR Log, 'Barcode Errors' view
o CIR Image Service: \Cobra\Imaging
o CIR DDoc Service: \Cobra\Ddoc or \Cobra\DDoc\Errors
· Screenshots or Logs of the service debugger as described below:
o AXIS FTP Service: Debug Screenshot (C:\cobra>ftpaxis –debug)
o CIR OCR Service: Debug Screenshot (C:\cobra>cirocr –debug)
o CIR Bar Service: Debug Screenshot (C:\cobra>cirbar –debug)
o CIR Image Service: Debug Screenshot (C:\cobra>cirimage –debug)
o CIR DDoc Service: Log (Logging=Y added to [DDOC] section of the INI) – results in DDOCFUNC.LOG. If no log is created, send debug screenshot
(C:\cobra>CIRDDSRV –debug)
How To Report CIR AXIS Technical Questions or Problems
|
|
 |