Known Issues with ICRFS-Plus™ 10.4
The following list contains the major problems we have been notified of in installing and running ICRFS-Plus™ 10.4 together with fixes. For troubleshooting support relating to ICRFS-Plus™ 10.3, click here.
Please contact support@insureware.com if you need any further help.
Errors are classified by when they appear: Installation Errors, Errors Launching ICRFS-Plus, Errors Opening a Database, Errors Opening PTF, Errors closing ICRFS-Plus, Issues with COM and Miscellaneous Bugs. Click on the error graphic to go to the fix.
Updates: Currently no updates are applicable at this time.
Errors Launching ICRFS-Plus
Errors Opening a Database
Errors Closing ICRFS-Plus
Installation Errors
I1. Problems have been encountered when Permissions have been changed on the registry or Temp directory. Ensure that the account you are using for installation has full access rights to the registry and Temp directory.
Errors Running an ICRFS-Plus Licence File
L1. Error message running an ICRFS-Plus licence "Problem in updating registry. Please contact Insureware".
You need to log on to your computer with administrator rights to run an ICRFS-Plus licence file.
Errors Launching ICRFS-Plus
L1. Error message on starting ICRFS "Error #101: Your computer is not licensed to run ICRFS".
Check that the program "licence" (supplied on a floppy disk or CD at the start of the current licence period) has been run. If it has been run, record any message produced by the licence program and send it to Insureware.
L2. Error message on starting ICRFS "Error #103: ... Your computer is not licensed to run ICRFS".
Check that the label on the licence floppy or CD matches the label on the sentinel key. If it does, please contact Insureware.
This problem has also been seen when the sentinel key has been damaged by repeated removal. If you have another sentinel key, check whether the program will launch with the other sentinel key.
L3. Error message on starting ICRFS "Check the Sentinel key.".
Check that the sentinel key is in the parallel port or USB port.
This error can be caused by an incompatibility of the sentinel key driver and the parallel port settings, on Windows XP or 2000, particularly on Toshiba laptops. The internal settings of the computer may need to be changed. Alternatively, a USB sentinel key can be supplied. Please contact Insureware for assistance.
This problem has also been seen when the sentinel key has been damaged by repeated removal. If you have another sentinel key, check whether the program will launch with the other sentinel key.
Errors Opening a Database
O1. Error message on opening an Interbase database: "Database error: Unknown database".
Check that InterbaseForICRFS or Interbase 5.6 has been installed.
This can occur if Interbase 6 or 7 has been installed by some other application. Please check which version of Interbase is installed and contact Insureware.
Occasionally you may also get this message if ICRFS-Plus™ is launched immediately after restarting, if the required system services have not yet started up. Wait for a moment and try to open the database again.
O2. Error message on creating an Interbase database: "Database error: General SQL error".
This can occur if Interbase 7 has been installed by some other application. Please check which version of Interbase is installed and contact Insureware.
O3. Error message on opening an Interbase database: "Unknown user name or password. unavailable database".
Check that InterbaseForICRFS or Interbase 5.6 has been installed.
Occasionally you may also get this message if ICRFS-Plus™ is launched immediately after restarting, if the required system services have not yet started up. Wait for a moment and try to open the database again.
O4. Error message on creating or opening an Interbase database: "Database error: Vendor initialization failed. Cannot load an IDAPI service library. File: GDS32.DLL Alias: theDB_1".
Check that InterbaseForICRFS or Interbase 5.6 has been installed.
This can occur if Interbase 6 or 7 has been installed by some other application. Please check which version of Interbase is installed and contact Insureware.
Occasionally you may also get this message if ICRFS-Plus™ is launched immediately after restarting, if the required system services have not yet started up. Wait for a moment and try to open the database again.
05. Database Error. General SQL Error. Check the username and password are correct.
06. Database Error: Invalid Enum Value.
This error message will occur on opening an MSAccess database if the user is a limited user and the database is stored in the Program Files sub-directory or if the database is read only. Copy the required database from the Program Files subdirectory and place in a limited user accessible directory. For example: C:\Documents and Settings\All Users\.
07. Database Error: Unable to open database.
Check the interbase server is running. Note that if you switch users, you will not be able to open local Interbase databases as the service will be running for the current user only - a restart is required.
Errors Opening PTF
P1. Error message on opening PTF: "External exception C000001D".
This can occur on computers with non-Intel processors. Run ICRFS-Plus™ and choose the menu option Options->Modelling Preferences and deselect Use Intel SPL.
Errors closing ICRFS-Plus 10.4
Windows 2000/XP: This error can occur when you close ICRFS-Plus 10.4 after manipulating a local Interbase database. There are no side effects aside from this message and the problem does not reoccur on a subsequent runs of the system.
Issues with COM
Note on IMptfForecastSetup::GetIndVarMode usage in Version 10.4
The following VBA script fragment for Excel demonstrates the supported usage of IMptfForecastSetup::GetIndVarMode method
Dim objCompRegrMgr As icMptfCom.MptfRegrManager
Dim objForecastSetup As icMptfCom.IMptfForecastSetup
Dim aMode As icModelcm.ForecastVarMode ' create and initialise objCompRegrMgr, estimate a MPTF model
Set objForecastSetup = objCompRegrMgr.GetForecastSetup()
objForecastSetup.SetIndVarMode 1, icmodelcm.MLE ' works OK
aMode = objForecastSetup.GetIndVarMode(0) ' does not compile
objForecastSetup.GetIndVarMode 0, aMode ' use this line instead of GetIndVarMode(0) to get an individual variance mode for a particular segment
' aMode stores the value of the segment 0 variance mode
Note to fix the above, two new functions are introduced as replacer functions in 10.4 COM - please see the COM Reference Guide for the new functions (GetIndividualVarMode and SetIndividualVarMode) and their corresponding documentation.
To resolve this issue, all scripts referencing these functions will need to be updated to refer to: GetIndividualVarMode and SetIndividualVarMode respectively. However, the above work arounds will continue to work in 10.4
Miscellaneous
Some ICRFS-Plus dialogs may not display properly when ICRFS-Plus is run with two monitors - especially when run from the secondary monitor. Solution: only run ICRFS-Plus from the primary monitor.
When creating a report for Office 2007, you will receive a warning
message from when the report is opened unless the extension check in
Office 2007 has been turned off. This is a feature of the extension
changes for Office 2007 and does not indicate any problems with the
ICRFS-Plus report which is saved in Office 97-2003 format.
Data from the triangle PL(I) cannot be read. ...
When this message applies to large triangles (for example both dimensions are greater than 208 periods) in Oracle or SQL databases you may be able to fix the problem by performing the following steps.
Start Control Panel -> BDE Administrator.
Under Configuration double click on Drivers -> Native
-> ORACLE. Change value of "BLOB SIZE" field to 1024.
-> SQL. Change value of "BLOB SIZE" field to 1024.
Select SQL or ORACLE on the left panel and right click button will bring
you a menu, where you click Apply.
Answer "Yes" on the all following questions.
Restart all BDE applications, including ICRFS-Plus.
Patch 1 for 10.4
This patch fixes an error in LRT and ELRF for regional settings where a character other than a period is used to indicate a decimal point when entering data. In the released 10.4 system, for ELRF (to Ultimate) and LRT, the decimal point indicators were ignored when entering data.
LRT selection graphs were not updating after pasting into the industry or judgement rows; this has also been corrected.
No other frameworks are affected.
Patch 1 for 10.4 is available here.













