Version 14 Release and Installation Notices

Service Pack 2 for V14 was released on 11 May, 2018.
Service Pack 1 for V14 was released on 1 August, 2016.
V14 became Generally Available on 16 November, 2015.
This page contains late breaking news and other important information about Version 14 of LANSA. Check back here regularly for all the latest updates.

See the new feature highlights in V14

Re-licensing all LANSA software

EPC142050 for V14 SP2 replaces sentinel development licenses with LANSA development licenses. Contact your local LANSA license representative to obtain a replacement V14 development license before applying EPC142050.
When upgrading to V14 from a previous version of LANSA or when installing a new V14, you will be required to obtain new V14 specific licenses for all LANSA software that required licensing at V13 and prior.
New licenses can be obtained in advance in preparation for a V14 upgrade.
Prior to upgrading to V14, you should send the CPU details of all servers and workstations requiring re-licensing to your LANSA representative for new V14 licenses. Refer to Product Licensing for more details.

Important Notice: From October 2018, LANSA will no longer be offering a hardware key (also known as a dongle) option for development licensing for any version of Visual LANSA. New Hardware key licensing requests and hardware key upgrade requests will instead be redirected to the softkey development licensing options. These include the softkey option for use on a single physical CPU (VLW key) and the License Server option for multiple developers, servers and virtual environments (VLN key). The information in this notice overrides any other existing hardware key information on the LANSA Licensing pages.

Version 14 Quicklinks

Release Notices

Filter by Product Reset

Date	Product	Version	Description
11 July 2023	Visual LANSA	All	Category: Visual LANSA failures after applying Windows 11 and Windows Server 2022 updates Windows 11 update 22H2 and Windows Server 2022 update 21H2 (and above) introduced a new Microsoft DLL, named lxutil.dll. The introduction of this DLL can cause issues for Visual LANSA in the areas of Server Modules (application and API) failing Super Server connection failures LANSA Debug not working All of these areas would have been working OK prior to the Windows updates. LANSA has established what is causing the problem and the fix is scheduled for the next EPCs for the supported versions of LANSA. In the meantime, there is a simple workaround copy \x_win95\x_lansa\execute\lxutil.dll into \Connect copy \x_win64\x_lansa\execute\lxutil.dll into \Connect64 and restart the LANSA listener and reset IIS. This should resolve the issue temporarily until a full solution is shipped in an EPC. If you still encounter this error after trying the workaround above, you should go into your PC temporary directory (open up an explorer window and type %temp% in the address bar), and look for the following 3 files: Summary.txt LansaInstallLogExt.txt LansaInstallLog.txt Also look for any other files in that folder that were created around the same time as those files (check the modified date). Send the files to your local support representative, highlighting what changed in your environment to introduce the issue LANSA and O/S version details (Note: generating the LANSA About is the best source for this information) that you have already attempted the workaround above.
3 June 2022	Visual LANSA	All	Category: Web execution/Partition initialization Upgrading from Windows 10 to Windows 11 introduces web execution 404 errors and partition init import failures for all supported versions of Visual LANSA. If you upgrade from Windows 10 to Windows 11, you can encounter several related problems in Visual LANSA. These errors can occur irrespective of LANSA version or EPC level. The symptoms of the windows 11 compatibility issues are: A web execution error 404 is issued for pages that previously executed OK in Windows 10. Performing a Partition init of any of the options (Mandatory partition initialization/Visual LANSA Framework/WAM development/LANSA Client field and file definitions/Sample Material) will fail for some imports, for example Standard Widgets, Standard Resources, VLF.The import error is: Operating system Error occurred when attempting to perform EXECUTE operations. Connecting to a windows backend server (on Windows 11) in the Web Administrator will give a Connection failed (0x0000001c) error. This compatibility issue has been fixed and the fix will be shipped in the next EPCs for V14 SP2 and V15 respectively. If you have an urgent need for the fix prior to the EPCs being available, you can request a hotfix by contacting your local LANSA support group. Please note that hotfixes are only available for the supported versions of LANSA (V14 SP2 and V15) at the latest EPC level.
18 Feb 2020	Visual LANSA	All versions	Category: Windows Updates New Microsoft System Locale Beta option “Beta: Use Unicode UTF-8 for worldwide language support” can cause System Init failure installing Visual LANSA and can cause data corruption in existing databases, if enabled. For more information, refer to https://lansa.com/support/notes/p0464.html
14 May 2019	Visual LANSA	V14 SP2	Category: Licensing EPC142050 introduces LANSA development licensing. This replaces the existing sentinel development licensing. You will require a new LANSA development license to use Visual LANSA after applying EPC142050. Your existing sentinel development license will no longer be valid. You should request a new replacement Visual LANSA development license from your local LANSA license representative before applying EPC142050 to avoid any development disruption.
27 November 2018	Visual LANSA	V14 SP2	Category: Deployment Tool & EPC142030 After applying EPC142030 to V14 SP2, your next deployment in the Deployment Tool cannot be a patch (MSP). You must deploy the new runtime shipped in this EPC as a version (MSI). Attempting to deploy this EPC as an MSP will generate a fatal error for file overridepackageinstallparameters.txt during the package build.
23 October 2018	LANSA Integrator LANSA Composer	V14 SP2	Category: Java compliance Oracle has announced a date of January 2019 for the Commercial User End of Public Updates for Java 8; any further updates will be available only to Customers and accessible through My Oracle Support and via corporate auto update where applicable. These changes will affect LANSA customers using LANSA Integrator and LANSA Composer so to assist LANSA customers concerned about the impact on their applications, we have updated our Java Compliance statement. Refer to Impacts on LANSA of Oracle enforcing Java compliance
18 May 2018	Visual LANSA	V14 SP2	Category: SQL Server 2017 You may encounter an error "Unable to install SQL Server” when installing SQL Server 2017 from the V14 SP2 Install. This issue is caused by having one of the following programs on your system when installing SQL Server 2017. - MS C++ redistributable 2017 - Visual Studio 2017 It is a known issue with the Microsoft SQL Server Install, as discussed on the Microsoft SQL Server forum https://social.msdn.microsoft.com/Forums/sqlserver/en-US/2ffd27d1-cbfe-4233-9baf-9dc00d0d39a4/unable-to-install-sql-server-setupexe-vs-shell-installation-has-failed-with-exit-code-1638?forum=sqlsetupandupgrade The recommended workaround is to - Uninstall the above program (MS C++ redistributable 2017 and/or Visual Studio 2017) - Start the V14 SP2 install again and install SQL Server 2017 - Install the above program again (MS C++ redistributable 2017 and/or Visual Studio 2017)
31 July 2018	Visual LANSA	V14	Category: Hardware Key licensing After applying Windows 10 update 1803, the hardware key (dongle) is not being recognized when logging into the Visual LANSA IDE. This problem appears to only affect Visual LANSA V14. Downloading the latest hardware key driver from the Sentinel section of the Gemalto web site (https://sentinelcustomer.gemalto.com/ sentineldownloads/) will not resolve the issue. This problem was reported to Gemalto and a fix has been provided and is shipped in EPC142010 for V14 SP2. If your hardware key is still not being recognized after applying EPC142010, do the following Open Windows Services. Locate Sentinel Protection Server service. Right click on the service and Stop it. Go into the Properties for this service and set to Disabled. Click Apply and close Windows Services. Log into VL again. Note: LANSA customers on maintenance can contact their local LANSA representative to obtain a V14 VLW softkey or VLN license server license on returning their hardware key.
11 May 2018	Visual LANSA	V14 SP2	Category: IDE Launching the Visual LANSA IDE without a license has changed in V14 SP2. The LANSA 'read-only mode' has been introduced to allow you to view code and compile objects without a development license. This mode is ideal for build machines. The Demo mode where you could create a limited number of name restricted objects, available in previous versions, has been removed. There is a new evaluation version of Visual LANSA available for download that will enable you to use the IDE unrestricted for a limited time period to replace demo mode.
11 May 2018	Visual LANSA	V14 SP2	Category: Deployment Tool V14 SP2 includes various Deployment Tool enhancements which has made it impossible to support the creation of a Patch (MSP) from a Version which was built prior to V14 SP2. Thus, the next deployment of any kind after installing V14 SP2 must be a Version, not a Patch.
11 May 2018	LANSA for i	V14 SP2	Category: Install The LANSA for i install is delivered as a save file in V14 SP2. The install can no longer be launched directly from the V14 SP2 (spin0335) DVD. The LANSA for i install save file is in a ZIP file on the V14 SP2 (spin0335) DVD. The ZIP file can be extracted from the DVD, the save file unzipped and moved to the IBM i using standard steps and the LANSA install launched using the instructions in the LANSA for i Install guide. The following link provide example instructions from IBM on how to FTP from the IBM i IFS to a save file in QGPL. (Its vital to create the save file in QGPL first) http://www-01.ibm.com/support/docview.wss?uid=nas8N1012624 This change also means that LANSA for i cannot be installed using the Image Catalog instructions provided here.
11 May 2018	LANSA for i	V14 SP2	Category: OSU The Open Systems Utilities (OSU) is no longer shipped from V14 SP2. The OSU utilities was never implemented for RDMLX and is no longer compatible with RDML in later versions of LANSA. Historically, the most commonly used utility was OS@P0003 (High speed partition deletion) but partitions can be deleted from within LANSA housekeeping, without requiring exclusive use of the LANSA system, since LANSA V12.
6 Dec 2017	LANSA Composer	All supported versions	Category: Mapforce Licensing With the recent release of the Altova Mapforce 2018 product line, there has been a change to the licensing model used by Altova. For more information, refer to Impacts on LANSA Composer of Altova Mapforce switch from concurrent licensing to Server licensing
3 Nov 2017	LANSA Composer	All supported versions	Category: Mapforce 2018 Mapforce 2018 has been released by Altova. LANSA has been actively testing Mapforce 2018 with Composer V6.1. This testing has completed without issue. The status of Mapforce 2018 has been updated to Tested OK by LANSA. You can check the versions of Mapforce tested with LANSA Composer (and the version of LANSA Composer) here This section also has the following general reminder: Attention: You should not download and apply any Mapforce Release or Service Pack until it is given an official support status by LANSA. Contact your LANSA Support representative for any Mapforce version support queries.
25 Oct 2017	LANSA Client	All versions	Category: Windows Updates Any LANSA Client queries with output to Excel will generate the following error after applying Windows update KB4041676 This error will occur irrespective of LANSA Client versions or Windows operating systems (after applying the update). The error above is listed in the KB4041676 notes, under the section ‘*Known issues in this update’ with a status of ‘Microsoft is working on a resolution and will provide an update in an upcoming release*.’ Uninstalling the windows update allows the queries to complete successfully with output to Excel. A short-term workaround, if customers don’t want to, or are not in a position to, uninstall the update, is to output to XML and load that XML file into Excel.
13 Sep 2017	Visual LANSA Visual LANSA Framework LANSA for i	V14	Category: Generic Select EPC141031 has introduced a change of behaviour when selecting records from a file using *SELECT ...FROM_FILE(<file>) GENERIC(YES)** whereby no records are returned, even though the criteria for selection is met. This can occur when the file you are selecting from (FROM_FILE) has had its OAM recompiled at EPC141031 or greater level. This issue can also be observed in the VLF after applying the latest EPC141034 (shipped with EPC141050) where a search for VLF users doesn't return any records, even though users exist that match the selection criteria. A patch is available at EPC141050 level to resolve this issue. Contact your local LANSA support group and ask for EPC141050HF_170829 (Visual LANSA) and HF141015 (LANSA for IBM i). Note that these patches come with user actions. LANSA User Action: After applying the patch, recompile the OAM of any application files that you perform generic searches on. VLF specific User Action: After applying the patch, recompile the OAM of the VLF shipped vfppf06 file to generate a new OAM.
26 Jul 2017	LANSA for i LANSA Composer	V14	Category: Upgrade In LANSA V12 SP1, a new COMPOSER_RUN BIF was introduced to facilitate one LANSA system interacting with a separate LANSA Composer system. Upgrading the LANSA V12 SP1 system calling the BIF to either V13 or up to V14 can cause functions using the COMPOSER_RUN BIF command to fail with the following error DCM9999 This BIF is only supported on Microsoft Windows. To overcome this error, you must recompile the failing function in the upgraded LANSA system.
23 Jun 2017	Visual LANSA	V14	Category: Cloud All LANSA Cloud images have been updated. The images that have been updated are: In the AWS Marketplace LANSA Scalable License V14 SP1 EPC 141031 compatible with the deployment of applications built with Visual LANSA V13 SP2 Visual LANSA Development Environment Web application framework Win2012 V14 SP1 EPC 141031 Visual LANSA Development Environment Web application framework Win2016 V14 SP1 EPC 141031 In the Azure Marketplace LANSA Scalable License V14 SP1 EPC 141031 Visual LANSA Development Environment Web application framework Win2012 V14 SP1 EPC 141031 If you assigned an IAM role to the instance when you created it, you may upgrade your current instances in situ.
22 Jun 2017	Visual LANSA	V14	Category: Cloud LANSA is aware of active attacks leveraging CVE-2017-8543, Windows Search Remote Code Execution Vulnerability. All LANSA’s images which are published in AWS Marketplace and Azure Marketplace have been checked that they are not vulnerable to this attack.
17 May 2017	LANSA for i LANSA for the Web	All	Category: Performance IBM PTF available for Mutex wait (MTXW) issue that can affect performance of LANSA applications. LANSA customers who have large systems involving many thousands of LANSA runtime jobs have sometimes reported a slowing down in performance of the LANSA jobs due to a Mutex Wait (MTXW) situation. Refer to Performance slowdown in LANSA applications caused by Mutex wait issue
4 May 2017	LANSA for i LANSA for the Web	V14 & V14 SP1	Category: Web Server LANSA for the Web will stop working after upgrading the O/S from 7.1 to 7.2 or 7.3 After an Operating System upgrade from 7.1 to either 7.2 or 7.3, the HTTP server instance for V14 or V14 SP1 will not start and a HTP8016 error will be logged in the http joblog. A patch is available from LANSA that will install a 7.2/7.3 ready version of the Apache Module. A different patch is required depending on whether you are on V14 GA or V14 SP1. Contact your local LANSA Support group and request the patch appropriate to your version of LANSA V14. V14 SP1: HF141001.zip or V14 GA: HF140005.zip
10 Feb 2017	LANSA for i	V14	Category: Checkin/Compile If you encounter the error - LIBRARY QSYSINC NOT FOUND during checkin and compile to the IBM i, the most likely reason is that some C compiler options are missing. We suggest you install (reinstall) the 5722SS1 Option 13 "System Openness Includes". Licensed Product Program Option Description 5770SS1 BASE IBM i 5770SS1 1 Extended Base Support 5770SS1 2 Online Information 5770SS1 3 Extended Base Directory Support 5770SS1 8 AFP Compatibility Fonts 5770SS1 12 Host Servers 5770SS1 13 System Openness Includes* As per the advice at http://archive.midrange.com/midrange-l/200510/msg00213.html you should install it from your original OS/400 or i5/OS CDs GO LICPGM Select option 11. Install Licensed Programs Type a 1=Install next to 5722SS1 Option 13, "System Openness Includes" and press Enter
13 Jan 2017	LANSA for i	V14	Category: Install/Upgrade LANSA for i upgrade to V14 SP1 can fail with a message 'FRCOBJCVN value not allowed.'. Refer to Upgrade to V14 SP1 can fail due to FRCOBJCVN value
22 Nov 2016	Visual LANSA	V14	Category: Cloud - Azure LANSA today announces the availability of their first Azure Quickstart template for deploying LANSA applications into a Microsoft Azure stack. https://azure.microsoft.com/en-us/resources/templates/lansa-vmss-windows-autoscale-sql-database/ The template deploys a LANSA MSI developed using the Visual LANSA IDE into a Windows Virtual Machine Scale Set and creates an Azure SQL Database. The Scale Set is initialised with a desired count of Virtual Machines and then the LANSA MSI is installed in each Virtual Machine and sets up the Azure SQL Database. Note: a similar template, which uses a pre-existing database, has been submitted to Microsoft for review. This allows an existing SQL Server Database, Azure SQL Database or MySql database to be used by the LANSA MSI only.
18 Nov 2016	Longrange for RPG/LANSA	All	Category: Longrange 21 January 2017: Apple have extended their iOS HTTPS/ATS implementation deadline from January 2017 deadline to a new undetermined date. This means that for the moment you don’t need anything. Refer to https://developer.apple.com/news/?id=12212016b Despite this extension of the deadline, Apple have made it clear that this implementation will occur. LANSA recommends including a move to HTTPS and ATS into your longer term plans. Original Post: Apple has announced that starting from January 2017, all apps (including LongRange) on the App Store are to use HTTPS (TLS) connection only. Refer to this Longrange forum notice for details https://longrange.lansa.com.au/viewtopic.php?f=13&t=511
7 Nov 2016	LANSA for i	V14 & V14 SP1	Category: Host Monitor/Checkin and Compile A checkin and compile problem has been encountered with the following criteria in place - An RDML physical file which has a key, in an RDMLX partition - Where the master repository is on an IBM i with Operating System 7.3 - The checkin and compile via the host Monitor will fail with an MCH5601 error in the joblog on a MOVOBJ command This has been confirmed as an OS 7.3 issue and an IBM PTF is available to resolve the issue. The PTF is SI62854. This problem is not exclusive to any particular version of LANSA and can occur on all supported versions of LANSA with the master repository on IBM OS 7.3.
22 Aug 2016	Visual LANSA Web	V14 & V14 SP1	Category: WAM Execution The following character set issue, exclusive to IBM i 7.3 operating systems, is caused by an API change in IBM i 7.3. On IBM i 7.3, in a WAM, a text LOB in CCSID 37 is sent as corrupted characters (not transcoded) when using the Internet Explorer browser. Note: In Chrome or Firefox users may experience symptoms of LANSAWEB object being downloaded. The cause of this issue is from changes made in 7.3 to an IBM i’s get attributes API causing failures to retrieve file information (CCSID, timestamps and other properties). There are separate patches available for all LANSA versions supported on 7.3. Please contact your local support team and quote #156463 to obtain the appropriate fix for the version of LANSA you are encountering the issue with. Important: You should only request this fix if you are encountering the issue described and only if you are on IBM i 7.3 operating system.
19 Aug 2016	Visual LANSA Framework	V14 SP1	Category: VLF-WIN In V14 SP1, a deployed VLF WIN application issues an object not found error for PRIM_ROM when shutting down the VLF. A hotfix is available from LANSA to resolve this issue. Please contact your local support team to obtain the fix. To apply: Download and apply the hotfix to the build environment where the VLF-WIN MSI deployment package is built. Rebuild and deploy the MSI package to pick up the new LANSA runtime with the fix. Alternatively, after applying the hotfix to the build environment where the VLF-WIN MSI deployment package is built, create an MSP (patch) for the LANSA runtime with the fix.
17 Aug 2016	Visual LANSA	V14	Category: Cloud LANSA IDE in the Amazon Cloud - Image with V14 SP1 pre-installed has now been released The image is now available from the AWS Marketplace. This image has V14 Service Pack 1 already installed. For existing users of 14.0 GA there are two ways to upgrade to V14 SP1. You can upgrade it the usual way as you would do if you were not in the Cloud by downloading or obtaining V14 SP1 from LANSA and upgrading your existing V14. Or, if you assigned an IAM role to the instance when you created it, you may upgrade in situ. This requires the instance to have the rights to access S3, hence the need to have assigned an IAM role when you created the instance. Instructions may be found in the instance in the Start Here shortcut on the desktop. Details about specifying an IAM role when creating an instance may be found in the Marketplace usage instructions for the LANSA IDE.
4 Aug 2016	Visual LANSA	All	Category: Visual LANSA Launching the Visual LANSA development environment after upgrading to Windows 10 64-bit or after applying the latest Windows 10 update results in a Global data Initialisation failed error. Refer to Visual LANSA failing with Global Initialisation failure after Windows 10 Upgrade or Update for details.
12 May 2016	Visual LANSA	V14	Category: Cloud LANSA IDE in the Amazon Cloud - Image with EPC 140020 pre-installed has now been released The image is now available from the AWS Marketplace. This image has EPC 140020 already installed. For existing users there are two ways to install EPC 140020. You can upgrade it the usual way - as you would do if you were not in the Cloud by downloading and applying EPC140020 Or, if you assigned an IAM role to the instance when you created it, you may upgrade in situ. This requires the instance to have the rights to access S3, hence the need to have assigned an IAM role when you created the instance. Instructions may be found in the instance in the Start Here shortcut on the desktop. Details about specifying an IAM role when creating an instance may be found in the Marketplace usage instructions for the LANSA IDE.
22 Apr 2016	Visual LANSA	V14	Category: Web development After upgrading Visual LANSA to V14, the option to 'Generate HTML' is missing from the compile options when compiling web enabled functions. Refer to Compile option to Generate HTML missing after upgrade to V14 for details and step to correct.
31 Mar 2016	Visual LANSA	V14	Category: Cloud LANSA IDE in the Amazon Cloud - Image with EPC140010 pre-installed has now been released The image is now available from the AWS Marketplace. This image has EPC140010 already installed. For existing users of 14.0 GA there are two ways to install EPC140010. You can upgrade it the usual way as you would do if you were not in the Cloud by downloading and applying EPC140010 Or, if you assigned an IAM role to the instance when you created it, you may upgrade in situ. This requires the instance to have the rights to access S3, hence the need to have assigned an IAM role when you created the instance. Instructions may be found in the instance in the Start Here shortcut on the desktop. Details about specifying an IAM role when creating an instance may be found in the Marketplace usage instructions for the LANSA IDE
16 Nov 2015	Visual LANSA Web	All	Category: Web Multi tier Model B support for an IBM i application server is only available for Visual LANSA Web with a Windows Web Server (IIS) or a Linux web server. The Apache server cannot be used in V14 as the Model B web server for Visual LANSA Web. Note: Single tier to IBM i is available for Visual LANSA Web and Model B using Apache server is still available for WAMs and Web Functions.
16 Nov 2015	Visual LANSA	V14	Category: Partition Initialization There have been reports of an intermittent Partition Initialization failure when importing the DirectX demonstration material. The error is that a DLL (xdemoboo.dll) is in use. Rerunning the partition initialization allows the import to complete OK. Note: The problem seems to be specific to Windows 8.1.
16 Nov 2015	Visual LANSA Framework	V14	Category: Visual LANSA Framework (VLF) The new VLF-ONE, based on Visual LANSA Web technology, is not shipped on the V14 GA DVD. VLF-ONE will be delivered soon as an EPC. When you install V14, there will be no VLF option during the install or partition initialization. If you upgrade from V13 VLF installed, VLF will remain unchanged at the level it was before the V14 upgrade.
16 Nov 2015	Visual LANSA Framework	V14	Category: Visual LANSA Framework (VLF) If you are a developer using the VLF (Visual LANSA Framework) and upgrade to LANSA V14 then you will lose access to online help resources. For example these assistance menu items will not function correctly: And using F1=Help for item level help text will not function correctly.
16 Nov 2015	Visual LANSA	V14	Category: WAM Execution After a successful WAM deployment using the template XWAMENB, the WAM does not execute. This is caused by the DBUS and PSWD values in X_lansa.pro not matching the login credentials provided in the package and the DB verification process during the installation. This issue only arises when Oracle is used as the Data/Application database engine. The solution is to manually set the DBUS and PSWD values in X_lansa.pro.
16 Nov 2015	LANSA for i	V14	Category: Install/Upgrade LANSA for i can only be installed or upgraded on supported versions of the IBM i Operating System.