Failure of Package install due to existing temporary directories and files

Date:21 December 2006
Product/Release:Visual LANSA V11
Abstract:Existing temporary files can cause unexpected package installation errors
Submitted By:LANSA Technical Support


It has been found that some Deployment Tool Package installs that have been created with Visual LANSA V11 may encounter problems due to conflicts with temporary files that have been created during previous application installs.

The problem is that during the install, when the user is defining details in the setup, they may encounter the following error:

Error Message: InstallSheild can not call DLL function: GetDlgItem

Other possible symptoms include:

  • Setup will start installing a different package to that being installed (i.e. it will start reinstalling a previously installed package)
  • Setup will attempt to install an EPC which was already installed by a previous package
  • Details on the summary screen that do not match the package being installed


This is generated by the fact that there are existing temporary directories present when the setup program starts. When user xyz installs an application that has been created by a previous version of Visual LANSA (V9.0 or V10.0), it will create the subdirectory:

C:\Documents and Settings\xyz\Local Settings\Temp\{C3C631B7-5B9E-11D5-BC1A-0001034063E1}

When a new application is being installed, it will not recreate the subdirectory, instead reusing the existing _isuser.dll of the older version. There are many changes in _isuser.dll from version 9 to 10 and from 10 to 11, and the error occurs because of the inconsistence between the install code (new) and _isuser.dll (old ).


If this error message shown above is encountered, they may press OK on the message both times (the error appears twice) and then continue on with the install.

The correct way to avoid this issue occurring all together is, before installing the application to the PC, go to the location C:\Documents and Settings\xyz\Local Settings\Temp\ and then delete the {C3C631B7-5B9E-11D5-BC1A-0001034063E1} directory.

The application can then be installed normally.