Presentation on theme: "Resolving Common halFILE Issues. Effective July 11, 2006, Windows 98, Windows 98 Second Edition, and Windows Me (and their related components) will transition."— Presentation transcript:
Effective July 11, 2006, Windows 98, Windows 98 Second Edition, and Windows Me (and their related components) will transition to a non-supported status. After this date, Microsoft will no longer provide any incident support options or security updates. Microsoft is not offering a custom support agreement for these products.
Therefore, Windows 98 is no longer supported as a halFILE O/S Platform. Plan to upgrade to XP Professional.
Effective January 1, 2002, Microsoft dropped support for SQL Server 6.5.
Therefore, SQL Server 6.5 is not supported as a database server platform. Plan to upgrade to SQL Server 2000 or 2005.
Connectivity Issues hal Tech Support personnel should be able to connect to your system via PCAnywhere, Remote Desktop or VNC. Your personnel should learn how to use the connectivity software to reduce the time and effort it takes to connect.
Crystal Reports Issues One halFILE station should have the full Crystal Reports Designer installed on it. That station should be open to connectivity (PCAnywhere, Remote Desktop, VNC).
Error 430: Class does not support automation Cause: Workstation has incorrect version of halviewer.dll or haltextviewer.dll. User does not have sufficient local rights to install and register the halviewer.dll and haltextviewer.dll controls.
Error 430: Class does not support automation Resolution: If new workstation, select the HFDeliver tab behind the Tools-Options menu of the halFILE Administrator, then click Apply Updates to this workstation. On existing stations, this may be corrected by going the General table of the same Tools-Options menu and changing the Viewer type then saving. Then go back in and change the Viewer type back and save again. Unregister halviewer.dll and haltextviewer.dll. Then replace them with the latest versions and re-register. When doing the above, ensure sufficient user rights to the Windows\System32 folder.
Error 429: ActiveX Component cannot create object Cause: Similar to 430 error, typically halviewer.dll or haltextviewer.dll are not registered, out of date or missing.
Error 339: Component (Control) not correctly registered Cause: A windows component (.dll or.ocx file) has not been properly registered or is unlicensed. Imaging for Windows has not been installed or the trial version has expired. Or the Kofax viewer is selected but the Kofax runtime install was not run. Error with msflxgrd.ocx when trying to run halFILE on a station where halFILE was not installed.
Error 339: Component (Control) not correctly registered Resolution: Register the offending control: regsvr32 Install missing components (Imaging for Windows / Kofax Adrenaline Hardware Runtime / halFILE).
Error 75: Path/File Access Error Cause: A file cannot be read from or written to the folder on your computer or network. For TWAIN scanners, the basket path is a UNC path and the TWAIN driver cannot scan to a UNC path. The user was importing from a CD and answered YES to the question about deleting after import.
Error 75: Path/File Access Error Resolution: If a new server was put in place, this is most likely a rights issue on the new server. If you are scanning or importing, check the basket path. For TWAIN scan module errors, create a c:\scantemp folder place the following into hftwain.ini: tempdirectory=c:\scantemp\ tempfolder=c:\scantemp\ Dont forget the trailing backslash !!
Error 515: Crystal Formula Error Cause: Change in the database structure that affects the report. A formula in the report encountered unexpected data. A report was upgraded from halFILE 2.1 to 2.2. In 2.1, date functions were required on date fields. These functions are no longer needed with version 2.2.
Error 515: Crystal Formula Error Resolution: Open the report with Crystal Reports designer and verify it (Database – Verify Database menu). Review the formulas to determine if the data used in the formula is causing the error. For date fields, remove the date function and place the database date field on the report.
Error 501: Crystal Job number does not exist Cause: The Crystal Report is not compatible with the version of the Crystal Engine (CRPE32.DLL) that is installed on the station.
Error 501: Crystal Job number does not exist Resolution: Make sure all workstations have the same Crystal Runtime engine. Open the report with the Crystal Designer for that version of the Crystal Runtime. Verify the report and then save it. Ensure that the path and filename of the report exists and can be accessed.
Error 5: Invalid Procedure Call Cause: Clicking Print Preview and then Print on the Report Printing Utility window in Search.
Error 5: Invalid Procedure Call Resolution: Pick up the update to Report32.exe from the halFILE Update Service.
Error 380: Invalid Property Value Cause: A window was trying to be restored to a position that is off the screen. Most often has occurred in the halFILE Search module regarding the Image Viewer window.
Error 380: Invalid Property Value Resolution: Edit halfile.ini file and remove the screen restoration parameters. These are organized by module sections and then have prefixes referring to the function. For example in the [HFSearch32] section, the HALVIEWxxx lines refer to the halViewer.
Auto Archive does not run Cause: The user configured for the Auto Archive job is not longer valid or the password changed. The service used to run auto archive has stopped. The system was migrated to a new server but the job were not set up on new server.
Auto Archive does not run Resolution: Determine which service is used to run Auto Archive (Windows Scheduler or SQL Server Agent). Make sure that service is started. Check the user configured to run the job and correct user id and/or password. If new server, job must be set up again.
halFILE Database Backup does not run Cause: The user configured for the Auto Archive job is no longer valid or the password changed. The service used to run auto archive has stopped. The system was migrated to a new server but the job were not set up on new server.
halFILE Database Backup job does not run Resolution: Determine which service is used to run Auto Archive (Windows Scheduler or SQL Server Agent) and make sure that service is started. Check the user configured to run the job and correct user id and/or password. If first time set up, then run the script to create the sp_hfwbackup script. If new server, the job must be set up again.
Resolving Common halFILE Problems Remember the halFILE Knowledge Base is available. Select Help-Go to the Web (halfile.com) menu from the halFILE Manager. Click My halFILE. halFILE Knowledge Base link.