Visual LANSA Resolved Issues

Page 1 of 4

• Using PDF viewer 10.1.1 with LANSA Framework could cause the instance list and filter to disappear.
  - Visual LANSA Framework - V12 SP1
  In regions where the decimal separator is a comma (,) installing Adobe PDF viewer version 10.1.1 can cause Visual LANSA Framework filters and the instance lists to disappear.
• Mobile Broadband software can cause LANSA communications and Debugger to fail
  - Visual LANSA V11 & V12
  Some Mobile Broadband (wireless data dongle) software can make changes to the TCP/IP stack, causing the problems with the listener and VL debugger
• Missing C++ Runtime causes installation and runtime failures
  - Visual LANSA V11 & V12
  Missing C++ runtime file MSVCR71.dll can cause Deployment Tool installations to fail during the loading of file data, and/or runtime failures that refer to missing application DLLs (which do exist)
• V12 LANSA install fails when creating an Oracle DSN
  - Visual LANSA V12
  Oracle Patch required to prevent the failure of a LANSA V12 install to an Oracle 11.2.0.1.0 database
• Message stating LPCMN.BND not found when executing RDMLX function/WAM/Component on iSeries
  - LANSA V12
  LANSA can issue an error stating LPCMN.BND is missing even though it does exist.
• VLF component DW_T01.DLL is incorrectly recognized as a virus by some anti virus software
  - Visual LANSA Framework All Versions
  Some anti-virus software incorrectly flag a LANSA shipped DLL (DW_T01.DLL) as a potential virus or unwanted program during a Visual LANSA installation.
• VF_AC006 module is not found error during deployment of VLF application
  - Visual LANSA Framework V12
  Deploying a VLF application from V12, you may encounter an error on some PCs that VF_AC006 module cannot be located or is not a LANSA component.
• Export lists not created even when selected in the Deliver To
  - LANSA V12
  After enabling the Create Export List in Deliver To the export list isn't created.
• Compatibility error when installing V12 on Windows 7
  - Visual LANSA V12
  Error "LANSA requires this operating system to have at least SP1 installed" when installing V12 on Windows 7.
• Windows firewall can prevent V12 Visual LANSA network client from accessing SQ Server database
  - Visual LANSA V12
  To access an instance of the SQL Server Database Engine through a firewall, you must configure the firewall on the computer running SQL Server to allow access.
• Microsoft updates can cause the Sentinel dongle driver to not be recognized
  - Visual LANSA All Versions
  Applying Microsoft Vista updates can cause the Sentinel dongle driver to no longer be recognized by Visual LANSA.
• Additional "Frameworks" & "Groups" are added into partition definitions from VLF_SV11
  - Visual LANSA V11 SP5 EPC843
  EPC843 imported extra "Frameworks" & "Groups" into a partition. This is now fixed in the latest version of EPC843.
• Upgrading Network Clients to V12 - manual intervention may be required
  - Visual LANSA V12
  Network client issues due to missing Visual C++ 2008 Redistributable.
• Altering the Network Library for Visual LANSA V11 SP5 and above
  - Visual LANSA V11 SP5 and above with SQL Server 2005 or SQL Server 2008
  Options regarding altering the Network Library for Visual LANSA V11 SP5 and above.
• Visual LANSA installation ends abruptly with no error messages
  - Visual LANSA V11 SP5
  If correct privileges are not held by the installer, Visual LANSA installation will not complete correctly.
• Language codes used for multilingual partition languages
  - Visual LANSA All Versions
  Language codes used in Partition Languages are not arbitrary and must conform to certain guidelines.
• After applying EPC845, using host monitor will show 'Connect to LANSA System' prompt
  - Visual LANSA V11 SP5
  After applying EPC845, using host monitor will show 'Connect to LANSA System' prompt and connection will fail.
• Installing a Deployment tool package can issue an 'FTP Server not found' error
  - Visual LANSA
  When installing a Deployment Tool package, the installer generates an error that the "FTP Server was not found.[87]".
• Multiple CPYTOIMPF or CPYFRMIMPF commands fail when run in an RDMLX partition in SP5
  - LANSA for iSeries V11 SP5
  A change in V11 SP5 causes multiple CPYTOIMPF or CPYFRMIMPF commands to fail when run in an RDMLX partition.
• Error when attempting to open files after applying EPC837
  - Visual LANSA
  Fatal error when attempting to open files after applying EPC837. This issue was introduced in EPC837. A fix has been delivered in EPC838.
• JIT Upgrade and Deployment Tool additional application icons
  - Visual LANSA V11 SP5
  Some considerations to be noted if using additional icons in an application that is upgraded by JIT application upgrades.

Page 2 of 4

• IDE crash when editing XSL Source
  - Visual LANSA V11 SP5
  IDE ends with a fatal error while editing XSL Source.
• *BLDNO error when running host monitor or system initialization
  - Visual LANSA V11 SP5
  *BLDNO error when running host monitor or system initialization after applying EPC830 to V11 SP5.
• How to restore the button captions of an error message window
  - Visual LANSA V11
  How to restore the button captions of an error message window.
• GET_SESSION_VALUE with the key USER returns exact case which can lead to problems for login or data retrieval
  - Visual LANSA V11 SP4
  GET_SESSION_VALUE in V11 SP4 return USER key in exact case.
• Weblets missing from the Weblet Templates View
  - LANSA for the Web V11 SP4 and above
  Misunderstanding the differences between the Weblet Templates list and the Weblets list in the IDE from V11 SP4 onwards might make it appear that some Weblets are missing from the one or the other lists.
• Unexpected results from Check_Authority BIF - making use of the GUSR setting
  - Visual LANSA V11
  In Version 11 the Group User setting is now used as a supplementary method of determining authority on VL, and this may affect existing applications.
• Applying SP4 to V11 re-introduces correct tabsheet behaviour when the order of tabsheets is changed
  - Visual LANSA V11 SP4
  Applying SP4 to V11 re-introduces correct tabsheet behaviour when the order of tabsheets is changed.
• Sybase EBF 3581 for ASA 9.0.2 causes security error logging into Visual LANSA IDE
  - Visual LANSA V11.x
  Sybase EBF 3581 for ASA 9.0.2 causes security error logging into Visual LANSA IDE.
• RAMP works in designer mode but not in user mode
  - Visual LANSA Framework - RAMP
  Known reasons for a RAMP application working OK in designer mode but not in user mode.
• Valid reason for the 'Cannot resolve to object' error message in Joblog
  - LANSA V11.3
  The message "Cannot resolve to object..." in an iSeries joblog may not always indicate a problem.
• Error connecting LANSA Client V11.3 to deployed Windows LANSA application
  - Visual LANSA V11.3
  Even if your application is deployed with LANSA Client support, LANSA Client may display an error message when attempting to create a new query.
• Error "(0001) - The partition name must be specified in the x_run command" when attempting to do an Import
  - Visual LANSA V11.3
  The location of the Windows user's temporary directory can affect LANSA Imports if the user has an apostrophe in their name.
• Fatal Error Invoking VisioEvent when starting Logical Modeler
  - Visual LANSA V11.3
  After removing a LANSA configuration or installing a new configuration, Logical Modeler may not be able to start due to corrupted registry entries.
• Checking in a process does not update the function control table on iSeries
  - Visual LANSA V11.3
  Changes to the Function Control Table in VL not updated on iSeries after checking in Process.
• DEFINE_ANY_SERVER and translation tables
  - Visual LANSA V11.3
  Using the DEFINE_ANY_SERVER BIF for SuperServer RDMLX connections and specifying translation tables.

Page 3 of 4

• Windows Help (.hlp) files no longer supported from Vista onwards
  - Visual LANSA
  Microsoft will no longer supply the Windows Help reader in Vista which can affect LANSA developed application that uses Winhelp.
• An *EPCCHK error when using *JOB *JOB as Translation Tables in VLF
  - Visual LANSA V11.3 and Visual LANSA Framework EPC804
  An EPCCHK error is generated when using *JOB *JOB for Translation Tables in language English.
• How to reset the LANSA IDE back to its shipped default settings
  - Visual LANSA V11.3
  How to reset the Visual LANSA IDE back to its shipped default settings.
• 3rd party software causes LCOTP.exe to fail
  - Any LANSA application or product using the local LANSA listener
  LCOTP.exe job fails immediately after connecting to local listener due to 3rd party LSP DLLs.
• An error 'UINUSERGROUP is null or not an object' is displayed when running a Visual LANSA Framework application
  - Visual LANSA Framework EPC793
  An error is displayed when running the Framework with User Groups defined.
• Failure of Package install due to existing temporary directories and files
  - Visual LANSA V11
  Existing temporary files can cause unexpected package installation errors.
• Deployed application never starts
  - Visual LANSA V11.3
  Deployed Visual LANSA application never starts application execution.
• Copied packages are built into the wrong location
  - Visual LANSA Deployment Tool
  When using the copy process the application is built into the wrong destination.
• Menu options grayed out after applying CU3 to a V11.0 environment
  - Visual LANSA V11.3
  Performing a Visual LANSA upgrade while running some VL applications can cause some Visual LANSA menu options to be disabled or unavailable.
• Cannot start Visual LANSA on Server due to disabled Terminal Services service
  - Visual LANSA V11.0
  Error generated when starting Visual LANSA on Server PC due to Terminal Services service being disabled.
• Automatic crossed updates checking is not working correctly in V11.0 with C OAMs
  - LANSA V11.0
  Automatic crossed updates checking is not working correctly in V11.0 with C OAMs.
• Deployment Tool does not recognise Components correctly, lists them as regular fields Visual LANSA V11.0
  - Visual LANSA V11.0
  The presence of old Internal File OAMs will cause the Deployment Tool to list all components/forms under fields.
• 'Read Only' shared drives on Windows servers stops Visual LANSA Network Clients connecting to server
  - Visual LANSA All Versions
  Shared drives or directories on newer windows operating systems are created with "Read only" permission, which affects Visual LANSA network clients connecting to the windows server.
• 'Too Many Fields Defined' error on an UPDATE query when using a Microsoft Access Other file with more than 127 fields
  - Visual LANSA V11.0
  An error will occur when attempting to update a Microsoft Access file that has been loaded into Visual LANSA as an 'OTHER' file and contains more than 127 fields.
• Possible issues deploying an application that makes an automatic connection to an RDMLX server
  - LANSA for iSeries V11.0
  Deployment Tool does not give the option to deploy an application that makes an automatic SuperServer connection to an RDMLX iSeries.

Page 4 of 4

• Documentation for Network Client Install does not cover local drive mapping parameter
  - Visual LANSA V11.0
  Documentation for Network Client Install does not include information about the 'Local mapping for the Server's LANSA root directory' install option.
• "QSYSINC library not found" during checkin and compile of RDMLX object on iSeries
  - LANSA for iSeries V11.0
  Error generated during checkin and compile of RDMLX object (eg. WAM) caused by IBM QSYSINC library not installed.
• Incorrect database type selected by default during Visual LANSA V11.0 Slave installation
  - Visual LANSA V11.0
  Visual LANSA Typical Slave or Typical Multiple Products Install will select ASA Client/Server database by default, which can cause problems with duplicate Server Names.
• Missing Liiiconfig.txt error when installing EPC759
  - Visual LANSA V11.0
  Missing Liiiconfig.txt error when installing EPC759 on a PC with multiple Visual LANSA V11.0 configurations.
• Updated driver for USB dongle
  - Visual LANSA
  If the USB dongle is not being recognized, applying the latest dongle drivers from Sentinel may resolve the issue.
• Windows administrator rights is required for Network Client Machines
  - Visual LANSA
  You need Windows administrator rights to access the Network Server from a Network Client machine.
• Microsoft HotFix KB891781 causes Visual LANSA Framework problems when editing RAD-PADs
  - Visual LANSA Framework
  Applying a Microsoft Hot fix can cause the RAD-PAD to crash.
• JIT may not install packages in order expected
  - Visual LANSA
  JIT packages not installed in order expected.
• .RRN files must exist in central location for Shared Server Database
  - Visual LANSA
  .RRN files must exist in central location for shared server databases otherwise duplicate errors will occur
• Potential problem when deploying Visual LANSA application with Other files to different DSN
  - Visual LANSA
  Deployed Other files will include the DSN name which can cause application errors on target PCs.
• Deploying an application compiled with Visual Studio .NET C++
  - Visual LANSA V10.0
  If you are using Visual Studio .NET to compile your RDML, you will need to package the extra C Runtime DLLs for .NET. when you ship your developed applications.
• Use SELECT with keys that are not Alphanumeric
  - Visual LANSA
  Generic search using numeric keys in the SELECT command ends with SQL ODBC errors.
• Error PRR0074 in SuperServer applications
  - LANSA for Windows
  PRR0074: Communications operation attempted without a valid connection to SSN &1.
• Pop-Up Menu Cut/Copy/Paste must be manually translated
  - Visual LANSA
  When a pop-up menu is created in Visual LANSA the AutoActions Copy/Cut/Paste property defaults to English text. This can be changed by manually editing the LpVo.bnd file.
• List of error return codes that you may receive when running the SYSTEM_COMMAND built-in function
  - LANSA for Windows
  List of error return codes that can be generated running the SYSTEM_COMMAND built-in function.

Archive

• Duplicate node names in Network Client installs can cause various problems using LANSA
  - Visual LANSA V10.0
  Duplicate node names in Visual LANSA Network Client Installs can cause various locking problems using Visual LANSA.
• Cannot apply EPCs to a Visual LANSA V10.0 configuration in a Client/Server development environment
  - Visual LANSA V10.0
  Generating an error "No configurations exist that can be updated by this EPC" when applying an EPC or installing a new LANSA product/feature to Visual LANSA V10.0.
• Windows XP Service Pack 2 closes ports by default which can cause errors in LANSA applications and products
  - All LANSA products
  Possible errors in LANSA products and applications after applying Windows XP Service Pack 2.
• Error when attempting to modify the appearance of web pages using Form Layout Assistant
  - Visual LANSA Framework
  Explorer's security restrictions does NOT allow the layout of Web pages to be modified when running application in VLF.
• Possible errors in LANSA for the Web on Windows after applying Windows XP Service Pack 2
  - LANSA for the Web and Visual LANSA
  Possible errors in LANSA for the Web on Windows and/or Visual LANSA after applying Windows XP Service Pack 2.
• How to avoid generating a HRESULT error when running the Logical Modeler from a Visual LANSA Network Client
  - Visual LANSA V10.0
  Steps to allow the LANSA Logical Modeler to execute from Network Clients.
• Custom install of Deployment Tool images reverts Visual LANSA to pre-EPC state
  - Visual LANSA V10.0
  Custom install of the Deployment Images from the 10.0 CD reverts Visual LANSA core files to 10.0 GA (pre-EPCs) level.
• Printing reports without LPT1 in Visual LANSA
  - Visual LANSA V10.0
  Previous problem of not being able to print reports without mapping to port LPT1 is resolved in 10.0.
• Issue with Date Stamping when using X_Run parameter DATF
  - Visual LANSA and LANSA for iSeries
  Issue with Date Stamping when using X_RUN parameter DATF.
• Duplicate key errors in Host Monitor – Field Visualisation
  - Visual LANSA V10.0
  Duplicate key errors in Host Monitor for Field Visualisation.
• Newly added fields to a file are not created in ASA
  - Visual LANSA
  Newly added fields are not created in Sybase ASA - only when certain compile options chosen.
• System dates not displaying correct behaviour in Visual LANSA
  - Visual LANSA
  System dates in Visual LANSA are inconsistent with both the documentation and the LANSA for iSeries behaviour.
• Updated driver for USB dongles
  - Visual LANSA V9.1
  If the USB dongle is not being recognized, applying the latest dongle may resolve the issue.
• Hardware key upgrade problem in 9.0 with old dongles
  - LANSA for Windows
  Problem upgrading Hardware Key in 9.0.
• Using OV_WINWORD with Windows 9x and Office 2000
  - LANSA for Windows
  Problems when using OV_WINWORD with Win98 and Office 2000.
• Host Monitor problems if PC name contains dash (-)
  - LANSA for Windows
  Host Monitor will not work if your computer name contains a dash (-).
• Host Monitor fails to start: error LII0028S
  - LANSA for Windows
  Error LII0028S is usually caused by an outbound communications job on the host AS/400 that is still active from a previous Host Monitor session.
• Recreation of I/O Module Fails after a Field has been Deleted
  - LANSA for Windows and LANSA for the AS/400 All Releases
  After deletion of a field from a file definition, the I/O module recompilation fails.
• Using % on the LIKE keyword on SELECT_SQL on LANSA for Windows
  - LANSA for Windows
  Special consideration when using the % wildcard character on the LIKE keyword on the WHERE clause on the SELECT_SQL.
• What objects are displayed in the Check-in list dialog
  - LANSA for Windows
  Criteria by which objects are listed in the Check in dialog.
• Setting Component Properties to their defaults at runtime
  - Visual LANSA
  Setting properties back to their default values at runtime.