Knowledge Base Articles Sorted By Title(Full Listing)

• <database file> isn't an index in this table. Look in the indexes collection of the TableDef object to determine the valid index names.
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3015
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• A Brief Explanation of Table Relationships In HelpMaster Pro's back end database
  HelpMaster Pro utilises a relational backend database.  This Knowledge Base article is designed to impart an understanding of what the "relationships" between the tables in the database are all about.  This is important information when writing custom reports.
  Error Code:n/a
  Date Created:10/04/2000
  Last Updated:10/04/2000
  


• 'A fatal error has occurred. Site header not found or duplicates found. This conversion process will now terminate.'
  This error will occur when attempting to convert a HelpMaster Pro V5 (HMP5) database to a HelpMaster Pro V6 (HMP6) database if the site header in the V5 database has been deleted or modified during a compact and repair procedure.
  Error Code:n/a
  Date Created:14/05/2003
  Last Updated:14/05/2003
  


• 'A Licensing error has occurred. Please save your work now because the system will log you off in the next minute'
  The following error occurs: 'A Licensing error has occurred. Please save your work now because the system will log you off in the next minute.'
  Error Code:n/a
  Date Created:21/05/2003
  Last Updated:21/05/2003
  


• All standard reports and all options in the print menu appear three times.
  This is problem does not produce any errors, but rather is a slight inconvenience. All three of each option does work.
  Error Code:n/a
  Date Created:31/01/2001
  Last Updated:31/01/2001
  


• Auto-create AssetID's and ClientID's
  Errors are encountered after the upgrade process from v4 to v5 of HelpMaster Pro. Typically "Error 13 - Type Mismatch" occurs when trying to view Assets or Clients Note: SQL code/queries on this page are based on a version 4 database only.
  Error Code:n/a
  Date Created:27/02/2001
  Last Updated:27/02/2001
  


• Checklist for trouble-shooting corrupt databases
  Database corruption and bloat is a normal and natural part of every database, whether it is an Access database, a SQL Server database or other. Good database maintenance is essential therefore to keep performance and integrity at a premium. This checklist has been compiled to assist database administrators to troubleshoot and determine the cause of a database that shows signs of regular corruption, despite a regular maintenance schedule.
  Error Code:n/a
  Date Created:7/10/2001
  Last Updated:7/10/2001
  


• Client Access Module - HTTP Header Errors
  The following error occurs when a user attempts to sign onto the web interface. Error: -2147467259 - 006~ASP 0156~Header Error~The HTTP headers are already written to the client browser. Any HTTP header modifications must be made before writing page content.
  Error Code:n/a
  Date Created:11/01/2001
  Last Updated:11/01/2001
  


• Component 'CRVIEWER.DLL' or one of its dependencies not correctly registered: a file is missing or invalid
  This error can effect Terminal Server users when they try to produce reports. It is caused when the Crystal Reports DLLs are registered in the Administrator part of the Registry, but not in the regular users part.
  Error Code:339
  Date Created:31/01/2001
  Last Updated:31/01/2001
  


• Create a Connection using ODBC
  The database file used by HelpMaster Pro is a secured Microsoft Access 97 database. Registered users of HelpMaster Pro are entitled to view the database; evaluation users are not. In order to access the database, you will need to connect to the "system.mdw" security file that is in the same directory as the HelpMaster pro database file "hmpro.mdb".
  Error Code:n/a
  Date Created:16/01/2001
  Last Updated:16/01/2001
  


• Creating An Archive For Your HelpMaster Pro Database
  For performance reasons you may wish to periodically create an archive of older Jobs that have been closed.  To do this you have two options: Option 1 creates an archived database that can be used immediately with HelpMaster Pro if you want to see the older jobs. This is the best way to go if you think you will need to refer back to the old jobs on a regular basis. Option 2 only archives the jobs, and does not include all the data in the other tables (such as clients, staff, sites, etc).  This is the best option if you do not think you will need to refer back to the older jobs often.  It saves disk space, but you will need to copy all of the records back into your live database (or a copy of it) before you can view the archived records with HelpMaster Pro again. NOTE: While the instructions in this article are for use with Microsoft Access 2000.  The same principle applies to performing this procedure with Microsoft Access 97.
  Error Code:n/a
  Date Created:1/03/2001
  Last Updated:1/03/2001
  


• Develop your own custom reports for Helpmaster Pro v4
  The purpose of this page is to help customers and consultants develop their own custom reports for HelpMaster Pro v4. HelpMaster Pro uses two different types of reports.
  Error Code:n/a
  Date Created:16/01/2001
  Last Updated:16/01/2001
  


• E-mail and HelpMaster Pro - Setting Your Chosen E-mail Application As The default MAPI Client On Your Computer.
  HelpMaster Pro attempts to send all E-mail through your systems default MAPI mail client. For this reason if you find that HelpMaster Pro is not using your preferred mail system even though it is MAPI compliant you may like to check that it has been set as the default MAPI application.
  Error Code:n/a
  Date Created:27/02/2001
  Last Updated:27/02/2001
  


• 'Encryption functions on this computer have failed…'
  After installation of the HelpMaster Pro V6 Desktop module, you may receive the following error “The encryption functions on this computer have failed...” See Fig.1. Fig.1 The problem would most likely be due to not using the Western European/US locale as the "system default" locale. This is because the Code Page is changed when the "system default" locale is changed. The registration code in the “HMP6Demo.mdf” Demo database has been encrypted using the Western European/US (WE/US) Code Page, so when a system tries to decrypt it using a different Code Page it will see invalid characters and the Encryption Functions will fail.
  Error Code:n/a
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• 'Encryptions on this computer have failed….'
  The following error - 'The encryption functions on this computer have failed....' - occurs when attempting to login to HelpMaster Pro.
  Error Code:n/a
  Date Created:14/05/2003
  Last Updated:14/05/2003
  


• Error 1000 - Unable to open database
  HelpMaster Pro uses a secured Microsoft Access database. Secure database require that a file named system.mdw is located in the same directory as the HelpMaster Pro database file ("hmpro.mdw"). When this file is absent, the following error message will be displayed. Please note that this “system.mdw” file is not the same as the default "system.mdw" file that is shipped with Microsoft Access. It is a file that is designed to work with HelpMaster Pro. The security file for the database is missing or not located in the correct directory. Please ensure that either the 'system.mda' or the 'system.mdw' file that was shipped with HelpMaster Pro is located in the same directory as the database and try again."
  Error Code:1000
  Date Created:10/04/2000
  Last Updated:10/04/2000
  


• Error 13 - Type Mismatch
  Errors are encountered after the upgrade process from v4 to v5 of HelpMaster Pro. Typically "Error 13 - Type Mismatch" occurs when trying to view Assets or Clients Note: SQL code/queries on this page are based on a version 4 database only.
  Error Code:13
  Date Created:6/10/1999
  Last Updated:6/10/1999
  


• Error 13 Type Mismatch Error
  You receive an error such as the one below Error Number: 13 Product: Desktop Error Description: Type mismatch Error Source: HMP6DBAdmin.guiSystemAdmin.myGuiListEntity_onSelect Dll Version Info: PRDErrorTrap = 6.06013; HMP6GUI = 6.0.6013; PRDCGUI = 6.06013; HMP6BLL = 6.0.6013; HMP6DBAdmin = 6.0.6013; DB Version Info: 1.2
  Error Code:13
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• Error 2001 Cannot Open File
  HelpMaster Pro uses a dockable and user-configurable menus and toolbar controls. The sizing and positioning details of these objects are stored on the hard drive of a computer in the same location as the HelpMaster Pro executable file (hmpro.exe). This file is named "USERLAYOUT.TB". Occasionally this file becomes corrupt.
  Error Code:2001
  Date Created:23/08/2000
  Last Updated:23/08/2000
  


• Error 2007 - Invalid Bands Collection Index or Error 2001 Cannot Open File
  HelpMaster Pro uses dockable and user-configurable menus and toolbar controls. The sizing and positioning details of these objects are stored on the hard drive of a computer in the same location as the HelpMaster Pro executable file (hmpro.exe). This file is named "USERLAYOUT.TB". Occasionally this file becomes corrupt.
  Error Code:2007
  Date Created:23/08/2000
  Last Updated:23/08/2000
  


• Error 20500 - Not enough memory for operation
  HelpMaster Pro v4 requires that a folder called “Reports” is located in the same directory as the HelpMaster Pro database file (hmpro.mdb). This folder contains all of the Crystal Report files (.rpt).
  Error Code:20500
  Date Created:10/03/2000
  Last Updated:10/03/2000
  


• Error 20533 - Unable to Open Database
  NOTE: [ This error may also occur if trying to use a custom report from a previous HMP db version. Reports written for use with HMP 4 cannot be used in HMP v5 as the DB structure and tables have been upgraded. Any custom reports you had for v4 will need to be re-written to suit HMP v5. ] When attempting to export a report the above error may occur. The indicates that the original installation did not work correctly, or there was a conflict when registering some of the required exporting DLL files.
  Error Code:20533
  Date Created:9/06/2000
  Last Updated:9/06/2000
  


• Error 3043: Disk or network error.
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3043
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 3050 - Couldn't lock file
  This error occurs when HelpMaster Pro is unable to create or modify the required database locking file ("databasename".lbd) upon database logon.  This can be caused by a permissions problem or possibly by a corrupt locking file after a database connection is suddenly lost.
  Error Code:3050
  Date Created:10/05/2000
  Last Updated:10/05/2000
  


• Error 3075 - Syntax error (missing operator) in query expression.
  This error may be experienced when attempting to import existing data into HelpMaster Pro.  It is caused by the presence of quotation marks in the import file (*.csv).
  Error Code:3075
  Date Created:14/04/2000
  Last Updated:14/04/2000
  


• Error 3078 : The Microsoft Jet database engine cannot find the input table or query 'tblMessages'. Make sure it exists and that its name is spelled correctly.
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3078
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 3112 : Record(s) can't be read; no read permission on <database file>.
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3112
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 3159 - Not a valid bookmark
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3159
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 3170 "Couldn't find installable ISAM"
  Error number 3170 - "Couldn't find installable ISAM" may occur when attempting to import data into HelpMaster Pro.
  Error Code:3170
  Date Created:2/10/2001
  Last Updated:2/10/2001
  


• Error 3197 : The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3197
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 32014 or 32021 "Unknown Recipient" or "Ambiguous Recipient" Error Message When Sending E-mail
  Some users may experience the above error when sending E-mail from HelpMaster Pro.  It is caused when the E-mail address used is not a full valid address and the addressee cannot be found in your address book, or the address is inconclusive/ambiguous. For example: If you were to try to send an E-mail to 'John' from within HelpMaster Pro, and no entry for 'John' was found at all in your address book you would receive an "Unknown Recipient" error message. If you were to try to send an E-mail to 'John' from within HelpMaster Pro, and two 'John' entries were found in your address book you would receive an "Ambiguous Recipient" error message.
  Error Code:32014
  Date Created:27/02/2001
  Last Updated:27/02/2001
  


• Error 32014 or 32021 "Unknown Recipient"or "Ambiguous Recipient" Error Message When Sending E-mail
  Some users may experience the above error when sending E-mail from HelpMaster Pro. It is caused when the E-mail address used is not a full valid address and the addressee cannot be found in your address book, or the address is inconclusive/ambiguous. For example: If you were to try to send an E-mail to 'John' from within HelpMaster Pro, and no entry for 'John' was found at all in your address book you would receive an "Unknown Recipient" error message. If you were to try to send an E-mail to 'John' from within HelpMaster Pro, and two 'John' entries were found in your address book you would receive an "Ambiguous Recipient" error message.
  Error Code:32021
  Date Created:4/05/2000
  Last Updated:4/05/2000
  


• Error 3343 : Unrecognized database format <database file>
  A corrupt database is typically caused when HelpMaster PRO was improperly shut down during the process of writing to disk during a database transaction. This usually occurs during a power loss or fluctuation, drive or network failure, system crash or any other abrupt system shutdown. These actions can corrupt the HelpMaster Pro database.
  Error Code:3343
  Date Created:5/07/2000
  Last Updated:10/08/2001
  


• Error 339 Component 'CRYSTL32.OCX' not correctly registered: file is missing or invalid.
  The installation program for HelpMaster Pro usually registers all of the required files. On occasion, this fails for various reasons.
  Error Code:339
  Date Created:10/04/2000
  Last Updated:10/04/2000
  


• Error 429 - ActiveX component can't create object
  All Windows-based software, including HelpMaster PRO rely on many different files in order to work correctly. These files are usually installed on your system during the installation process. Some of the file types that HelpMaster Pro uses are : * Executable files that have a .exe file extension, * Dynamic Link Libraries that have a .dll file extension, * OCX, WAV, + many other file types. If any of the required files that HelpMaster Pro uses are deleted, renamed, corrupted, or over-written by other versions of the file, HelpMaster Pro may stop working and produce errors like this one.
  Error Code:429
  Date Created:10/04/2000
  Last Updated:10/04/2000
  


• Error 50030 - Unexpected Error
  An Unexpected Error message will be displayed at application start-up, if a single computer is attempting to run more than one instance of the HelpMaster Pro v5 application. Usually indicates that a system file such as an .ocx or .dll file is corrupt, the wrong version, or is conflicting with another version of itself elsewhere on the system. For some files, it has been due to invalid registry entries. A very tough bug to track down! May also occur if just the HelpMaster Pro .exe file is copied from one machine to another, (or from the PRD Website) without running the complete installation program.
  Error Code:50030
  Date Created:9/06/2000
  Last Updated:9/06/2000
  


• Error 53 - File Not Found. May occur when attempting to run custom reports
  HelpMaster Pro requires a text file called "reports.txt" to be available in the "reports5" directory, found under the directory in which your HelpMaster Pro database resides, in order to run your custom reports created with Seagate Crystal Reports. If this file is missing the above error will occur
  Error Code:53
  Date Created:3/06/2000
  Last Updated:3/06/2000
  


• Error 76 - Path not found
  HelpMaster Pro v4 requires that a folder called “Reports” is located in the same directory as the HelpMaster Pro database file (hmpro.mdb). This folder contains all of the Crystal Report files (.rpt).
  Error Code:76
  Date Created:9/06/2000
  Last Updated:9/06/2000
  


• Error 80004005 Unspecified Error
  "Provider Error '80004005' unspecified error" may appear when attempting to logon to the HelpMaster Pro Staff Web Interface.
  Error Code:80004005
  Date Created:11/07/2001
  Last Updated:18/12/2001
  


• Error Number : 3029 Not a valid account name or password.
  The above errors may occur when attempting to logon to HelpMaster Pro. It may be caused by having an incorrect security file in the HelpMaster Pro database directory, or by changing the password for the security file (System.mdw). This is usually done via "User and Group Accounts" under "Security" in the "Tools" menu of Access 2000.
  Error Code:3029
  Date Created:31/01/2001
  Last Updated:31/01/2001
  


• Error Number : 32002 Unspecified Failure has occurred.
  There are two known possible causes of this error. The above error may occur when attempting to send E-mail through HelpMaster Pro. HelpMaster Pro attempts to send all E-mail through your systems default MAPI compliant mail system. This error can occur if your chosen E-mail system has not been set as the default MAPI client for your PC and the current default MAPI client is not correctly configured. Sending a blank E-mail with an attachment.
  Error Code:32002
  Date Created:31/01/2001
  Last Updated:31/01/2001
  


• Error Number : 35602 Key is not unique in collection
  Error Number : 35602 "Key is not unique in collection". May occur at various stages during use of HelpMaster Pro. E.g. when attempting to attach an asset to a job
  Error Code:35602
  Date Created:5/04/2001
  Last Updated:5/04/2001
  


• Error Number 1000 - Job record not found
  This error occurs with HelpMaster Pro v5.0.12 and earlier. Please note that the combination of events required to produce this error occur very rarely in day-to-day work flow, and as such this error is unlikely to create any significant disruption to HelpMaster Pro users.   The vast majority of HelpMaster Pro users will never experience this error.
  Error Code:1000
  Date Created:10/04/2001
  Last Updated:10/04/2001
  


• Error Number 3028 - Can't start your application. The workgroup information file is missing or opened exclusively by another user.
  The above error may be produced when you start HelpMaster Pro or attempt to log onto a database from the "Open Database" screen.  This error is most common after copying or moving a database to a new directory.
  Error Code:3028
  Date Created:3/07/2000
  Last Updated:3/07/2000
  


• Error Number 3167 - Record is deleted or Error Number 3075 - Syntax error (missing operator) in query expression
  The above errors may occur when attempting to import data from a csv (coma separated value) text file.  Both errors may be produced if SQL reserved characters are found in the data to be imported.Reserved characters include " and ' Error Number 3167 is known to occasionally occur when an attempt is made to import a very large number of records at one time.
  Error Code:3167
  Date Created:3/07/2000
  Last Updated:3/07/2000
  


• Error Number 713 - "Application-defined or object-defined error" when generating standard reports
  When attempting to produce standard reports, just after pressing the "View Report" button, users may experience error "Error Number : 713" with "Error Description : Application-defined or object-defined error". The report will then fail to generate.
  Error Code:713
  Date Created:14/05/2001
  Last Updated:14/05/2001
  


• Error Number 91 - Object variable or With block variable not set.
  The above error may be produced when you start Priority Manager
  Error Code:91
  Date Created:3/06/2000
  Last Updated:3/06/2000
  


• Error Number: 430, Error Description: Class does not support Automation or does not support expected interface
  Error 430 occurs when HMP6 is run and attempts to utilize an MDAC2.6 function
  Error Code:430
  Date Created:7/05/2003
  Last Updated:7/05/2003
  


• Error Number:5 Invalid procedure call or argument prdDatabase.LoadDatabase
  The above error is produced upon starting HelpMaster Pro
  Error Code:5
  Date Created:1/06/2000
  Last Updated:1/06/2000
  


• Error: -2147467259 - [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
  When attempting to Log On using the Client Web Interface you may encounter the above error. This indicates that the Client Web server doesn't have System TEMP Variables assigned.
  Error Code:-2147467259
  Date Created:18/12/2001
  Last Updated:7/05/2003
  


• Fixing a Troublesome Web Interface Installation - Things to Check and Try
  Most of the issues we have experienced to date have fallen into two categories: Permissions DLLs There are a number of steps you can take to address these common problems, and confirm if they are behind the difficulty you are experiencing.
  Error Code:n/a
  Date Created:11/01/2001
  Last Updated:11/01/2001
  


• Green icons
  Occasionally, under rare circumstances you may notice that the icons in your tool bar have turned green .
  Error Code:n/a
  Date Created:9/03/2001
  Last Updated:9/03/2001
  


• HelpMaster Pro freezes or closes automatically after logon
  HelpMaster Pro may freeze or close itself automatically after pressing the Logon button on the Logon screen.  If you have the "Tip of the Day" feature enabled it may partially appear before freezing.  The program can be stopped by ending it's task in the Windows task list.
  Error Code:n/a
  Date Created:27/02/2001
  Last Updated:27/02/2001
  


• How to check which version of the Microsoft Data Access Components is installed
  The easiest way to determine the version of MDAC is to right click on C:\Program Files\Common Files\System\ado\msado15.dll, select Properties, and then consult the Version information. The version information has the same format as that of the FullInstallVer value -- x.xx.yyyy.y, where x.xx is the version number. An alternative way to determine the version of MDAC you’re using is to consult the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess registry key. The FullInstallVer key provides a value of the form x.xx.yyyy.y, where x.xx is the version number (e.g., if the FullInstallVer value were 2.70.7713.0, it would mean that MDAC 2.7 is installed on the system). For the most comprehensive way to check which version of MDAC is installed, you should unzip and run the Microsoft utility "MDAC Com Check", filename is "cc.exe". This utility can be found in the "...Extras\MDAC\MDAC_Component_Checker" folder of your HelpMaster Pro V6 installation CD, or downloaded from the Microsoft web site.
  Error Code:n/a
  Date Created:7/05/2003
  Last Updated:7/05/2003
  


• How to detach a database if using MSDE 2000
  MSDE 2000 is not distributed with any ‘user friendly’ management tools, therefore PRD Software provides the MSDE Wizard to configure MSDE 2000 and attach a database for use with HelpMaster Pro V6. To detach an SQL database from MSDE 2000, the OSQL utility must be run from the Command Prompt and a T-SQL statement must be entered to perform this operation.
  Error Code:n/a
  Date Created:14/05/2003
  Last Updated:14/05/2003
  


• How to Install HelpMaster Pro 6 Reports
  When Helpmaster Pro v6 installs, the reports feature is not automatically installed with it.
  Error Code:n/a
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• How to open the HelpMaster Pro database in Microsoft Access
  Microsoft Access is a third party tool that can be used to write custom reports for HelpMaster Pro.  This Knowledge Base article explains how to open your HelpMaster Pro database with Microsoft Access.  Once you have opened the database you can create any custom reports you may require.
  Error Code:n/a
  Date Created:10/04/2000
  Last Updated:10/04/2000
  


• IIS and SQL Authentication
  If a SQL Server login is defined in the connection string, and it can successfully access the database, then it doesn't matter if the login used in IIS for Anonymous Authentication hasn't been assigned permissions to the database. The connection string will grant access to the database regardless. However, if the connection string is defined to use Integrated Security, it will look for the current login to authenticate with, and will use the login provided by IIS. In this case, if using Anonymous Authentication, the login defined will need to have been given access to the database. If using the 'sa' SQL Server login in the connection string, giving explicit rights to the login being used by IIS will not have any affect. However, the 'sa' account should obviously have rights to the database as well. Using a login and password in the connection string means they are available as plain text from the XML file where the settings are saved. This is OK if the XML file is not accessible.
  Error Code:n/a
  Date Created:28/05/2003
  Last Updated:28/05/2003
  


• Knowledge Base columns dissapear
  This problem is caused when a knowledge base article is opened for a detailed view, and while this is open, the master knowledge base list screen is closed. The column sizings get confused and disappear. All of the column widths are stored in the system registry.
  Error Code:n/a
  Date Created:9/06/1999
  Last Updated:9/06/1999
  


• Microsoft Access: You don't have the necessary permissions to use the 'DatabasePath\DatabaseName.mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you.
  This Article explains a resolution to a Microsoft Access problem with HelpMaster PRO.
  Error Code:n/a
  Date Created:21/03/2001
  Last Updated:21/03/2001
  


• Minimum SQL Access Permissions
  When using Windows NT/Integrated authentication in the connection string to HelpMaster Pro V6’s SQL database, the following minimum SQL Server database permissions are required for all SQL database logins. In the Database User Properties screen, the user requires the db_datareader and db_datawriter database roles to be enabled. This provides the access to read and write data for all the tables. In addition, the user will need to be given Execute permissions for the stored procedures in the HelpMaster Pro 6 database. To do this from SQL Server Enterprise Manager: From the Database User Properties screen, click the Permissions button. Scroll down the list of objects and find the stored procedures. They will be grouped together, and all start with 'sp' or 'stp'. There are 11 of them. Enable the 'Exec' permission for each one. This should be all the rights required. It may be easier, rather than applying them separately to each user, to apply them to a domain group. Another alternative is to create a new database role with what you need.
  Error Code:n/a
  Date Created:28/05/2003
  Last Updated:28/05/2003
  


• No notification E-mails are being sent from the Client or Staff Web Access modules via the SMTP Server
  When attempting to send a Staff or Client notification email from the Client or Staff Web Access modules, the emails are not sent and no error message appears. See Fig.1.
  Error Code:0xC00402CE
  Date Created:7/05/2003
  Last Updated:12/11/2002
  


• Outlook Security Messages: External application trying to access outlook address book
  Sending emails from HmPro6, and getting messages from Outlook saying there is an external application that is trying to access the Outlook address book.
  Error Code:n/a
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• Page not loading correctly: Error: Object doesn't support this property to method: 'document.all.item(...).Nodes'
  When logging a new Help Request with the Staff Web Interface the error "A Runtime Error has occurred. Do you wish to Debug? Line: xxx Error: Object doesn't support this property to method: 'document.all.item(...).Nodes'" may appear. Please note these script errors will only be displayed if the "Disable Script Notification" checkbox is not checked. On computers that have "Disable Script Notification" checked only a small error icon will be shown in the lower left-hand corner of the web browser.
  Error Code:n/a
  Date Created:30/03/2001
  Last Updated:30/03/2001
  


• Repair and Compact Database Utility
  Some corrupt databases are unable to be fixed by either HelpMaster Pro, or Microsoft Access. Usually this is indicated by the following error when trying to compact or repair the database : Error: 3112 Description : Record(s) can't be read; no read permission on Microsoft have released an standalone, updated version of the compact and repair database utility that features advanced database recovery techniques.
  Error Code:n/a
  Date Created:5/07/2000
  Last Updated:5/07/2000
  


• Runtime error '-2147190909 (80047783)' No export DLLs found
  When attempting to export a report the above error may occur. The indicates that the original installation did not work correctly, or there was a conflict when registering some of the required exporting DLL files.
  Error Code:80047783
  Date Created:9/06/2000
  Last Updated:9/06/2000
  


• Runtime error '-2147190909 (80047783)' No export DLLs found
  When attempting to export a report the above error may occur. The indicates that the original installation did not work correctly, or there was a conflict when registering some of the required exporting DLL files.
  Error Code:-2147190909
  Date Created:9/06/2000
  Last Updated:9/06/2000
  


• Setting up SQL Server for full-text Searching to work within HelpMaster Pro Enterprise Edition
  With Helpmaster Pro Enterprise Edition's full-text search interface, you have the ability to search all text fields of the five primary entities being: 1. Clients 2. Sites 3. HelpDesk Jobs 4. Actions 5. Knowledge base Articles
  Error Code:n/a
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• The following recipient(s) could not be reached: No transport provider was available for delivery to this recipient.
  The above "bounced" E-mail message is received in the inbox of the E-mail profile used by Priority Manager.
  Error Code:n/a
  Date Created:18/07/2000
  Last Updated:27/02/2001
  


• Tips and Techniques for Installation
  This article gives instructions for installing HelpMaster PRO
  Error Code:n/a
  Date Created:10/01/2001
  Last Updated:1/05/2001
  


• Tips for Updating to the Latest Version of HelpMaster Pro
  This article instructions and advice on updating HelpMaster PRO.
  Error Code:n/a
  Date Created:10/01/2001
  Last Updated:1/05/2001
  


• Unable to display the Help file.
  HTML Help files can not be opened either by pressing the F1 key within the application, or by attempting to open the help files directly (*.chm files)
  Error Code:n/a
  Date Created:19/07/1999
  Last Updated:19/07/1999
  


• Understanding reports within HelpMaster Pro v5.
  HelpMaster Pro uses two different types of reports; Built-In Reports and Custom Reports. The HelpMaster Pro v5 database structure has changed significantly since v4. Customers that have existing v4 custom reports (or custom web-based solutions) should take this into consideration when upgrading from v4 to v5.
  Error Code:n/a
  Date Created:16/01/2001
  Last Updated:16/01/2001
  


• Updating Reports.txt After Creating A Custom Report
  When you create a custom report with Seagate Crystal Reports that you wish to use from within HelpMaster Pro you need to let the program know a few details about the report you have created.  This simple process involves updating a text file.
  Error Code:n/a
  Date Created:15/05/2001
  Last Updated:15/05/2001
  


• Upgrading to a new version of HelpMaster Pro Enterprise Edition (v6.0.xxxx)
  When a new version or maintenance release of Helpmaster Pro Enterprise Edition (v6.0.xxxx) is available, use the following procedure if there is already an instance of HelpMaster Pro Enterprise Edition installed on the computer.
  Error Code:n/a
  Date Created:14/08/2003
  Last Updated:14/08/2003
  


• Web Module Error 3709
  When attempting to login through the Staff or Client Web Access module, you may receive an error 3709. This error is due to insufficient permissions to the SQL database for the IIS Anonymous Authentication user account, or the logged in user if using Integrated Authentication.
  Error Code:3709
  Date Created:28/05/2003
  Last Updated:28/05/2003
  


• Writing Custom Reports
  The purpose of this page is to help customers and consultants develop their own custom reports for HelpMaster Pro.  Many software packages may be used to create custom reporting solutions. If however you choose to use Crystal Reports ( by Seagate Software ), HelpMaster Pro will allow you to view these custom reports from within the HelpMaster Pro application itself. The "Report Filter" may not be used with custom reports - only the built in reports.
  Error Code:n/a
  Date Created:17/08/2000
  Last Updated:17/08/2000