Version 12 Release and Installation Notices
Version 12 Service Pack 1 (SP1), the latest service pack for V12, became available in June 2011. SP1 highlights include Enhanced WAMs, allowing the building of web sites using jQuery/jQuery UI and to return JSON responses for AJAX requests, new RDMLX Repository object named External Resource which provide the ability to enroll all resources associated with an application in the Repository and the ability to install or upgrade LANSA for iSeries into IASPs.
You can install a new Version 12 Service Pack 1 system, update an existing Version 12 system to Service Pack 1 or upgrade an existing Version 11.3 or later system to Version 12 Service Pack 1. Read important SQL Server 2008 Express 2008 upgrade information for V12 SP1.
| Date | Description |
|---|---|
| 18 January 2012 | Visual LANSA- V12 SP1 EPC871 After upgrading to V12 SP1 EPC871, your web application may encounter intermittent failures if your application uses header variables with *webevent functions. An EPC871 fix can be requested from LANSA Support to correct this. |
| 30 December 2011 | Visual LANSA- V12 SP1 EPC871 Installing a new V12 SP1 EPC871 non-english LANSA system or upgrading to V12 SP1 EPC871 on non-english LANSA systems can cause problems with system variables that use the system variable evaluation program M@SYSVAR. For example, the @ sign charracter for language FRA is ą ie. MąSYSVAR but after an upgrade to V12 SP1 EPC871, the evaluation program will be M@SYSVAR. This will cause programs that use system variables (evaluated by M@SYSVAR) to fail. The problem is due to the autoimport.exe that is performed during the install or upgrade running the english import.. The issue can be corrected by re-running the SYSVAR import via the System Initialization utility. |
| 7 December 2011 | LANSA Integrator - V12 EPC869 A significant issue has been discovered that requires an EPC869 LANSA Integrator correction. EPC869 HTTP outbound services now identify themselves as HTTP/1.1. Because the HTTP client supports HTTP/1.1 protocol, some HTTP servers are deciding to send the response content using the Chunked Transfer encoding mechanism. This is causing the response to be corrupted. An EPC869 fix can be requested from LANSA Support. |
| 1 December 2011 | Visual LANSA - V12 SP1 EPC871 WAMs generated after applying EPC871, which contains fields in a list which have the *HIDE or *HIDDEN tag may not display correctly at runtime. Refer to Hidden columns on a WAM list are shown at runtime for full details and correction. |
| 4 July 2011 | Visual LANSA - V12 SP1 EPC871 (spin0316) The V12 SP1 DVD will install SQL Server 2008 Express SP2 instead of SQL Server 2008 Express. The install will not upgrade from SQL Server 2008 Express to SP2. SQL Server 2008 Express SP2 does not install The SQL Server Configuration Manager. A separate install for this can be found in \setup\installs\MSSQLEXP\SQLManagementStudio*.exe |
| 4 July 2011 | Visual LANSA - V12 SP1 SQL Server 2008 SP2 is shipped on the V12 SP1 DVD. You may experience the following error when installing Visual LANSA where the install attempts to install or upgrade SQL Server 2008 to SP2. Install ended in error. Error <-3> creating database. Error message: SQL Server Network Interfaces: Error Locating Server/Instance Specified[xFFFFFFFF]. Microsoft SQL Server Native Client 10.0 If you have Microsoft .Net Framework 4 installed, it must be the full version i.e. both .Net Framework 4 Client Profile and .Net Framework 4 Extended must be installed prior to installing Visual LANSA (see image).  If the full version is not installed then the Microsoft SQL Server 2008 Express with SP2 install will fail. Refer to the Microsoft Support site article for full details: http://support.microsoft.com/kb/2500042 Note: The error will also occur if you attempt to install or upgrade to SQL Server 2008 SP2 manually (not as part of the Visual LANSA install). |
| 29 June 2011 | Visual LANSA Deployment Tool - V12 SP1 It can occur in the Deployment Tool that objects (Forms, Processes/Functions, WAMs) selected in the Object Selection dialog are not saved correctly with the package. This occurs when the Other Objects tab is active when pressing OK on the Object Selection dialog; any newly added Forms/Processes/WAMs are discarded. A work-around is to press OK after adding these objects, before going back into the dialog to select Other Objects. Contact your local LANSA vendor to request a hotfix. |
| 21 April 2011 | LANSA for iSeries - V12 When upgrading LANSA for iSeries to V12, you may be unable to restore V12 objects to QTEMP on V5R3 or V5R4. This is a known situation whereby PTFs are required for any objects saved on IBM i 6.1 before they can be restored on previous IBM i versions. Refer to Unable to restore V11 SP5 objects to QTEMP on V5R3 or V5R4. This situation also applies to V12 objects. |
| 03 Sep 2010 | LANSA - V12 In V12 EPC851, when executing RDMLX on the IBM i, an error can be generated stating that LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent functions, RDMLX components running on System i, and WAMs executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX function/WAM/component on IBM i |
| 30 Jul 2010 | LANSA Composer - V3.0 This item only applies if you installed the LANSA Composer client-runtime version that is compatible with the LANSA Composer server running in a LANSA V11 SP5 system. If the LANSA system containing the LANSA Composer server is later upgraded to LANSA version 12, then the LANSA Composer client will no longer be able to connect to it. In this event, you can do one of two things:
|
| 30 Jul 2010 | LANSA Composer - V3.0 If you are upgrading from LANSA Composer version 2.0 and have NOT previously applied Hotfix 002, then you should complete the following steps to move the .jar files for your existing Transformation Maps to their new location. Refer to the following technical note Important note if upgrading LANSA Composer version 2.0 and have NOT previously applied Hotfix 002 |
| 23 Jul 2010 | 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. For further details including a solution, refer to Unable to Load/locate module VF_AC006 error after deploying a VLF application in V12 |
| 22 Jul 2010 | Visual LANSA - V12 You may experience the following error during the installation of a V12 Visual LANSA network client onto a Windows 7 or Vista PC.  This error can occur when the V12 Visual LANSA Server that you are connecting to is installed on Windows 2008 64-bit. LANSA has investigated the cause of this fatal error and have reported our findings to Microsoft. If you encounter this installation error, you should contact your local LANSA vendor for instructions on how to overcome the problem and complete the V12 network client install. |
| 09 Jul 2010 | Visual LANSA - V12 It is possible to generate an error "LANSA requires this operating system to have at least SP1 installed" when installing V12 on Windows 7. Refer to It is possible to generate a compatibility error when installing V12 on Windows 7 |
| 29 Mar 2010 | LANSA for iSeries - V12 If your IBM i master system is on V5R4, you must ensure that you are up to date with the latest CUME and PTFs to avoid any issues during checkin or checkout. You must get to the latest CUME and PTFs level before installing V12 to avoid potential problems. If you do not, you may experience checkin or checkout issues, for example, objects not available in the IDE after a refresh or checking out from the master repository or *svrpgm not created during a checkin and compile. If you encounter any issues during checkin or checkout, check the joblog on the IBM i for the following error MCH3601 X_BASE From module . . . . . . . . : LPBASE From procedure . . . . . . : NotifyDependents__12LpInteractorFQ2_6LpBase6ReasonlP8LpObject Message.. . . . . . . . . . . : Pointer not set for location referenced. If this error exists, then you will need to apply the very latest CUME and PTFs. NOTE: Because this issue is one of re-encapsulation of V6R1 shipped objects, V12 will need to be reinstalled after applying the latest CUME and PTFs. |
| 01 Feb 2010 | Visual LANSA - V12 V12 provides the option of installing SQL Server 2008 Express as the database. Adaptive Server Anywhere databases are no longer provided. Use the following tip to migrate your existing database from V11 and ASA to V12 and SQL Server 2008 Express. Steps to migrate your database from ASA to SQL Server 2008 Express |
| 01 Feb 2010 | LANSA for iSeries - V12 If your IBM i master system is on V5R4, you must ensure that you are up to date with the latest CUME and PTFs to avoid any issues during checkin or checkout. If you experience any checkin or checkout issues, for example, objects not available in the IDE after a refresh or checking out from the master repository, ensure that your IBM i CUME and PTF levels are up to date. |
| 01 Feb 2010 | Visual LANSA - V12 V12 adds support for FLDX so that numeric enter key behaves like field exit (Tab). The FLDX parameter of x_run was previously ignored and defaulted to 'N' rather than the correct default of 'Y' as per the documentation. If you wish the numeric enter key to revert to pre V12 behaviour (Enter key), you can set FLDX=N on the x_run |
| 01 Feb 2010 | Visual LANSA - V12 The Visual LANSA General Checklist contains the following check
|
| 01 Feb 2010 | Visual LANSA - V12 After upgrading to V12, a Visual LANSA network client installation may not function as expected if the Microsoft Visual C++ 2008 Redistributable is not available on this PC. Refer to Upgrading Network Clients to V12 - manual intervention may be required for further details and steps to correct. |
| 01 Feb 2010 | Visual LANSA - V12 When installing Visual LANSA V12 on Windows 7, you may generate an MS SQL Server 2008 compatibility message indicating that SQL Server 2008 Service Pack 1 should be applied.  If you are using Windows 7 64 bit and SQL Server 2008 Express, you must install the SP1 for SQL Server 2008 Express.LANSA recommends downloading and applying the Service Pack to avoid any issues during the Visual LANSA install. Note: You may have to restart the Visual LANSA V12 install if a reboot is required after applying Service Pack 1 to SQL Server 2008 Express |
| 01 Feb 2010 | Visual LANSA Framework - V12 The version of the Visual LANSA Framework shipped with V12 doesn't cater for password length greater than 10 characters or case sensitivity. Support for these features will be added to the VLF post V12 GA. |
| 01 Feb 2010 | Visual LANSA - V12 Object Locking must be enabled in the Visual LANSA system when using the Deliver to option to deliver to an IBM i remote system. This requirement has been removed in EPC851 for V12. |
| 01 Feb 2010 | Visual LANSA - V12 The Visual LANSA V12 Installation can fail if TCP/IP not enabled. For example, you may have Microsoft SQL Server already installed but if the TCP/IP protocol is not enabled an installation failure may occur. You can check for this possibility in the following location: In SQL Server folder, select SQL Server Configuration manager within the Configration Tools folder. When the SQL Server Configuration manager launches, select SQL Server Network Configuration and then Protocols for <Server name >. TCP/IP should be displayed as Enabled or Disabled. If its set as Disabled, enable this protocol and restart the Visual LANSA Install. Check with your Database Administrator if you require assistance with setting or changing SQL Server protocols. |
| 01 Feb 2010 | Visual LANSA - V12 & V11 An LX_ConfigurationName error message is issued when installing a V11 Network Client once V12 is installed on the Server. While attempting to install a V11 Network Client, where the Server machine already has both v11 and v12 configurations, a message stating that the LX_ConfigurationName does not exist in the server registry appears after selecting the configuration to connect to. This message can be avoided by ensuring that the V11 configuration on the Server is the "current configuration". Even though the message appears stating that the LX_ConfigurationName does not exist in the registry, this message is not a fatal message and after clicking OK, the install continues. |
| Visual LANSA | |
|---|---|
| January 18, 2012 - V12 SP1 EPC871 After upgrading to V12 SP1 EPC871, your web application may encounter intermittent failures if your application uses header variables with *webevent functions. An EPC871 fix can be requested from LANSA Support to correct this. | |
| December 30, 2011 - V12 SP1 EPC871 Installing a new V12 SP1 EPC871 non-english LANSA system or upgrading to V12 SP1 EPC871 on non-english LANSA systems can cause problems with system variables that use the system variable evaluation program M@SYSVAR. For example, the @ sign charracter for language FRA is ą ie. MąSYSVAR but after an upgrade to V12 SP1 EPC871, the evaluation program will be M@SYSVAR. This will cause programs that use system variables (evaluated by M@SYSVAR) to fail. The problem is due to the autoimport.exe that is performed during the install or upgrade running the english import.. The issue can be corrected by re-running the SYSVAR import via the System Initialization utility. | |
| December 1, 2011 - V12 SP1 EPC871 WAMs generated after applying EPC871, which contains fields in a list which have the *HIDE or *HIDDEN tag may not display correctly at runtime. Refer to Hidden columns on a WAM list are shown at runtime for full details and correction. | |
| July 4, 2011 - V12 SP1 SQL Server 2008 SP2 is shipped on the V12 SP1 DVD. You may experience the following error when installing Visual LANSA where the install attempts to install or upgrade SQL Server 2008 to SP2. Install ended in error. Error <-3> creating database. Error message: SQL Server Network Interfaces: Error Locating Server/Instance Specified[xFFFFFFFF]. Microsoft SQL Server Native Client 10.0 If you have Microsoft .Net Framework 4 installed, it must be the full version i.e. both .Net Framework 4 Client Profile and .Net Framework 4 Extended must be installed prior to installing Visual LANSA (see image). If the full version is not installed then the Microsoft SQL Server 2008 Express with SP2 install will fail. Refer to the Microsoft Support site article for full details: http://support.microsoft.com/kb/2500042 Note: The error will also occur if you attempt to install or upgrade to SQL Server 2008 SP2 manually (not as part of the Visual LANSA install). | |
| July 4, 2011 - V12 SP1 (Spin0316) The V12 SP1 DVD will install SQL Server 2008 Express SP2 instead of SQL Server 2008 Express. The install will not upgrade from SQL Server 2008 Express to SP2. SQL Server 2008 Express SP2 does not install The SQL Server Configuration Manager. A separate install for this can be found in \setup\installs\MSSQLEXP\SQLManagementStudio*.exe | |
| June 29, 2011 - V12 SP1 It can occur in the Deployment Tool that objects (Forms, Processes/Functions, WAMs) selected in the Object Selection dialog are not saved correctly with the package. This occurs when the Other Objects tab is active when pressing OK on the Object Selection dialog; any newly added Forms/Processes/WAMs are discarded. A work-around is to press OK after adding these objects, before going back into the dialog to select Other Objects. Contact your local LANSA vendor to request a hotfix. | |
| September 3, 2010 - V12 In V12 EPC851, when executing RDMLX on the IBM i, an error can be generated stating that LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent functions, RDMLX components running on System i, and WAMs executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX function/WAM/component on IBM i | |
| July 22, 2010 - V12 You may experience the following error during the installation of a V12 Visual LANSA network client onto a Windows 7 or Vista PC. This error can occur when the V12 Visual LANSA Server that you are connecting to is installed on Windows 2008 64-bit. LANSA has investigated the cause of this fatal error and have reported our findings to Microsoft. If you encounter this installation error, you should contact your local LANSA vendor for instructions on how to overcome the problem and complete the V12 network client install. | |
| July 9, 2010 - V12 It is possible to generate an error "LANSA requires this operating system to have at least SP1 installed" when installing V12 on Windows 7. Refer to It is possible to generate a compatibility error when installing V12 on Windows 7 | |
| February 1, 2010 - V12 V12 provides the option of installing SQL Server 2008 Express as the database. Adaptive Server Anywhere databases are no longer provided. Use the following tip to migrate your existing database from V11 and ASA to V12 and SQL Server 2008 Express. Steps to migrate your database from ASA to SQL Server 2008 Express | |
| February 1, 2010 - V12 V12 deployed runtime applications now require the Visual C++ 2008 Runtime to be installed on the PC. This can be deployed/installed automatically by ticking the "Deploy VC90 Runtime" package setting in the deployment tool. It is now ticked by default in all shipped package templates. However if the deployment package build process involves copying an existing deployment package, then this setting needs to be manually selected. Failure to include the VC90 Runtime will result in an x_run.exe - Application error similar to "The application was unable to start correctly." | |
| February 1, 2010 - V12 The Visual LANSA General Checklist contains the following check. If you are installing LANSA on a PC running Windows Vista or Windows 2008 you must have User Account Control ( UAC ) turned OFF. If UAC is ON, the install process will terminate. When the install process terminates, the message on the screen will indicate that UAC is the cause. Steps to turn off UAC are available from the Microsoft site at http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx. Care should be taken when making changes to the UAC and you must be able to log on with or provide the credentials of a member of the local Administrators group. | |
| February 1, 2010 - V12 After upgrading to V12, a Visual LANSA network client installation may not function as expected if the Microsoft Visual C++ 2008 Redistributable is not available on this PC. Refer to Upgrading Network Clients to V12 - manual intervention may be required for further details and steps to correct. | |
| February 1, 2010 - V12 When installing Visual LANSA V12 on Windows 7, you may generate an MS SQL Server 2008 compatibility message indicating that SQL Server 2008 Service Pack 1 should be applied. If you are using Windows 7 64 bit and SQL Server 2008 Express, you must install the SP1 for SQL Server 2008 Express. LANSA recommends downloading and applying the Service Pack to avoid any issues during the Visual LANSA install. Note: you may have to restart the Visual LANSA V12 install if a reboot is required after applying Service Pack 1 to SQL Server 2008 Express. | |
| February 1, 2010 - V12 V12 adds support for FLDX so that numeric enter key behaves like field exit (Tab). The FLDX parameter of x_run was previously ignored and defaulted to 'N' rather than the correct default of 'Y' as per the documentation. If you wish the numeric enter key to revert to pre V12 behaviour (Enter key), you can set FLDX=N on the x_run | |
| February 1, 2010 - V12 Object Locking must be enabled in the Visual LANSA system when using the Deliver to option to deliver to an IBM i remote system. This requirement has been removed in EPC851 for V12. | |
| February 1, 2010 - V12 The Visual LANSA V12 Installation can fail if TCP/IP not enabled. For example, you may have Microsoft SQL Server already installed but if the TCP/IP protocol is not enabled an installation failure may occur. You can check for this possibility in the following location: In SQL Server folder, select SQL Server Configuration manager within the Configration Tools folder. When the SQL Server Configuration manager launches, select SQL Server Network Configuration and then Protocols for <Server name>. TCP/IP should be displayed as Enabled or Disabled. If its set as Disabled, enable this protocol and restart the Visual LANSA Install. Check with your Database Administrator if you require assistance with setting or changing SQL Server protocols. | |
| February 1, 2010 - V12 An LX_ConfigurationName error message is issued when installing a V11 Network Client once V12 is installed on the Server. While attempting to install a V11 Network Client, where the Server machine already has both v11 and v12 configurations, a message stating that the LX_ConfigurationName does not exist in the server registry appears after selecting the configuration to connect to. This message can be avoided by ensuring that the V11 configuration on the Server is the "current configuration". Even though the message appears stating that the LX_ConfigurationName does not exist in the registry, this message is not a fatal message and after clicking OK, the install continues. | |
| Visual LANSA Framework | |
|---|---|
| July 23, 2010 - 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. For further details including a solution, refer to Unable to Load/locate module VF_AC006 error after deploying a VLF application in V12 | |
| February 1, 2010 - V12 The version of the Visual LANSA Framework shipped with V12 doesn't cater for password length greater than 10 characters or case sensitivity. Support for these features will be added to the VLF post V12 GA. | |
| LANSA for iSeries | |
|---|---|
| April 21, 2011 - V12 When upgrading LANSA for iSeries to V12, you may be unable to restore V12 objects to QTEMP on V5R3 or V5R4. This is a known situation whereby PTFs are required for any objects saved on IBM i 6.1 before they can be restored on previous IBM i versions. Refer to Unable to restore V11 SP5 objects to QTEMP on V5R3 or V5R4. This situation also applies to V12 objects. | |
| September 3, 2010 - V12 In V12 EPC851, when executing RDMLX on the IBM i, an error can be generated stating that LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent functions, RDMLX components running on System i, and WAMs executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX function/WAM/component on IBM i | |
| March 19, 2010 - V12 If your IBM i master system is on V5R4, you must ensure that you are up to date with the latest CUME and PTFs to avoid any issues during checkin or checkout. You must get to the latest CUME and PTFs level before installing V12 to avoid potential problems. If you do not, you may experience checkin or checkout issues, for example, objects not available in the IDE after a refresh or checking out from the master repository or *svrpgm not created during a checkin and compile. If you encounter any issues during checkin or checkout, check the joblog on the IBM i for the following error MCH3601 X_BASE From module . . . . . . . . : LPBASE From procedure . . . . . . : NotifyDependents__12LpInteractorFQ2_6LpBase6ReasonlP8LpObject Message.. . . . . . . . . . . : Pointer not set for location referenced. If this error exists, then you will need to apply the very latest CUME and PTFs. NOTE: Because this issue is one of re-encapsulation of V6R1 shipped objects, V12 will need to be reinstalled after applying the latest CUME and PTFs. | |
| February 1, 2010 - V12 Object Locking must be enabled in the Visual LANSA system when using the Deliver to option to deliver to an IBM i remote system. This requirement has been removed in EPC851 for V12. | |
| LANSA for the Web | |
|---|---|
| None at this time. | |
| LANSA Composer 3.5 | |
|---|---|
| January, 2012 - V3.5 A significant issue has been discovered that affects LANSA Composer 3.5. With the version of LANSA Integrator shipped with LANSA Composer 3.5 (EPC869) HTTP outbound services now identify themselves as HTTP/1.1. Because the HTTP client supports HTTP/1.1 protocol, some HTTP servers are deciding to send the response content using the Chunked Transfer encoding mechanism. This is causing the response to be corrupted. An EPC869 fix is shipped on the LANSA Composer installation media in the \FIXES\EPC869INT-111123 folder. After upgrading your LANSA Composer server, please follow the instructions provided in the readme.txt file in that folder to apply the fix to LANSA Integrator on your LANSA Composer server on IBM i or Windows. | |
| LANSA Composer 3.0 | |
| July 30, 2010 - V3.0 This item only applies if you installed the LANSA Composer client-runtime version that is compatible with the LANSA Composer server running in a LANSA V11 SP5 system. If the LANSA system containing the LANSA Composer server is later upgraded to LANSA version 12, then the LANSA Composer client will no longer be able to connect to it. In this event, you can do one of two things:
| |
| July 30, 2010 - V3.0 If you are upgrading from LANSA Composer version 2.0 and have NOT previously applied Hotfix 002, then you should complete the following steps to move the .jar files for your existing Transformation Maps to their new location. Refer to the following technical note Important note if upgrading LANSA Composer version 2.0 and have NOT previously applied Hotfix 002 | |
| LANSA Client | |
|---|---|
| None at this time. | |
| Documentation | |
|---|---|
| None at this time. | |
