Progress OpenEdge 11.3.0 Readme Ports: All Date: July, 2013 -------------------------------- Copyright (c) 1984-2013 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. Read these On-line Release Notes ================================ It is important to read these on-line release notes. They are the exclusive release notes for this release. The on-line release notes are on the distribution medium as one text file, readme.txt. The readme.txt file includes a list of known issues followed by a list of the issues fixed in this release. In addition, the distribution medium includes the following HTML report files which list the issues addressed in this release - organized by version, issue number (CR ID), or product component. * PROGRESS_OE__VERSION.htm (Lists fixed issues by Version) * PROGRESS_OE__ISSUE.htm (Lists fixed issues by Issue Number) * PROGRESS_OE__COMPONENT.htm (Lists fixed issues by Component) --------------------------------------- PRODUCT NOTES 1. Installation Install 2. ABL Internationalization Language Issues Web Services client 3. Adapter for Sonic ESB 4. ADE Tools and Runtime Data Dictionary Deployment GUI Rendering Services Tools Translation Manager Web Rendering 5. AppServer Broker 6. Auditing 7. BP Server 8. BPM Classes 9. BPM Studio 10. BPM Web Flow 11. Business Process Modeler 12. Business Process Portal 13. Database Database Utilities Failover Clusters 14. DataServers MS-SQL ORACLE 15. Documentation Electronic Documentation Help Progress Developer Studio for OpenEdge 16. Graphical User Interface ABL ActiveX 17. Management Management 18. Migration 19. OE Mobile 20. Open Client Web Services Provider 21. OpenEdge GUI for .NET 22. OpenEdge Replication Server 23. Porting 24. Progress Developer Studio for OpenEdge AppBuilder Support Debugger Visual Designer 25. REST 26. Security User Authentication 27. SQL ESQL92 Server SQL 28. Web Services Client 29. WebClient 30. WebSpeed Tools ================================================ Installation - ================================================ Note: OE00121569 Type: Limitation OpenEdge installation may install Sonic client and container code --------------------------------- RN#: 101A-00291 =============== The OpenEdge installation program may install Sonic Software client and container code depending on which products get installed. Because the installation program requires it run as ROOT on Unix, the Sonic Software code gets installed with those permission set. The OpenEdge installation program attempts to set the correct permissions for the Sonic code, but this fails on the HPUX operating system. This will cause the Sonic ESB Container created by OpenEdge to fail when started unless it is started as ROOT. To resolve this, run the command 'chmod -R o+w *' from $DLC/sonic as ROOT. Note: OE00163769 Type: Workaround Unknown Publisher message with a Netsetup Install --------------------------------- After performing a Netsetup install on Windows the user may see an Unknown Publisher message when running any OpenEdge .EXE files from a network drive. To resolve this issue, add the network drive share to the client's trusted zone. To add the network drive to your trusted zone: 1. Open the Internet Options Dialog Box from an Internet Explorer session. 2. Select the Security Tab. 3. Select the Local Intranet icon from the zones shown. 4. Click the Sites command button, which opens a Local Intranet Dialog Box. 5. Click the Advanced command button, which opens a dialog box where you add and remove websites from your intranet. 6. Add \\servername\ to the list of websites. Click Close, then OK to return to the main Internet Options Dialog Box. You may have to reboot the client for this to take effect. Note: OE00168104 Type: Known Issue Sonic container startup shortcut requires quotes for directories with spaces --------------------------------- If you install OpenEdge into a directory with a space in the name (e.g. C:\Program Files\OpenEdge), the shortcut to start up the sonic container does not function properly. You can fix the problem by editing the shortcut and enclosing the Target: and Start in: fields in double quotes. Note: OE00187147 Type: Known Issue The WebClient One-Click install fails as a Non-Admin User --------------------------------- The WebClient One-Click install (OCI) (over-the-web install) fails when run by a non-admin on a system that does not already have the Installshield Setup Player installed as an Add-On. For this to work, the add-on must already be installed/registered by an Administrator. Running the WebClient One-Click install as Administrator just one time will get the Setup Player installed. After this is done the WebClient One-Click install can be run as a Non-Administrator. This issue only occurs when installing Over-the-Web. This issue does not occur when running the WebClient installation directly via the setup.exe file. Note: OE00213877 Type: Limitation Slow Webclient installation on the Windows 2003 Server --------------------------------- While installing WebClient on the Windows 2003 Server, the progress bar might reach 90% and then stop for more than 20 minutes before completing the installation. This happens for the non-administrator group users. Note: OE00234021 Type: Known Issue WebClient 11.2.x service pack fails to install on top of WebClient 11.2.0 --------------------------------- The WebClient 11.2.x service pack fails to install on top of WebClient 11.2.0 for a non-admin user. It is a problem in the WebClient 11.2.0 installation and cannot be resolved in this service pack. To install the WebClient 11.2.x service pack properly, you must uninstall the WebClient 11.2.0 and install the WebClient 11.2.x service pack again. ================================================ Installation - Install ================================================ Note: OE00147494 Type: Known Issue Installation of Failover Clusters -- Windows --------------------------------- You must ensure there are no active instances of the Cluster Administrator utility prior to installation. To do this, use the Windows Task Manager to check for processes running the cluadmin.exe image. If a user associated with an instance of the Cluster Administrator is not readily identifiable, these processes can be forcefully terminated as follows: 1. Within Task Manager, select the cluadmin.exe process and press the End Process button. 2. Answer yes to the popup dialog asking if you really want to terminate the process. Failure to shut down all instances of the Cluster Administrator tool results in a partial installation and fails to properly register the resource and administrator extension DLLs, causing cluster management to fail. Note: OE00163889 Type: Known Issue .Net Framework not installed with unknown default language --------------------------------- Progress Developer Studio and OpenEdge Advanced UI Controls have a dependency on the Microsoft .NET Framework v4.0. The OpenEdge installation media includes the English version of the Microsoft .NET Framework, and the OpenEdge installation process will automatically install the framework if it is not already your system, provided that your system's locale is set to English. If the locale on your system is set to something other than English and the .NET Framework 4.0 for your locale is not already installed, then Progress Developer Studio and OpenEdge Advanced UI Controls do not install properly. OpenEdge will not install the English version of the .NET Framework when the system locale is not English, and the Advanced UI controls will not install without the .NET Framework installed. To work around this problem, install the Microsoft .NET Framework v4.0 for your locale, prior to installing OpenEdge. To download different languages of the .NET Framework 4.0 as well as the Windows 64-bit version: - Login to http://www.progress.com/esd - Choose "Progress OpenEdge Deployment Components" - Choose "Microsoft .NET Framework" download page Note: OE00201877 Type: Limitation OpenEdge support on Windows XP --------------------------------- OpenEdge supports Windows Service Pack 3 and later for the Windows XP platform. Note: OE00234441 Type: Limitation Progress Dynamics as an optional component disabled for Win-64 --------------------------------- When you install 64-bit OpenEdge, the Progress Dynamics check box is disabled on the Configuring/Installing Components dialog box. ================================================ ABL - Internationalization ================================================ Note: OE00073374 Type: Known Issue Thai characters or complex scripts do not display in command prompt or console --------------------------------- The Windows command prompt or console is not enabled for Thai characters or complex scripts on any version of Windows (XP, Vista or Windows 7). When trying to read Progress messages sent to the Console while using Thai or complex scripts, you can: * Use the English PROMSGS file. * Use the Thai character or complex script PROMSGS file, but pipe the output of the command to a file that can be read by any Windows editor. Note: OE00125227 Type: Behavior Change Pasting Unicode text into GUI widgets might require font and codepage changes --------------------------------- For the GUI client (prowin32.exe), text widgets such as editors and fill-ins are Unicode-enabled. If you enter characters into these widgets that are not supported by the font in use or are not available in the -cpinternal codepage, the widget value might contain a question mark (?). For example, if the user were to copy a quoted string from another Unicode-enabled application, the double quotes copied might be U+201C and U+201D, the left and right double quotation marks respectively. When copying these into an OpenEdge editor, the quotation characters might not display correctly in the editor, and might be converted to question mark (?) when accessing the value of the editor. The default font OpenEdge uses for widgets is MS Sans Serif. MS Sans Serif does not provide a visual representation for these quotation characters. Changing the editor's font to Courier New instead will allow the characters to display correctly. Many customers use ISO8859-1 as the -cpinternal codepage. The ISO8859-1 codepage does not contain these quotation characters, so they will be converted to "?" when accessing the value of the editor. Changing -cpinternal to 1252 instead of ISO8859-1 will allow these characters to be displayed correctly. You should set your font and -cpinternal codepage according to the characters you will be using in your application. Prior to OE10, the GUI client used ANSI widgets. If non-ANSI characters were pasted to ANSI widgets, Windows would provide a conversion from these characters to ANSI characters. The characters were visually similar, but not the same. ================================================ ABL - Language Issues ================================================ Note: OE00147609 Type: Known Issue CAN-FIND X field-list problem --------------------------------- The FIELDS clause does not guarantee the inclusion or exclusion of fields in any given query. The AVM may require additional fields, for example, to accommodate a key value required by an index. The application must not reference fields that are missing from the FIELDS list. In most cases when this occurs a run-time error is generated indicating that the field is unavailable. There are situations, for example with a function that includes the NO-ERROR attribute by default, where it is legitimate to satisfy function requirements using a field that is missing from the FIELDS list. Such instances equate the missing field to the Unknown value (?) or null (for DataServers) in order to resolve an expression. In other words, the ABL attempts to detect missing fields with run-time errors where possible. However, there are cases where it is legitimate to use a missing field in an expression. In such cases, the missing field will resolve to the Unknown value (?) or native data source null. Note: OE00147778 Type: Limitation INT64 ActiveX support requires oleaut32.dll version 5.1.2600.2180 or later --------------------------------- To support the INT64 data type with ActiveX controls or ActiveX Automation objects, C:\windows\system32\oleaut32.dll must be version 5.1.2600.2180 or later. If your application uses an earlier version of oleaut32.dll and a parameter of INT64 data type is passed to a COM object, the results are unpredictable and may result in an error. This is true even if it is an input parameter and the number in the variable is within the 32-bit range. Therefore, if you do not have the correct version of oleaut32.dll, you should not use the INT64 data type with COM objects. ================================================ ABL - Web Services client ================================================ Note: OE00147860 Type: Known Issue Xmethods Web services used for demonstration in samples --------------------------------- This product and accompanying documentation contain references to the Weather - Temperature and StockQuotes XMethods Demo services provided by XMethods, Inc. (www.xmethods.net). Copyright 2003 XMethods, Inc. All rights reserved. Any use of these services by you shall be for demonstration purposes only. ================================================ Adapter for Sonic ESB - ================================================ Note: OE00192621 Type: Limitation Agents remain locked when ESB Adapter returns a Fault in Sonic Workbench --------------------------------- When using the OpenEdge Adapter for Sonic ESB with a session-free AppServer and persistent procedures, it is important that you release the persistent procedure when your ESB process completes, to prevent having a locked agent. When the adapter returns a fault, you must ensure the Release operation is done in your Fault process. This requires you to keep track of your process ID and have access to it in your Fault process. In the Progress Developer Studio for OpenEdge/Sonic Workbench development environment, Sonic intercepts all fault returns so that it can display the result. Consequently, Fault processes are never run. Setting the Command Parameter ESB Fault Return Mode to "Continue Process with Fault" discards the original message where your Procedure ID is stored, so this is not a viable solution. To free up locked agents on the AppServer, you must restart your development container. Using Persistent Procedures within Sonic ESB processes is discouraged because it greatly complicates the handling of Faults and makes your session-free AppServer operate no differently than a session-managed AppServer. Note: OE00215955 Type: Behavior Change Connnection string limitation for session-managed native ESB Adapter --------------------------------- The combined length of the connection string (composed of a user-id, password, and information fields) must not exceed 30,000 non-Unicode characters when connecting to an AppServer. Exceeding the string length causes an AppServer exception. ================================================ ADE Tools and Runtime - ================================================ Note: OE00108492 Type: Behavior Change Generic comment deletion code removed from triggers --------------------------------- Deletion triggers have been updated to not generically remove comments, security allocation and multi-media records due to performance impact. A new ERWin trigger template db/af/erw/afercustrg.i has been provided that customers can use to re-generate their own triggers without the generic deletion code. Customers can also update their triggers with specific code to do the deletion in such a specific way that should not have any performance impact. Note: OE00237556 Type: Limitation AppBuilder in Developer Studio does not support SHIFT in accelerators --------------------------------- The ABL does not support SHIFT as second modifier for modified single key accelerators. Developer Studio bindings defined with ALT-SHIFT-X or CTRL-SHIFT-X (The "x" refers to any printable char.) will thus not work when the focus is in the design window. Progress will send CTRL-X or ALT-X to Eclipse ignoring the SHIFT and fire corresponding bindings if defined. This means that the ABL UI Designer do not respond to CTRL-SHIFT-W (Close all) and CTRL-SHIFT-S (save all) in the Developer Studio default Theme. Note: OE00237707 Type: Known Issue Repeated calls to a DecisionService instance's InvokeService() method can fail --------------------------------- Repeated calls to the same DecisionService instance's InvokeService() method can fail, especially when dealing with nested data. To work around this issue, create a new instance of the DecisionService for each call. Note that the RulesServerConnection instances can be re-used. ================================================ ADE Tools and Runtime - Data Dictionary ================================================ Note: OE00126947 Type: Behavior Change Mandatory fields are not marked as NOT NULL during protoodbc --------------------------------- When running a pro-to-odbc migration against a DB2 data source, fields marked as "mandatory" in the OpenEdge database were being created in generated SQL script and the foreign data source without the NOT NULL syntax. This leads to a situation where these fields are null capable in the foreign database. To make DB2 consistent with the MS SQL Server and Oracle DataServers, the OpenEdge DataServer for ODBC will now set the NOT NULL constraint on SQL columns derived from mandatory fields for DB2 data sources. Note: OE00168857 Type: Known Issue Initial value rules for logical fields in the GUI Dictionary --------------------------------- By default, when you create a logical field through the GUI Data Dictionary, it sets the Initial Value as the first value in the Format. For example, if the Format is "male/female", the Initial value defaults to male. The exception to the first item rule is when the format is "yes/no" or "true/false". For those cases, the tool uses the OpenEdge default value for a logical field, "no" and "false", respectively. ================================================ ADE Tools and Runtime - Deployment ================================================ Note: OE00088123 Type: Known Issue Notes on using the Deploy Static Objects tool --------------------------------- When deploying static objects using the Deploy Static Objects tool, please note the following: 1) You must specify the following extra directories in the Deploy Static Objects tool, in order for a standard Progress Dynamics WebClient install to work: adeicon ry/img adm2/image adeicon.pl can be used instead of the adeicon directory, but you must manually copy this file into the target directory. These image directories are not required for a server install (AppServer of Web). 2) You must manually copy the adm2/dyntreew.wrx file into the target directory, for WebClient installs. 3) You must manually copy adecomm.pl into the target directory for a WebClient install. Note: OE00116351 Type: Behavior Change Static Object Deployment Tool - Option to generate source listing --------------------------------- The Deploy Static Objects tool has the ability to produce a listing file of all the files that are packaged into a deployment produced by the tool. The listing file is specified in the UI before the deployment starts building. If no listing file is specified, then the listing will not be produced. A default value is provided by the tool, and is for a file called 'listing.log' in the session's temporary directory. The listing file consists of the following fields, tab-delimited: File name Relative path Deployment type Design-only flag This functionality can be used to determine which files are required for compilation on 64-bit platforms. A Dynamics client is only supported on Windows, which is a 32-bit platform, and customers may connect to an AppServer running on a 64-bit platform; in such a case the code would need to be compiled against the 64-bit platform, and the listing file will give the ability to determine which files are required. Note: OE00132914 Type: Behavior Change DCU enforces MinVersion with migrations --------------------------------- If a setup XML file has migration setup types (defined by having a migration_source_branch session property with a non-blank value), then a check is performed to ensure that the DB version sequence matches that of the MinimumVersion in the Database node of the setup_type. If these 2 versions don't match an error is raised and a message shown. This message is a new message and has a code of 'MSG_cannot_migrate', and appears in the shipped setup101B.xml. If customers have created their own setup.xml files, they need to add this message to all the setup types contained in those XML files. Note: OE00215883 Type: Workaround The DynamicsVersion session property must be manually updated --------------------------------- If you are working in an OpenEdge release later than 10.2B, the DynamicsVersion session property may be set to the wrong release number. This property is not automatically updated. To workaround this issue, modify $DLC/src/dynamics/db/icf/dfd/update_dynamics_version_property.p so that the value of the DYNAMICS-VERSION preprocessor is set to the relevant OpenEdge release number (11.2, for example). Compile this file and copy to $DLC/gui, which is important because the DCU does not run against source code. Note: OE00215923 Type: Product Notice Migrating Progress Dynamics to Release 11.0+ --------------------------------- Before attempting any migration, convert the physical database to Release 11.0+, using the proutil conv1011. Progress Software Corporation recommends making a backup at this time. Before migrating to Release 11.0+, Progress Dynamics currently using Version 2.1B must upgraded to Version 2.1B02. The following steps are the only supported path to migrate a Version 2.1B Repository to OpenEdge 10.2B: - Ensure the Repository is upgraded to Version 2.1B02 (db version: 020030). The migration does not work properly on earlier versions of the Repository. - Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install. - Modify the -icfparam parameter in the target. Change 'DCUSETUPTYPE=ProgressSetup' to 'DCUSETUPTYPE=Migrate21Setup'. - Run the Dynamic Configuration Utility (DCU) from this shortcut to upgrade the Repository from Version 2.1B02 to Release 11.0+. To migrate from Release 10.0B05 to Release 11.0+, follow these steps: - Ensure the Repository is upgraded to Release 10.0B05 (db version: 100005). The migration does not work properly on earlier versions of the Repository. - Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install. - Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate100Setup. - Running the DCU from this shortcut upgrades the Repository from Release 10.0B05 to Release 11.0+. To migrate from Release 10.1A02 to Release 11.0+, follow these steps: - Ensure the Repository is upgraded to Release 10.1A02 (db version: 101002). The migration does not work properly on earlier versions of the Repository. - Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install. - Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101ASetup. - Running the DCU from this shortcut upgrades the Repository from Release 10.1A02 to Release 11.0+. To migrate from Release 10.1B03 to Release 11.0+, follow these steps: - Ensure the Repository is upgraded to Release 10.1B03 (db version: 101101). The migration does not work properly on earlier versions of the Repository. - Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install. - Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101BSetup. - Running the DCU from this shortcut upgrades the Repository from Release 10.1B03 to Release 11.0+. To migrate from Release 10.1C to Release 11.0+, follow these steps: - Ensure the Repository is upgraded to Release 10.1C (db version: 101201). The migration does not work properly on earlier versions of the Repository. The migration will also work for service packs 1 and 2. - Create a new shortcut for the Dynamics Configuration Utility (DCU), based on the existing shortcut from the install. - Modify the -icfparam parameter in the target. Change DCUSETUPTYPE=ProgressSetup to DCUSETUPTYPE=Migrate101CSetup. - Running the DCU from this shortcut upgrades the Repository from Release 10.1C to Release 11.0+. To migrate from Release 10.2A to Release 11.0+, follow these steps: - There were no updates made to the Repository between 10.2A and 11.0, and so no migration is necessary. To migrate from Release 10.2B to Release 11.0+, follow these steps: - There were no updates made to the Repository between 10.2B and 11.0, and so no migration is necessary. ================================================ ADE Tools and Runtime - GUI Rendering ================================================ Note: OE00020074 Type: Limitation Print Preview and Export to Excel do not work when the data source is an SBO --------------------------------- Print Preview and Export to Excel options available on various browse toolbars are not supported for visual objects whose data sources are SmartBusinessObjects. These options will do nothing when chosen. Note: OE00024747 Type: Limitation Static data objects do not get initial value from Repository --------------------------------- Static SDO proxies (_cl) do not get the INITIAL-VALUE from the Repository's EntityField DefaultValue at run time. The temp-table's INITIAL-VALUE attribute is a read-only attribute that is compiled into the SDO temp-table definition from the SDO include. Note: OE00059495 Type: Behavior Change RowObjUpd.ChangedFields is obsolete --------------------------------- Prior to Version 10.0A, the RowObjUpd.ChangedFields field was used to figure out which fields to save in an SDO. This is now obsolete and no longer used. The SDO now figures out which fields to save to the database tables based on a comparison of the before-image and the changed record. The ChangedFields field is not used in any logic, except for a call to bufferCollectChanges, which updates this field. Since it does not capture all changes, this update is not reliable and the method will be deprecated in the future. Note: OE00060333 Type: Known Issue New records can be duplicated when reading new batch if added while batching --------------------------------- If new records are created that sort higher than the last record in the current batch, the new record is duplicated when a batch includes the new record. To prevent this, either ensure that the user is at the last batch when adding the new records that will get key values that sort higher than the currently last record or avoid batching when such records can be created. Note: OE00061359 Type: Known Issue WebSpeed detail program called from a WebSpeed report program hangs --------------------------------- A WebSpeed detail program called from a WebSpeed report program might hang when the Add button is used a second time or the Delete button is used. If the detail program is used separately from the report program, the problem does not occur. Note: OE00076414 Type: Limitation ADM2 does not support the READ-ONLY attribute on browse columns --------------------------------- The ADM2 does not support setting the READ-ONLY attribute directly on browse columns as a way to disable fields. Field enabling is controlled by the EnabledFields property, that is, you make columns read-only by removing them from the enabled fields list. This is not considered to be a bug. Dynamic browser columns are all read-only at start up, so it would be very difficult to implement a solution to detect if the READ-ONLY attribute has been set in initializeObject. Note: OE00087999 Type: Known Issue Loss of data when changing page while browse is in add --------------------------------- When adding a new record in a browser that is part of a tabbed user interface, the entered data can be lost or appended to the next record in the browser under the following conditions: - The browser is the update source for an SDO. - The user did not enter all of the required fields in the browser row. - The user selects a different page before saving the new record. Note: OE00088005 Type: Limitation A single toolbar cannot switch navigation between SDOs and SBOs --------------------------------- In a paged container where a SDO is the Data-source of a SBO, you cannot use a single toolbar to navigate both the SDO and the SBO. Note: OE00088184 Type: Limitation Static browsers/browsers in static windows don't get Repository column labels --------------------------------- Browsers running in static windows linked to a static SDO on an AppServer will not get the column-label from the Repository's EntityField. Instead, the browser gets the column-label from the database schema. This problem also applies to any static browser. Note: OE00094575 Type: Limitation Error 4054 (.. does not fit..) if ToolbarDrawDirection is "vertical" --------------------------------- The Dynamics layout manager does not handle toolbars where the ToolbarDrawDirection is set to 'vertical'. Note: OE00102910 Type: Behavior Change Read only SDO tables can be specified to remain NO-LOCKed during transaction --------------------------------- The NoLockReadOnlyTables property can hold a comma-separated list of read-only (non-updatable) tables that should remain NO-LOCKed during the transaction. A value of 'ALL' means that all read-only tables should remain NO-LOCKed. Note that read-only tables defined by this property also are excluded from the optimistic lock check of changes. Note: OE00104047 Type: Limitation CallerProcedure, CallerObject, and CallerWindow are not set in createObjects --------------------------------- The Session Manager's launch in Progress Dynamics sets properties like CallerProcedure, CallerObject, and CallerWindow in the launched container. These properties are set before the container is initialized and can thus be used in an initializeObject override. However, they are not intended for use during the construction (the execution of the main block) of the container. The createObjects call is typically done as part of the construction. However, in previous releases, static non-window containers, like SmartFames and SmartDataViewers, did call createObjects from initializeObject allowing these properties to be used also in createObjects. Now, createObjects is called during the construction of almost all containers. If a createObject override uses these properties, it is unlikely to work. Any logic referring to these properties in createObjects should be moved to an initializeObject override instead. Moving this logic to initializeObject should not cause any change in behaviour. Note: OE00107469 Type: Known Issue SmartFrame objects stored with .w in object name may need two translations --------------------------------- For SmartFrames or SmartWindows that are launched from a static container, the object name for Title and Page Label translations is resolved from the procedure:FILE-NAME without path and extension. Therefore, SmartFrame objects that have the .w extension in their Repository object names might need two translations, one without the extension for usage in static containers and one with the extension for dynamic containers. Note: OE00107568 Type: Known Issue Error messages for child SDO not returned when CLOB involved --------------------------------- A detailed error message may not be returned to the client while adding a record to a SmartDataObject under the following circumstances: - the SDO is running on AppServer - the SDO contains large object fields - AutoCommit is false (commit is used to commit multiple updates at once) The client does receive an "update cancelled" message but should have a detailed error. The detailed error is written to the AppServer log file. This situation is more likely to occur with an SDO that is part of a SmartBusinessObject. Note: OE00109030 Type: Behavior Change Changes in how Dynamics Window dimension profiles store WINDOW-MAXIMIZED --------------------------------- Progress Dynamics windows now store the WINDOW-MAXIMIZED state together with the previously stored dimensions in the user profile. The state is stored as a 5th entry in the profile value. In previous versions, this state just overwrote the old profile. If you close a maximized window and no dimensions have been saved previously, the window still stores "WINDOW-MAXIMIZED" as the only entry. With the new behavior, a window can store the WINDOW-MAXIMIZED state without loosing the stored dimensions for the previously saved WINDOW-NORMAL state. The next time you launch the window, it displays maximized. But, when the WINDOW-NORMAL state is applied, the window resumes its previously stored size. Note: OE00109275 Type: Limitation The SmartDataBrowser sort profile is not used with SBO data-sources --------------------------------- The sort profile saved for a SmartDataBrowser with a SmartBusinessObject as its data-source is not used upon restart. Note: OE00109286 Type: Known Issue Translation tool does not include SmartDataBrowser search field --------------------------------- The optional search field of a SmartDataBrowser doesn't show up in the translation window to allow you to add a translation. Note: OE00110402 Type: Known Issue Setting of BaseQuery in initializeObject requires synchronization of QueryWhere --------------------------------- If any other query manipulation has been done before changes to the BaseQuery are made, you need to synchronize QueryWhere and possibly the QueryString. If the BaseQuery is set in an initializeObject override before SUPER, you might also need to synchronize QueryWhere in an SDO without any custom query manipulation. The only cases where BaseQuery can be set without synchronizing the QueryWhere are on the client (AsDivision = 'client') and in dynamic SDOs on the server (AsDivision = 'server'). Static SDOs calls setOpenQuery, which calls setQueryWhere, from the main block (query.i) when connected to the database. Dynamic objects that are connected to the database will call prepareQuery from createObjects. Background: The BaseQuery is the design-time, fixed part of the query. It is part of the object definition. The design philosophy is that runtime query manipulation can be done without violating the integrity of this part of the expression. Consequently, the BaseQuery should not be changed after any query manipulation has been done. However, it is quite common for applications to need to set this when an SDO instance is launched. (For example, to filter data on department or company key based on the userid.) Various examples and documentation have shown and stated that this can be done in an initializeObject override before the call to SUPER. In particular, older documentation examples showed this being done with setOpenQuery, which also synchronizes the physical query by calling QueryWhere. This was a problem on a client since setQueryWhere used to always prepare the physical query. setQueryWhere has since become more lightweight, but setOpenQuery still calls the server and should still be avoided in an AppServer session. Note: OE00110532 Type: Known Issue stripLookupfields is not used in the new lookup API --------------------------------- In previous versions, the stripLookupFields procedure was called on each display to figure out if the SmartDataFields could be resolved by the viewer's DataSource. The new lookup API does not use this procedure. Note: OE00111488 Type: Limitation SDO Cache does not include Auditing & Comments tick-information --------------------------------- The data caching and data sharing support does not always cache auditing and comment information. This information is retrieved only for certain instances and would only be cached if the actual object that did the initial server retrieval was set up to include this information. Data objects that retrieve their data from the cache may thus be unable to show the correct tick-mark in the toolbar if the initial server request did not include this information. Note: OE00112018 Type: Limitation Sharing data object, browse and viewer out of sync showing data --------------------------------- The support for SharedData does not actively refresh viewers or browse viewports when data is changed by another DataObject. To refresh a browse, you must currently scroll the record out of the viewport. To refresh a viewer, you must currently navigate to another record and back. Note that a viewer on a hidden page does not refresh itself if it is on the same record as when it was hidden. So, in this case, it does not help to navigate to another record and back in the browser. Note: OE00112062 Type: Limitation DynCombo support for a DataObject as data source does not include static SDO --------------------------------- The option to define an SDO DataSource for a DynCombo is not supported for static SDOs. Note: OE00112320 Type: Known Issue BaseQuery must have NO-LOCK after WHERE --------------------------------- A child SDO loses parent filter criteria if its BaseQuery has the NO-LOCK option before the WHERE criteria. When two SmartDataObjects are linked in a parent/child relationship, with or without a SmartBusinessObject, the child SDO might lose its filtering by the parent SDO. In previous versions, this happened if the child SDO was generated by the Object Generator with Follow joins turned on. This generated a BaseQuery with NO-LOCKs before the join criteria and caused the ADM to add the foreignfield criteria to the query incorrectly. As a workaround, opening and saving the SDO in the AppBuilder alters the BaseQuery to put the NO-LOCKs after the join criteria as expected by the ADM. Note: OE00112600 Type: Limitation Widgets on static SmartDataBrowser are not enabled on dynamic containers --------------------------------- When a static SmartDataBrowser contains other objects on its frame, those objects are not enabled when the static SmartDataBrowser is run on a dynamic container. When that static SmartDataBrowser is run on a static container, those objects are enabled. Note: OE00112836 Type: Known Issue assignNewValue w/ invalid values behaves different in new lookup API --------------------------------- The old and new lookup APIs behave differently when passing invalid value parameters to assignNewValue if the lookup key field is different from the lookup displayed field. With the old API (pre-2.1B/10.0B02 behavior and 2.1B/10.0B02 behavior with keep_old_api set to TRUE), passing an invalid key field value or an invalid displayed field value to assignNewValue displays blank in the lookup field when assignNewValue is invoked. If changes to the record are saved, blank is stored in the record's key field. With the new API (2.1B/10.0B02 default behavior), passing an invalid key field parameter displays blank in the lookup field when assignNewValue is invoked. If changes to the record are saved, the previous value displays in the lookup field and the value is not changed in the record's key field. Passing an invalid displayed field parameter displays the invalid value in the lookup field when assignNewValue is invoked. If changes to the record are saved, the previous value displays in the lookup Note: OE00115074 Type: Behavior Change Changes to how decimal values are managed in dynamic combos --------------------------------- There were several problems in previous releases developing decimal dynamic combos with default flag values that contain a numeric decimal point and deploying with different numeric formats. Default flag values were always stored in the format used during development. This prevented deployment to numeric formats other than the one used for development. Either errors displayed and no data displayed in the combo or incorrect data was stored in the repository for the or option. With 2.1B01, 10.0B03 and 10.1A this has changed to store default flag values with American numeric format. They should be entered in the SmartDataField maintenance tool using the session's format but the tool will replace the numeric decimal point with a period in the stored value. At runtime, any stored periods in the data are replaced with the current session's numeric decimal point. A fix program runs as part of the DCU Upgrade to convert existing default flag values for decimal dynamic combos to American format. The DCU must run in the format that was used to develop dynamic combos. The fix program writes a message to the log file for each default flag value it attempts to convert. It writes a message when a value is converted successfully or writes a message if the conversion fails. Review the DCU log file after the upgrade and manually correct any failures. Any failures that are not corrected may not behave properly at runtime as the runtime has changed to attempt to convert stored American formats to the format of the running session. There are several Dynamics objects in the repository that store blank default flag value instance attributes and give messages in the log file. These are for the cbSCMTool dynamic combo on the following viewer objects: gsmsxgenviewv gsmsxotviewv gsmsxpmviewv The messages for these objects are expected and you can ignore them. Any dynamic combo instance attributes stored in static viewer code in your application must be converted manually to American numeric format. Note: OE00116096 Type: Known Issue IndexInformation property only contains information for primary table(s) --------------------------------- The IndexInformation property has been changed to only contain index information for the table(s) that are uniquely represented in one row in the SDO query. The default table(s) are the EnabledTables or the first table for read-only SDOs. The getIndexInfoTables function determines which tables' info is added to the property. This is not implemented as a property, but can be overridden if different behavior is needed. If you want the old behavior all data objects, then add a custom version that returns the value from getTables (all tables in the query). Note: OE00121218 Type: Known Issue The Export to Excel functionality removes leading zeros from character strings --------------------------------- The Export to Excel functionality removes leading zeros from character strings. Note: OE00124494 Type: Behavior Change UndoChange action added to all tableio toolbars --------------------------------- Beginning with version 10.1B all shipped toolbars and tableio bands contain a new UndoChange action. This action replaces the old Reset action as the default in these toolbars. This constitutes a behavior change (label and accelerator) for existing applications that use the shipped toolbars or bands, since the caption is changed to "Undo" instead of "Reset" and the accelerator is changed to "CTRL-Z" from "ALT-R". The new UndoChange action defines some of the translatable text needed for the context sensitive text in the admmsgs.i include, message number 97. Customers that use the shipped toolbars or bands and want to remove the new action and get the old one back need to customize the class or toolbar. Customers that already have specific toolbars might need changes either to be able to use the new action or to remove it. To remove (hide) the new UndoChange action and get Reset back in shipped toolbar or band: ------------------------------------------------------------------- The Reset action is already present in the toolbar, so in order to make the Reset into default, the UndoChange needs to be added to the comma-separated HiddenActions property. Existing customer toolbars -------------------------- Existing customer toolbars may or may not get the new UndoChange action. If the toolbar or menu is defined with the "Tableio" category or one of the tableio bands, then the action is added automatically. But, many toolbars add tableio actions specifically in initAction() or initMenu() overrides in order to control the order and add rules. The "UndoChange" will need to be added to these. customized initAction --------------------- Since the getTableioUndoNew may need to load the actions if it is called from a visual object before the toolbar is initialized, the toolbar initAction has been changed to setIsActionsLoaded(true). Overrides of initAction that do not call super must add the same call, using dynamic-function or the {set~ include. Note: OE00135094 Type: Limitation DynLookup limit on number of joins may vary on DataServers --------------------------------- In Release 10.1C, the DynLookup supports a join with up to 18 tables instead of 10. But, this limit might not apply when using a DataServer, because there also is a limit decided by the size of the ROWIDs in the tables. The ROWIDs of the tables are added to an indexed RowIdent field and the ABL has a limit on the size of an index. Starting with Release 10.1B, as long as -tmpbsize 4 (default) or larger is used, temp-tables use large index keys and can store up to 1970 characters. This means that, in theory, you can store and index up to 16 ROWIDs returned from MSSQL server ( 16 * ( 116 + 1 ) - 1 = 1871 characters for rowids + separators). The different DataServers will return ROWIDs with different lengths, so the limit will vary. If this limit is an issue, then you can edit the af/app/afgettemp.p procedure and remove the following index definition. ---- hTT:ADD-NEW-INDEX("idxRowIdent":U,FALSE,FALSE). hTT:ADD-INDEX-FIELD("idxRowIdent":U,"RowIdent":U,"asc":U). ---- The index is used in certain reposition operations on the client. Removing it has an affect on performance, but this might be unnoticeable or acceptable since the operation is done on the temp-table on the client. Note: OE00161453 Type: Limitation Toolbar never creates a Band more than once per toolbar instance --------------------------------- The toolbar creates only a single instance of each Band for a toolbar instance. However, the Repository allows multiple instances of the same Band on a toolbar. Before Release 10.1C, the toolbar created the multiple instances of the same Band, but the second instance had no menu items. In Release 10.1C, the second instance of a Band is ignored completely. Note: OE00162048 Type: Workaround **Widget ID not unique () error for recursive Dyn TreeViews --------------------------------- The "Runtime Widget-ID Assignment" tool assigns default gap values for the imported SmartObjects. These default values should work without problems in most cases. But, for Dynamic TreeViews with structure nodes, the default gap value of 2000 for "TreeNode" might not be large enough. Since the nodes are created at runtime according to the database data, it is impossible to know how many tree node levels are going to be created in the Dynamic TreeView. If this happens and the default gap value of 2000 is not enough, that default value should be increased as specified in the "Application Development Environment (ADE) Addenda" Web paper in the "Widget IDs for ADM2 and Progress Dynamics" section. Note: OE00176891 Type: Limitation dynlaunch.i fails in thin client with DATETIME, DATETIME-TZ, RAW or ROWID param --------------------------------- Calling a PLIP using dynlaunch.i fails in a thin-client environment if the procedure call includes DATETIME, DATETIME-TZ, RAW or ROWID parameters. The client will report this error: Mismatched number of parameters passed to routine . (3234) The AppServer agent will report these errors: BUFFER-FIELD was not found in buffer ttSeqType. (7351) Lead attributes in a chained-attribute expression (a:b:c) must be type HANDLE or a user-defined type and valid (not UNKNOWN). (10068) The workaround is to implement calls with these data types to run as external procedure calls on the AppServer. e.g. RUN xxx on gshAstraAppServer (INPUT ...) Alternatively, you might add CASE statements for the 4 data types in obtainInitialValueField in adm2/caller.p. (This has not been tested, but is assumed to be the problem.) Note: OE00191743 Type: Known Issue Dynamic SDO with join require calculated fields to be defined in table order --------------------------------- In a Dynamic SDO based on a join, calculated fields will behave incorrectly under these circumstances: - Both tables in the join have calculated fields defined in the Repository's entity definitions. - Both tables also have one or more of these SDO Entity calculated fields included in the SDO. - The calculated fields from the right-hand table of the join appear before those of the left-hand table in the list of fields in the SDO. Symptoms include incorrect formatting and incorrect initial values being provided, as well as calls to the SDO data logic procedure failing with errors relating to temp-table schema mismatches. ================================================ ADE Tools and Runtime - Services ================================================ Note: OE00016261 Type: Limitation Record level transaction hooks must be implemented in the Data Logic Procedure --------------------------------- You must implement a static SmartDataObject's record level transaction hooks (create*, write*, and delete*) in the Data Logic Procedure. They will only fire from the SDO if the SDO does not have a Data Logic Procedure. Note: OE00106187 Type: Known Issue Static SmartDataFields (e.g. SmartSelect) cannot be translated. --------------------------------- SmartSelect objects are not presented for translation in the Translation window at runtime. The work around is to enter translations of SmartSelects in the Translation Control tool. The same naming convention as for Lookups is used. You must specify the Widget Type as 'FILL-IN' and the Widget Name as 'fiLookup' in all cases. You must enter the Object Name as :. If the static SmartDataViewer containing the SmartSelect is used in a static container, you must enter the file name of the viewer, including the extension (.w), in the Object Name. If the viewer is used in a dynamic container, you must enter the object name of the viewer, without any extension. This is an example based on a viewer for the Warehouse table using a SmartSelect for the 'State' field. The file name of the viewer is 'warehousesdv.w'. Translation for use in a static container: Object Name: warehousesdv.w:state Widget Type: Fill In Widget Name: fiLookup Translation for use in a dynamic container: Object Name: warehousesdv:state Widget Type: Fill In Widget Name: fiLookup Note: OE00108151 Type: Behavior Change Info for all users sent to client --------------------------------- When a user attempts to login in a client-AppServer configuration, the entire list of users is sent from the AppServer back to the client. This may be an expensive operation when there is a large number of users in the repository. To reduce this overhead, adding the session property "abbreviatedUserTable" to all client and AppServer session types and setting its value to "YES" will result in only the user that is logging in having his data shipped across from the AppServer, thereby reducing the traffic. Note: OE00123050 Type: Limitation The DataView does not support Dynamics Comments and Auditing --------------------------------- There is no default support for Comments and Auditing when DataViews and ProDataSets are used. The following error is returned when attempting to save a comment for a DataView: BUFFER-FIELD RowUserProp was not found in buffer .(7351) The Server Interface implementation could define a RowUserPropfield in the entity temp-table to store the information needed to trigger Auto Comment and show tick marks in the Dynamics toolbar's Auditing and Comment actions, similar to how the SDO handles it. Using this field might make it easier to use existing Repository Manager APIs and reuse existing SDO code. Note that the Auditing and Comment information is stored with delimiters in the field. This makes it difficult to use outside of the ADM and difficult to populate. The population have to be done for each record and will likely affect performance. Note: OE00125984 Type: Behavior Change Translated labels and widgets on same row but different column --------------------------------- When translating static viewers where KeepChildPositions=Yes, translated labels now use the existing label's width only. Also when translating static viewers, the label's font, rather than the widget's font, is used to determine the width of the label. The translation of simple (LIST-ITEMS) combo-box labels is now supported for dynamic viewers. When translating dynamic viewers with KeepChildPositions=Yes, the label moves to the bottom (back) so that it doesn't overlay any widgets to its left. The label is not truncated, unless it is longer than the space available. Note: OE00127924 Type: Known Issue Progress Dynamics can't find the help file during AppServer sessions --------------------------------- When the help file is set in the "security control" window, Progress Dynamics can't find the help file using the help-menu-item in an AppServer session. Note: OE00128539 Type: Behavior Change Dynamics translated application: performance problems on login --------------------------------- Support has been added for a session property called "cached_translations_only" which is set via the session definition (in the XML file and/or repository). In the absence of such a property in the session, the default is YES (the historical value). If cached_translations_only is false, then translations are not retrieved at startup, but rather on demand when an object is translated. ================================================ ADE Tools and Runtime - Tools ================================================ Note: OE00021013 Type: Known Issue scm_checks_on in Security Control is not supported --------------------------------- In Security Control, there is a toggle that switches on and off checks for the use of an SCM tool. The use of this setting is not yet implemented in all the places where it is relevant to check for this setting. SCM functionality is always enabled when the SCM tool (Roundtable) is in use with Progress Dynamics. Note: OE00024983 Type: Known Issue Fields hidden on DynView master layout in design mode if custom layout exists --------------------------------- If a field on a master layout has its HIDDEN attribute set to TRUE, the viewer typically displays the field in design mode. However, if a customized layout is made for the viewer, the viewer does not display the hidden field when the viewer reopens. This is inconsistent with the normal behavior for displaying hidden fields in master layouts. If you need to modify a hidden field in this situation, use the ROM tool. Do not modify the hidden field by using the 'List Objects' button to bring up the property sheet. Doing so removes the field instance. Note: OE00035615 Type: Known Issue Netscape Default HTTPS and SSL Support --------------------------------- The AppBuilder uses two OCX controls for remote file management (RFM) for WebSpeed. One of these controls, CIHTTP v4.00.002, comes from Crescent. According to current Crescent FAQ documentation on their Web site, OCX controls do not work with a secured server. Note: OE00045969 Type: Known Issue Double Dot Path Notation Causes Failure --------------------------------- When using Netscape WebServers with an NSAPI messenger, the WebServer might general protection fault if passed a .gif file location that uses a double dot path notation that goes higher than the docroot, for example, ..\msthemes\auto.gif. To avoid this problem when using an NSAPI messenger, do not specify .gif file locations using double dots if that notation goes higher than the docroot. Note: OE00070627 Type: Known Issue Toolbar object modifications are not updated in the Toolbar --------------------------------- 011A90108 Toolbar data are cached on the client as soon as they have been read once from the server, so when actions, bands and/or toolbars are changed in the Toolbar and menu designer these changes will not always be reflected in new instances of toolbars. Running the Dynamic Launcher and checking the 'Destroy ADM super-procedures' option will ensure that toolbar data are refreshed. The other option is to restart the session. Note: OE00086609 Type: Known Issue HTML after WSTag not sent if WSTag runs another WebSpeed object --------------------------------- If a SpeedScript file contains a WSTag tag that runs another WebSpeed object, the remaining HTML after the WSTag tag is not sent to the Web browser. Note: OE00088031 Type: Known Issue DataFields cut/copied then pasted are associated with RowObject --------------------------------- There is an issue when you cut or copy DataFields from one dynamic viewer and then paste them to another dynamic viewer built from the same SDO. Until you save and reopen the second viewer, the AppBuilder shows the new fields as being associated with the RowObject table instead of their actual database table. Note: OE00093984 Type: Known Issue Copy-Paste in DynView is not keeping all the attributes of the widgets --------------------------------- When copying widgets from a DynView to another DynView, some widget attribute values are missed. For example, when a fill-in is copied, the values of the ShowPopup and Label attributes are missed in the target DynView. This happens for all attributes that are read from the Repository. Note: OE00097484 Type: Known Issue Client cache viewer tool returns errors --------------------------------- The client cache viewer tool no longer works when run against a current version of the Repository API. Note: OE00098133 Type: Known Issue Error 560 Generating Objects From SDO --------------------------------- Error 560 (Entry outside the range of list) is raised when the Object Generator is used to create dynamic objects from a prebuilt SDO when the SDO has been created by the Object Generator, and has subsequently had other tables manually added, and the product module has sublevels in the path. Note: OE00103384 Type: Known Issue RTB: Problems when dyn object and super proc in different module --------------------------------- When modifying a dynamic object where the dynamic object and its super procedure were created in different product modules, the following error may occur: The product module and the product module must be the same. (AF:110) Note: OE00107793 Type: Known Issue Dynamic Lookup maintenance window does not destroy its maintenenance SDO --------------------------------- The Dynamic Lookup maintenance window does not destroy its SDO and associated Data Logic Procedure Whenever you open the maintenance window of the dynamic lookup from the dynamic lookup browse, the system launches a new instance of the maintenance window's SDO and its associated DLP. However, these objects are not destroyed upon closing the maintenance window. Note: OE00107875 Type: Known Issue Cascading security allocations does not work for Data Security --------------------------------- The option to cascade security allocations from a profile user does not work for Data security. Note: OE00109408 Type: Limitation Help cannot be mapped to static container run from the AppBuilder --------------------------------- It is not possible to map help for a static container that has been run from the AppBuilder. The container must be run from the Dynamic Launcher to map help for it. Note: OE00168684 Type: Known Issue Error 7452 in Dynamics Dataset Export Filter --------------------------------- Customers using European numeric settings might see the 7452 error when pressing the filter button on the Dataset Export screen. Note: OE00170170 Type: Known Issue Error: The Root node code must be specified. (AF:1) when creating Dyn TreeViews --------------------------------- When entering data in the "Dynamic TreeView Builder" tool, you must enter the "Object filename" value first. If you do not enter the Object filename first, you see the "Root node code must be specified. (AF:1)" error upon saving the data. Note: OE00232771 Type: Behavior Change RESULTS now supports database type MSS --------------------------------- RESULTS now supports database type MSS. ================================================ ADE Tools and Runtime - Translation Manager ================================================ Note: OE00102201 Type: Known Issue Changing the TranMan Language combo may cause error (132) --------------------------------- Changing the selected language on the TranMan Data Tab combo does not display the correct translations after using the 'View', 'Sort' option from the pull down Menu. Double clicking on some rows might give the following error: ** This Translation already exists with Sequence number Instance Number Language Name "". (132) Note: OE00110396 Type: Known Issue Creating a zip file on removable media causes zip errors --------------------------------- Creating a zip file on removable media causes the following errors: Error occurred while accessing component property/method: MultiVolumeControl. Out of present range. Error code: 0x8002000a Zip adetran/common/_zipmgr.w (5890) Zip: Couldn't open to write. (15). Note: Creating a zip file on non-removable storage functions properly. Note: OE00224401 Type: Known Issue Creating a .zip file on removable media from Visual Translator causes errors --------------------------------- Creating .zip file on removable media from Visual Translator causes the following errors: Error occurred while accessing component property/method: MultiVolumeControl. Out of present range. Error code: 0x8002000a Zip adetran/common/_zipmgr.w (5890) Zip: Couldn't open to write. (15). Note: Creating a .zip file on non-removable storage functions properly. ================================================ ADE Tools and Runtime - Web Rendering ================================================ Note: OE00040946 Type: Limitation Avoid changing Foreign Keys in Web Objects with joined queries --------------------------------- When you use the Detail Wizard to create a Web object that contains a join, do not make the foreign key field updateable. If you change the value of the foreign key in a record, the next stateless request might not be able to find that record. When this happens, you get an error that the query could not reposition to that record. If your application needs the ability to update the value of the foreign key in a joined query, you must make sure that the list of ROWIDs in the "CurrentRowids" attribute contains ROWIDs of the newly joined table, instead of the originally-joined table. Note: OE00135596 Type: Known Issue Two undo/reset buttons on the Standardtoolbar --------------------------------- The new UndoChange toolbar action is not supported in Dynamics Web. By default, UndoChange replaces the Reset action in shipped toolbars and Tableio bands. When these toobars and bands are realized in the Web, the Reset button and menu item remain and function correctly. However, the UndoChange action may also be realized at runtime as a non-functioning button and menu item, labeled "Undo 1 (CTRL-Z)". In order to suppress the UndoChange button and menu item, the UndoChange action can be set to Hidden, or added to the HiddenActions property, for the toolbar. For additional information, please see the note for the new UndoChange action under GUIRENDR / SmartToolbar in this document. ================================================ AppServer - ================================================ Note: OE00221745 Type: Behavior Change Support for Actional is removed --------------------------------- Support for Progress Actional (including all Actional interceptors for OpenEdge), which was first introduced in OpenEdge 10.2B, is removed from OpenEdge Release 11.1. Note: OE00238571 Type: Limitation SSL connectivity using certificates that expire 2014 --------------------------------- Clients and adapters of OpenEdge 11.2.1 or earlier releases will not establish SSL connections with an OpenEdge 11.3 AppServer that uses a built-in server test certificate because the test server certificate and the CA certificate expire after February 2014 so they will not validate the SSL connections. Workaround: 1. Use OpenEdge 11.3 clients and adapters with an OpenEdge 11.3 AppServer that uses a built-in test certificate. 2. Create your own server certificate and CA certificate to establish SSL connections between clients and adapters of OpenEdge 11.2.1 or earlier releases and an AppServer of OpenEdge 11.3. Do not use the OpenEdge 11.3 AppServer built-in certificates. ================================================ AppServer - Broker ================================================ Note: OE00203472 Type: Known Issue Startup time of AppServer broker increases when SSL is enabled (Linux and UNIX) --------------------------------- After upgrading to OpenEdge Appserver V11, the AppServer broker's startup time might increase if SSL is enabled. This happens if /dev/random is not populated with random data. The SSL libraries used by the AppServer broker require several kilobytes of random data to properly secure SSL connections to the broker. To resolve the issue, ensure that /dev/random is populated with enough random data. There are two possible solutions: - Move /dev/random to /dev/random_bak, and then add a simlink from /dev/random to /dev/urandom. This makes /dev/random reference /dev/urandom. Note that /dev/urandom is less secure. - Install and run rngd, the random number generator daemon. It increases the entropy pool used /dev/random to provide random data. ================================================ Auditing - ================================================ Note: OE00238705 Type: Workaround 11.3.0 new audit events not present in policies.xml --------------------------------- The policies.xml file stores auditing policies for OpenEdge system events for convenience, and you can load the xml file to enable auditing on all supported system events. In Release 11.3, new system events for proutil auditreconfig and MT Data Move (proutil datamove) are introduced, but not included in the polices.xml file. To enable auditing on these new events, you need to manually create auditing policies through either an ABL program or the Auditing Policy Maintenance tool in the Data Dictionary. ================================================ BP Server - ================================================ Note: OE00233289 Type: Known Issue Web Service adapter configured with ABL datatypes as undefined is suspended --------------------------------- The Web Service adapter gets suspended if you have configured the Web Service adapter with native datatypes that are marked are undefined. You must set a values of the native datatypes in pre-script before the Web Service adapter is invoked. Note: OE00234856 Type: Limitation EJB Server does not start when hostname has _ --------------------------------- The EJB Server does not start when hostname has "_". This is a limitation with JBoss application server. Note: OE00236343 Type: Known Issue Alert configured with the Schedule Rule Wizard does not work --------------------------------- An alert having a recipient mapped to a dataslot and configured to the Schedule Rule Wizard does not execute at run-time. Note: OE00237587 Type: Known Issue XML file name is modified on setting or copying the XML dataslot value --------------------------------- When the XML dataslot value is set or copied from another XML dataslot, name of both the XML files are modified while the content is copied. Note: OE00237787 Type: Limitation OE BP Server database not visible in OpenEdge Management after reinstallation --------------------------------- Uninstalling OpenEdge BP Server does not remove the BPM database. When you reinstall it, the database is not overwritten even if the "Create Database" option is selected during installation. This is done to prevent destroying customer data. If you are reusing an existing BPM database and want it to display in OpenEdge Management, stop the database using the "stopdb" script in the database directory, and then restart the database using "dbman -start -db ". Alternatively, if you want a new database then specify a new BP database name during installation. Note: OE00237881 Type: Known Issue ABL client crashes while fetching tasks --------------------------------- If a presentation type has metadata as a system dataslot, the ABL client crashes while fetching tasks. System dataslots must not be defined in configuration for presentation types. Note: OE00238254 Type: Behavior Change TIMEZONE function is not preserved with the Business Process Server --------------------------------- The ABL API TIMEZONE function is not preserved when working with the Business Process Server. The Business Process Server returns datetime values to ABL in GMT time zone. You must convert the GMT time zone value to your time zone. Note: OE00238462 Type: Known Issue ABL DECIMAL type values cannot be assigned to DECIMAL dataslot --------------------------------- You cannot assign the maximum '50' and minimum '0' values of the ABL DECIMAL datatype to a DECIMAL dataslot which is created in OpenEdge BPM Designer. The DECIMAL dataslot does not support to hold the maximum and minimum values of the ABL DECIMAL type. Note: OE00238578 Type: Known Issue Archiver events are not purged when -delete option is used --------------------------------- Scheduler does not choose the config file that is provided in the archiverscheduler.properties file instead it uses the archiverprocesspurge.xml file. Note: OE00238620 Type: Known Issue ABL APIs related to working with tasks fail with single sign-on --------------------------------- Users logged in with single sign-on and who is not defined on the Business Process (BP) Server will not be able to use the ABL APIs related to working with tasks such as gettask( ) or getassignedtask( ). The user must be created in the BP Server to use the task-oriented APIs when the user performs a SSO to log into BP Server. Note: OE00239453 Type: Known Issue Error is displayed when email escalation is assigned for a collaborative task --------------------------------- When you enable email notification as the escalation action for a collaborative task, an error is displayed and the escalation action does not complete. Note: OE00239544 Type: Known Issue sbm.log file reference is displayed on the Prepare Repository error dialog box --------------------------------- The Prepare Repository error dialog box displays the sbm.log file reference. The sbm.log is now changed to oebps.log and is located in your OpenEdge installation folder at $dlc\oebpm\server\log. Note: OE00239795 Type: Known Issue Archiver events are not purged when -delete option is used --------------------------------- Scheduler does not choose the config file that is provided in the archiverscheduler.properties file instead it uses the archiverprocesspurge.xml file. ================================================ BPM Classes - ================================================ Note: OE00223838 Type: Limitation Process:ActivateWorkstep() requires a valid performer for Monitoring Process --------------------------------- If you use Process:ActivateWorkstep() with an external workstep in a Monitoring Process, there is currently a limitation that the performer you specify must be defined in your process. Note: OE00233525 Type: Limitation BP Server DataSet CLOB supports only UTF-8 --------------------------------- When you populate a dataslot with a DataSet value that contains a CLOB field, the format must be UTF-8. If your source data is in another format, it must be converted to UTF-8 using ABL statements. For example: COPY-LOB FROM m2 TO etable1.clobFld CONVERT TARGET UTF-8. ================================================ BPM Studio - ================================================ Note: OE00229027 Type: Workaround Unable to add dataslots to activity that is updated using Form Designer --------------------------------- You cannot add dataslots from the "Fields" section of the "Properties" view, to an activity that is updated using Form Designer. You must open the form in Form Designer, delete all the designed contents, and save the form. You can then add dataslots from the "Properties" view. Note: OE00235975 Type: Workaround Business Objects imported using schema file do not have Types Information --------------------------------- When you import Business Objects from a schema (XSD) file, Types are not listed against the source file in the Business Object Manager dialog box. You must import Business Objects using only XML and Java Beans files. Note: OE00236277 Type: Workaround Dataslot properties are not persistent --------------------------------- Dataslot properties such as initial value, default format options, and validations do not persist when you export and import dataslots using a Comma Separated Value (CSV) file. For the dataslot properties to be persistent, you must use an XML file to export and import dataslots. Note: OE00237590 Type: Limitation Role information is not imported from the BPM server --------------------------------- When you import the Organization hierarchy from the BPM server using the User Management tool in BPM Studio, the role configured for the user in a group is not imported. Note: OE00237921 Type: Limitation No options are available to write a condition based on the unknown value --------------------------------- If the dataslot type is DATETIMETZ, CHARACTER, or INTEGER, there is no option to write a condition to check if the value of a dataslot is UNKNOWN. You must add a condition so that the dataslot is null such as DataslotName==null, while defining condition against the selected connection using the "Advanced" option in the "General" tab. Note: OE00238222 Type: Workaround Changes to a few dataslot properties are not reflected in activity properties --------------------------------- Modifying default format values like Required, Label, Editable, and Type in the dataslot tab does not change the values in activity properties (in the Fields tab). You need to change the properties of each activity manually by clicking Modify. However, a new activity created inherits the modified properties. Note: OE00238282 Type: Known Issue Description of controls cannot have double quotation marks --------------------------------- In BPM forms, if the description of a control has special characters like double quotation marks (""), an exception is thrown when you generate the form preview of the control. Note: OE00238372 Type: Limitation Process Modeler throws an error when you try to export template to XPDL --------------------------------- Process Modeler throws an error when you try to use the "Templates to XPDL Process" option. Note: OE00238861 Type: Limitation Remote sub-processes cannot be invoked --------------------------------- Only sub-processes available in the deployed server can be invoked. Specifying details for the remote a sub-processes such as server URL, does not change the outcome. The process will only invoke a sub-process that is available in the server that is deployed. Note: OE00238928 Type: Workaround Business Objects not reflected in dataslot workspace until process is re-opened --------------------------------- Newly created Business objects are not reflected in the dataslot workspace until you reopen the Process Editor. Note: OE00239068 Type: Known Issue Control with validation message does not display on the Form Preview --------------------------------- When you add a validation message with a line added to the message using the ENTER key to a control on the Form Editor, the dataslot does not display on the Form preview and at run-time. Note: OE00239106 Type: Known Issue Issue with copying and pasting an adapter to another workstep --------------------------------- After you have copied an adapter which is associated with a workstep to another workstep in the process and then modified configurations of the copied adapter, the source adapter configurations are changed and its associated workstep might not work as intended. ================================================ BPM Web Flow - ================================================ Note: OE00238300 Type: Limitation Importing a Microsoft Project Exchange (MPX) file does not work --------------------------------- After you import a Microsoft Project Exchange (MPX) file as a Web Flow project, empty BizSolo process is created. ================================================ Business Process Modeler - ================================================ Note: OE00238459 Type: Known Issue Table control events added on the Form Editor are not displayed at run-time --------------------------------- The events such as onClick, onMouseDown, or onKeyPress defined for a table control on the Form Editor, do not execute when deployed on the Business Process Server. These events do not display in the Form Preview and at run-time. Note: OE00239847 Type: Limitation Role information is not imported from the BPM server --------------------------------- When you import the Organization hierarchy from the BPM server using the User Management tool in BPM Studio, the role configured for the user in a group is not imported. Note: OE00239849 Type: Workaround Unable to add dataslots to activity that is updated using Form Designer --------------------------------- You cannot add dataslots from the "Fields" section of the "Properties" view, to an activity that is updated using Form Designer. You must open the form in Form Designer, delete all the designed contents, and save the form. You can then add dataslots from the "Properties" view. Note: OE00239854 Type: Known Issue Document dataslots get converted to String dataslots on process migration --------------------------------- After you migrate projects from the Savvion 7.6.1 or 8.0 to OpenEdge 11.3, Document datalots defined in the Savvion process are converted to String dataslots in OpenEdge. Note: OE00239857 Type: Workaround Changes to a few dataslot properties are not reflected in activity properties --------------------------------- Modifying default format values like Required, Label, Editable, and Type in the dataslot tab does not change the values in activity properties (in the Fields tab). You need to change the properties of each activity manually by clicking Modify. However, a new activity created inherits the modified properties. Note: OE00239858 Type: Workaround Business Objects imported using schema file do not have Types Information --------------------------------- When you import Business Objects from a schema (XSD) file, Types are not listed against the source file in the Business Object Manager dialog box. You must import Business Objects using only XML and Java Beans files. Note: OE00239860 Type: Limitation Options are not available to write a condition based on the UNKNOWN value --------------------------------- If the dataslot type is DATETIMETZ, CHARACTER, or INTEGER, there is no option to write a condition to check if the value of a dataslot is UNKNOWN. You must add a condition so that the dataslot is null such as DataslotName==null, while defining condition against the selected connection using the "Advanced" option in the "General" tab. Note: OE00239861 Type: Workaround Dataslot properties are not persistent --------------------------------- Dataslot properties such as initial value, default format options, and validations do not persist when you export and import dataslots using a Comma Separated Value (CSV) file. For the dataslot properties to be persistent, you must use an XML file to export and import dataslots. Note: OE00239862 Type: Known Issue Description of controls cannot have double quotation marks --------------------------------- In BPM forms, if the description of a control has special characters like double quotation marks (""), an exception is thrown when you generate the form preview of the control. Note: OE00239864 Type: Limitation Importing a Microsoft Project Exchange (MPX) file does not work --------------------------------- After you import a Microsoft Project Exchange (MPX) file as a Web Flow project, empty BizSolo process is created. Note: OE00239865 Type: Known Issue Dates displayed in the custom header or footer sections are incorrect --------------------------------- If a custom header or footer has data related to a variable date value (start or due date, for example), the values displayed are incorrect. The date displayed is a static value. Note: OE00239866 Type: Known Issue Table control events added on the Form Editor are not displayed at run-time --------------------------------- The events such as onClick, onMouseDown, or onKeyPress defined for a table control on the Form Editor, do not execute when deployed on the Business Process Server. These events do not display in the Form Preview and at run-time. Note: OE00239871 Type: Limitation Remote sub-processes cannot be invoked --------------------------------- Only sub-processes available in the deployed server can be invoked. Specifying details for the remote a sub-processes such as server URL, does not change the outcome. The process will only invoke a sub-process that is available in the server that is deployed. Note: OE00239872 Type: Workaround Business Objects not reflected in dataslot workspace until process is re-opened --------------------------------- Newly created Business objects are not reflected in the dataslot workspace until you reopen the Process Editor. Note: OE00239875 Type: Known Issue Control with validation message does not display on the Form Preview --------------------------------- When you add a validation message with a line added to the message using the ENTER key to a control on the Form Editor, the dataslot does not display on the Form preview and at run-time. Note: OE00239876 Type: Known Issue Issue with copying and pasting an adapter to another workstep --------------------------------- After you have copied an adapter which is associated with a workstep to another workstep in the process and then modified configurations of the copied adapter, the source adapter configurations are changed and its associated workstep might not work as intended. ================================================ Business Process Portal - ================================================ Note: OE00235983 Type: Limitation Users can belong to a maximum of 1015 security groups --------------------------------- Due to a limitation in LDAP, a user who is a member of more than 1015 security groups cannot log on. When a user logs on to a computer, the local Security Authority (LSA) generates an access token for the user to represent the security context of the user. The access token contains the user's unique security identifier (SID) and the SIDs of every group that the user is a member of, including transitive groups. The field that contains the SIDs of the user's group memberships in the access token can contain a maximum of 1024 SIDs. If a user (with an administrative user account or a non-administrative user account) is a member of more than 1024 security groups, the LSA cannot create an access token for the user during the logon attempt. Therefore, the user will not be able to log on. During access token generation, depending on the type of logon being performed, the LSA also inserts up to 9 well-known SIDs in addition to the SIDs for the user's group memberships (evaluated transitively). Because of this addition of well-known SIDS by the LSA, if a user is a member of more than 1015 security groups, the total will be larger than the 1024 SID limit. Therefore, the LSA will not be able to create an access token for the user during the logon attempt. (This 1015 number includes local group memberships of the computer that the user is trying to log on to.) Because the user cannot be authenticated, they cannot log on. Note: OE00237153 Type: Known Issue Portalserver start-up takes a long time on Unix Machines --------------------------------- The Portalserver start-up takes a long time, approximately 10 minutes, on Unix Machines. This happens only on the first start up. Note: OE00238146 Type: Known Issue Fields on Create Permission page are inter-dependent --------------------------------- When creating a permission with the following values: Component: Administration Resource : Application be aware that even though the "Action" field comes before "Application Type" field in the flow of the page, the values of the "Action" field change depending on the selection of "Application Type" field. Once you select the "Application Type", you may need to revisit the the "Action" field value to avoid any ACL related issues. Note: OE00238301 Type: Known Issue Dates displayed in the custom header or footer sections are incorrect --------------------------------- If a custom header or footer has data related to a variable date value (start or due date, for example), the values displayed are incorrect. The date displayed is a static value. Note: OE00238820 Type: Known Issue BPM forms cannot handle unknown --------------------------------- BPM forms cannot handle unknown values (?). An unknown value in any dataslot can be passed between adapters including the OpenEdge adapter. However, if there is any human workstep in between, then the dataslot value is reset to empty (for character) or zero (for int, int 64). Note: OE00238992 Type: Known Issue IP validation with 'IPv6' format fails on portal --------------------------------- IPv6 validation fails when a dataslot in the portal is correctly set for IPv6 validation. The portal reports an "Invalid entry" validation message even for valid IPv6 values. Only IPv4 validation is processed properly. Note: OE00240461 Type: Known Issue Issue using a Custom Adapter workstep with PAKCreatePI class --------------------------------- A custom adapter defined with 'PAKCreatePI' class, and with 'BIZSITE_USER', 'BIZSITE_PASSWORD', and 'ptName' as CHARACTER type dataslots does not function as designed. The class throws an exception at runtime when creating the instance process template with the provided template name (ptname). As a workaround, you must create a new class which extends the 'PAKCreatePI' class and add the following import statements and methods. You can then use the new created class with the custom adapter workstep. Note: Ensure that the "Generate Java Code" option is not enabled for the custom adapter in OpenEdge BPM Designer. IMPORT com.progress.lang.Character; IMPORT com.savvion.BizSolo.Server.PublicResources PUBLIC INT COMMIT() THROWS EXCEPTION{ covertPropertiesToStrings(); INT result = super.commit(); undoConvertPropToStrings(); RETURN result; } PRIVATE VOID covertPropertiesToStrings() { Object object = getPropObject(PublicResources.PT_NAME); IF (object instanceof Character) setPropString(PublicResources.PT_NAME, ((Character) object).getValue()); object = getPropObject(PublicResources.BIZSITE_USER); IF (object instanceof Character) setPropString(PublicResources.BIZSITE_USER, ((Character) object).getValue()); object = getPropObject(PublicResources.BIZSITE_PASSWORD); IF (object instanceof Character) setPropString(PublicResources.BIZSITE_PASSWORD, ((Character) object).getValue()); setPropString(PublicResources.MODE, PublicResources.STANDALONE_MODE); } PRIVATE VOID undoConvertPropToStrings() { Object object = getPropObject(PublicResources.PT_NAME); IF (object instanceof String) setPropObject(PublicResources.PT_NAME, new Character((String) object)); object = getPropObject(PublicResources.BIZSITE_USER); IF (object instanceof String) setPropObject(PublicResources.BIZSITE_USER, new Character((String) object)); object = getPropObject(PublicResources.BIZSITE_PASSWORD); IF (object instanceof String) setPropObject(PublicResources.BIZSITE_PASSWORD, new Character((String) object)); } ================================================ Database - ================================================ Note: OE00234366 Type: Behavior Change Database log messages contain GMT timestamps --------------------------------- During regular execution, when OpenEdge processes write to the database log file (.lg) the timestamp header of the message shows the time in local time format. This header with local time information includes the offset of the local time from Greenwich Mean Time (GMT). For example: "[2013/04/25@11:00:34.123-0400]" which shows that the time is 4 hours offset from GMT. On UNIX systems, when OpenEdge processes field exceptions (either internal fatal errors or signals from other processes), messages may be written to the database log (.lg) file from within the process' Signal Handler code. These messages, when written from the Signal Handler, show a timestamp header in Greenwich Mean Time (GMT) format. For example: "[2013/04/25@15:01:07.000+0000]" which shows that the time is actual GMT with 0 hours offset. In addition, the time information written from the process' Signal Handler does not show millisecond values. This change in timestamp formatting allows OpenEdge to avoid calling certain UNIX system functions which can cause a process to hang or not properly terminate if called from within the Signal Handler code. ================================================ Database - Database Utilities ================================================ Note: OE00153461 Type: Limitation On overflow condition, specified binary dump does not dump as expected. --------------------------------- While dumping data for a column with datatype BIGINT, an overflow condition occurs when the specified column value is larger than the max BIGINT value. No error message is generated, and the dump continues as if the number specified is a negative number. Note: OE00153473 Type: Limitation Negative integers are not supported by specified binary dump. --------------------------------- Negative integers are not supported by the specified binary dump utility as input parameters. You can dump all negative values by specifying a value range as "LT 0" for the column, but specifying any negative integer, such as "LT -1", fails. The specified binary dump utility cannot interpret command lines with a "-" negative sign in the input parameter on command line. Note: OE00192738 Type: Workaround dbutil.bat supports nine command line parameters --------------------------------- dbutil.bat supports 9 command line parameters. Use proutil.bat if your command line requires more than 9 parameters. proutil.bat supports 27 parameters. Note: OE00199451 Type: Behavior Change Promon output format is changed to include additional fields --------------------------------- In Release 11.0.0, new columns are inserted into promon reports to provide information on new fields, for example domains, tenants, and partitions. Refer to "OpenEdge Data Management: Database Administration" for more details. Understanding the change in column location is particularly important if you have scripts that parse promon output and act on the parsed results. Note: OE00230850 Type: Limitation Linux 8.3 Database Utilities don't work on currently supported Linux OS --------------------------------- The Progress Version 8.3 Database Utilities included in the $DLC/bin/83dbutils directory do not work with the currently supported Linux operating system versions for both 32-bit and 64-bit Linux releases. To upgrade an 8.3 database, you must perform the required truncate BI and 'prostrct convert' migration steps using an installed version of Progress Version 8.3 on a Linux operating system certified to run Version 8.3. Note: OE00237768 Type: Workaround The Data Move utility -domain option is not fully supported --------------------------------- When starting the Data Move utility (PROUTIL DATAMOVE) user interface (UI), the -domain command-line option is not fully supported when specified on the command-line when starting the UI. If the -domain option is specified, the -domain information is not properly passed to the process handling the data move and the utility may fail with a message of the form: "Error message "Authentication service: user authentication failed for . The user account does not exist" To work around this issue, you may alternately specify user account domain information by specifying the domain information with the -U command-line option with the domain specified on the user id string separated by an @ sign. For example: > proutil mydb -user myuser -domain mydomain -C datamove source mysrcdb is not supported, whereas: > proutil mydb -U myuser@mydomain -C datamove source mysrcdb is supported. ================================================ Database - Failover Clusters ================================================ Note: OE00147498 Type: Limitation Failover Clusters node ordering --------------------------------- The node the cluster chooses to fail over to is a default preference Clusters accepts from the cluster manager. If you want to tailor this, you must use your operating system cluster management utilities. Clusters does not alter node ordering. Note: OE00147499 Type: Limitation Failover Clusters excluding nodes from fail over --------------------------------- All clustered systems provide a means for disallowing hosts from hosting a resource. You must use your operating system cluster management utilities to do this. Clusters does not provide a means to disallow a host. Note: OE00147501 Type: Limitation Failover clusters helper processes that do not start on another machine --------------------------------- If any of the helper (APW, BIW, or AIW) processes or the watchdog process specified to start with a particular database fails, they will not be started on another machine during a failover. They will produce an OFFLINE status. Note: OE00147509 Type: Product Notice Failover Clusters Sun Cluster uses global devices --------------------------------- Clusters only supports databases stored on global devices. The Sun Cluster uses global devices to provide cluster-wide, highly available access to any device in a cluster, from any node, without regard to where the device is physically attached. In general, if a node fails while providing access to a global device, the Sun Cluster software automatically discovers another path to the device and redirects the access to that path. The local disks on each server are not multi-ported, and thus are not highly available devices. Multi-ported global devices provide more than one path to a device. In the case of multi-host disks, because the disks are part of a disk device group hosted by more than one node, the multi-host disks are made highly available. Note: OE00163001 Type: Known Issue Restarting on the same node -- HPUX only --------------------------------- A package that fails, attempts to switch to the next node on which it is configured to run. If you wish the package to restart on the node where the failure occurred, you must use the MC/ServiceGuard cmmodpkg utility to re-enable the package to run on that node. See your MC/ServiceGuard documentation for details regarding the syntax of this utility. Note: OE00192361 Type: Known Issue An encryption-enabled, manual start db cannot be started by failover clusters --------------------------------- You cannot start a database enabled for failover clusters with your operating system cluster resource manager if it is also enabled for transparent data encryption and configured for manual start. Failover cluster and encryption-enabled databases must be configured for autostart to be started by the cluster resource manager. If you attempt to start an encryption-enabled database configured for manual start with the operating system cluster resource manager, the actual startup fails, but the cluster resource manager may incorrectly report that the database has been started. ================================================ DataServers - ================================================ Note: OE00218857 Type: Behavior Change Always run r-code against the schema image of the original database --------------------------------- Position-independent rcode is "independent" of the physical position of a column in the foreign data source. That is, column positions in the server table can be rearranged without the need to recompile. However, introducing a new column or deleting an existing column from an existing record structure always requires the r-code to be recompiled against the new schema layout. The r-code is dependent only on a logical identification of the column, and not the physical position of the column. The logical identification, in the OpenEdge database, takes place before migrating to a foreign data source, and the logical identification does not change once the column is defined in the OpenEdge table. When the columns are rearranged on the server, the code need not be recompiled, but the foreign schema must be pulled back into the schema image. This is to ensure that the new physical position of a column is matched in the schema to the logical identifier that is also known to the r-code. You can only run r-code or load data (.d file) while connected to a schema image that is derived from the same database that was migrated and connected to the server when the code was first compiled and/or the data was first dumped. This ensures that the same logical column identifier is preserved after migration and/or after any subsequent schema pulls. Note: When the server table is re-pulled into the same schema image (after the columns are rearranged on the server), the logical column identifier is re-matched to the physical column position so that the r-code can find again the column in a run-time application. Note: OE00221190 Type: Behavior Change Prepended underscore dropped from OE-generated default constraint names --------------------------------- The OpenEdge dictionary tool allows you to generate constraint definitions that can be added in Oracle and MS SQL Server DataServers and then ported to foreign data sources. The generated constraint definitions are given default names that can be modified by the user before saving. However, the previous name generation algorithm placed an underscore at the beginning, followed by an acronym describing the type of constraint, another underscore, and then some object names associated with the constraint. The newly implemented name generation algorithm will work the same as the old but it will drop the underscore character from the first position. This is needed since underscore as the first character in an OpenEdge name is identified as an indicator of an OpenEdge metaschema object. To avoid confusion about object identification and to avoid name validation conflicts, the underscore prefix is no longer generated for default constraint names. Note: OE00234731 Type: Behavior Change Recompile r-code if the second operand of BEGINS operator is a column name --------------------------------- BEGINS In a query, if the second operand of a BEGINS operator is a column name then the query does not return any records even when the value of starts with . However, the query returns value if both the operands, and , are the same or is a string literal. Therefore, to get the expected behavior after applying this fix, you must recompile the r-code for all the applications that use a BEGINS operator with its second operand as a column name. ================================================ DataServers - MS-SQL ================================================ Note: OE00186542 Type: Workaround Techniques to load .d file when table has non-updatable column on MSSQLServer --------------------------------- In MSS DataServers, there is a restriction to a load operation from a .d file when the table has non-updatable columns (i.e. columns on MS SQL server are of type 'identity' or 'timestamp' or 'rowguid'). You can work-around this restriction by following one of the two options described below. Option 1:- Use dump/load tools of the foreign data source instead of data from a .d file to load your foreign table. Note: This is the only way to retain the original values from non-updatable columns. Option 2:- If the user wants newly generated values for non-updatable columns stored along side updatable fields from the given '.d' file, write an ABL program to read data from the .d file into a temp table and then skip non-updatable fields while writing the temp table records to the foreign table. Sample ABL code provided below to perform this task. Conside a table named "test" on SQL Server side with the sturcture as, TABLE [test]( [fld1] [int] IDENTITY(1,1) NOT NULL, [fld2] [varchar](50) NULL, [fld3] [varchar](50) NULL ) ****** sample ABL code ****** /* define temp table with the name Temptbl for table test */ define temp-table Temptbl like test. /* pouplate temp-table Temptbl from the records in the .d file name test.d */ INPUT FROM test.d. REPEAT: CREATE Temptbl. IMPORT Temptbl. /* create a record in the foreign DB */ CREATE test. BUFFER-COPY Temptbl EXCEPT fld1 TO test. END. INPUT CLOSE. ***************************** Note: OE00190218 Type: Known Issue SQLError not getting message with SNAC-10 driver. --------------------------------- New trigger solution (CR#OE00178470) generates 'PSC-init' and 'PSC-end' messages on trigger execution. Modified DataServer code gets these messages using SQLFetch()- SQLError - api calls for 2 times. Observed that SNAC-10 driver is not returning the PSC-end message as part of the 2nd time SQLFetch() with SQLError()- API calls. This is a 3rd party SNAC-10 driver issue. Confirmed the same by using a sample ODBC program. Note: This behavior has NO impact on DataServer functionality. Note: OE00195562 Type: Product Notice ZPRGRS_RECID_BUF_SIZE Option minimum value changed from 44 to 52 --------------------------------- The minimum RECID buffer size has changed to 52 (from 44). The ZPRGRS_RECID_BUF_SIZE option allows the RECID buffer size to be configured to a customized size for the DataServer session. NOTE: DO NOT INCREASE THIS VALUE IF THERE IS NO REQUIREMENT FOR IT. INCREASED BUFFER SIZES CAN HAVE A NEGATIVE EFFECT ON NETWORK PERFORMANCE RUNNING DATASERVER'S CLIENT/SERVER. This syntax is for setting the buffer size for the RECID area, -Dsrv ZPRGRS_RECID_BUF_SIZE,nnnn (where nnnn is the new size of the area in bytes. The range limits for nnnn are inclusive of values between 52 to 1024.) Note: OE00198360 Type: Product Notice Computed column support enabled by MSS DataServer prior to MS SQL Server 2005 --------------------------------- Computed columns are resolved differently in the server schemas prior to MS SQL Server 2005 when compared to how they are resolved in MS SQL Server 2005 and later versions. This fix properly resolves computed columns in server schemas prior to MS SQL Server 2005 so that computed columns are now correctly identified by the DataServer in all supported releases of MS SQL Server. Note: OE00217893 Type: Behavior Change Unicode datatypes mapped to OE CHARACTER truncated during data comparison --------------------------------- In the previous releases, only Non-Unicode data was truncated during data comparison, while an equivalent Unicode character datatype issued an error due to the size mismatch of the comparison. To resolve this issue, Unicode datatypes in MS SQL Server mapped to the OpenEdge CHARACTER datatype in database tables (defined in the schema holder), get truncated during data comparison with other Unicode character columns or expressions defined in a WHERE clause. (This is similar to the non-Unicode data types behavior.) This is done to achieve compatibility with the OpenEdge database which currently performs this same WHERE clause value truncation. Therefore, the new behavior provides consistency across all (Unicode and non-Unicode) character types. Note: OE00218653 Type: Product Notice Existing MSS logical schema requires an update to enable certain LOB operations --------------------------------- In MS SQL DataServer, partial LOB operations with non-native MS SQL Server drivers had resulted in an error. The schema image has been modified to include additional information that allows for important LOB data type distinctions in the non-native drivers. As a result, a newly created logical schema with re-pulled server definitions will no longer experience errors when non-native drivers are processing DataServer LOB operations. If you want to successfully use an existing logical schema with non-native driver connections, you must first run the attached, upd_sqlcols_buf.p, script and then re-pull your table definitions with LOB data types from the server into the schema holder database. Note: OE00218872 Type: Behavior Change Always run r-code against the schema image of the original database --------------------------------- Position-independent rcode is "independent" of the physical position of a column in the foreign data source. That is, column positions in the server table can be rearranged without the need to recompile. However, introducing a new column or deleting an existing column from an existing record structure always requires the r-code to be recompiled against the new schema layout. The r-code is dependent only on a logical identification of the column, and not the physical position of the column. The logical identification, in the OpenEdge database, takes place before migrating to a foreign data source, and the logical identification does not change once the column is defined in the OpenEdge table. When the columns are rearranged on the server, the code need not be recompiled, but the foreign schema must be pulled back into the schema image. This is to ensure that the new physical position of a column is matched in the schema to the logical identifier that is also known to the r-code. You can only run r-code or load data (.d file) while connected to a schema image that is derived from the same database that was migrated and connected to the server when the code was first compiled and/or the data was first dumped. This ensures that the same logical column identifier is preserved after migration and/or after any subsequent schema pulls. Note: When the server table is re-pulled into the same schema image (after the columns are rearranged on the server), the logical column identifier is re-matched to the physical column position so that the r-code can find again the column in a run-time application. Note: OE00223564 Type: Limitation Recompile r-code in 11.2.1/11.3.0 from OpenEdge 11.2 or previous V11 versions --------------------------------- 32-bit and 64-bit platform r-code compiled on OpenEdge 11.2 (or previous versions) must be recompiled at least once before being executed on OpenEdge 11.2.1 or later versions. Corrections were required for all r-code compiled against the DataServer for MS SQL Server due to 64-bit alignment issues associated with stored r-code that affect run-time capabilities on both 32 and 64 bit platforms. Note: OE00223755 Type: Behavior Change R-code compiled in OpenEdge 11 before and after this fix must be recompiled --------------------------------- 32-bit and 64-bit datasever r-code compiled in OpenEdge 11.2.0 is incompatible with OE 11 releases before and after it due to a change of data stored in r-code. Corrections are required for all r-code compiled against the DataServer for MS SQL Server in releases other than 11.2.0. Release 11.2.0 r-code is only compatible with its own run-time. Moving Release 11.2.0 MSS DataServer r-code to later releases (11.2.1+ or 11.3+) requires a recompile even if you recompiled once already in moving to 11.2.0. Note: OE00226541 Type: Behavior Change Field name on right side of a MATCHES operator get resolved on the client --------------------------------- In the ABL applications, the MATCHES operator compares a character expression to a pattern (Sample syntax: MATCHES ) and evaluates to TRUE if the expression satisfies the pattern criteria. The pattern can include a constant, a field name, a variable name, or an expression whose value is a character. If MATCHES operator is used in a WHERE clause and the pattern is a constant, a variable, or an expression whose value can be resolved during ABL compilation or statement preparation, then wildcards in the pattern will be replaced with native syntax before the WHERE clause is sent to the foreign data source via the DataServer interface. However, if the MATCHES pattern references a table column in the foreign data source, then any wildcards patterned in the foreign column data cannot be known and modified before issuing the database request to the server that selects the records. And, because wildcard expressions in the column data of server references cannot be resolved in advance, MATCHES patterns with column references are omitted from any WHERE clause bracket sent to the server. Instead, such MATCHES predicates must be resolved by the client, including any pattern filtering required on ABL wildcard expressions in the data content, after the server returns the result set. Client filtering of MATCHES on a wider result set bracket returned from the server can have a negative impact on performance. For better performance, avoid server column references in the MATCHES pattern when placing requests to a foreign data source via the DataServer interface. ================================================ DataServers - ORACLE ================================================ Note: OE00204194 Type: Behavior Change LEFT OUTER-JOIN query keywords default to JOIN-BY-SQLDB server join translation --------------------------------- Beginning with the OpenEdge 11.0.0 release, DataServers for Microsoft SQL Server and Oracle translate ABL LEFT OUTER-JOIN FOR EACH queries (dynamic or static) into corresponding server-side LEFT OUTER-JOIN SQL requests. In previous OpenEdge DataServer releases, the client processed the LEFT OUTER-JOIN queries. In the join-by-client method, a client requests records from parent and child server tables and matches the keys from the records of the child table with the corresponding keys in the parent table, and then continues the same matching process for all the records in the parent table. When the join-by-server method (JOIN BY SQLDB) is used, the foreign database SQL engine processes tables for ABL LEFT OUTER-JOIN query requests. The advantages of offloading the LEFT OUTER JOIN to a server: 1. Reduced network traffic, hence improved network turnaround time. 2. Reduced data transfer rates because fewer numbers of records are transferred to the client. 3. Fewer CPU requirements on the client to handle join processing and sorting. 4. Optimized record processing and join performance by leveraging the server capacity. Despite the advantages, inconsistencies related to NULL join key values may occur. For example, all the OpenEdge DataServers translate the Unknown value (?) to the NULL value when mapped to MSS. This affects join translation in an inconsistent manner between OpenEdge and SQL databases. If a join key contains the Unknown value in OpenEdge, matching join keys are included in join results. This is in contrast to the NULL value translation of Unknown in SQL databases where if the join key contains the NULL value, record matches are excluded from join results. NULL never matches a corresponding key for an inner join for SQL while the Unknown value always matches a corresponding key for of an inner join for OpenEdge. For JOIN-BY-SQLDB functionality, see the manuals OpenEdge Management: DataServer for Oracle and OpenEdge Management: DataServer for Microsoft SQL Server. Note: OE00228859 Type: Limitation Recompile r-code in 11.2.1/11.3.0 from OpenEdge 11.2 or previous versions --------------------------------- 32-bit and 64-bit platform r-code compiled on OpenEdge 11.2 (or previous versions) must be recompiled at least once before being executed on OpenEdge 11.2.1 or later versions. Corrections were required due to the byte ordering of data stored in r-code compiled against any DataServer (ODBC, MSS, or ORACLE). The byte-ordering of r-code storage and run-time retrieval affects run-time capabilities on both Little Endian (LE) and Big Endian (BE) machine types. ================================================ Documentation - ================================================ Note: OE00146970 Type: Known Issue Microsoft Security Update may affect remote access of Online Help --------------------------------- If you receive the following error when accessing the help remotely: "Action cancelled Internet Explorer was unable to link the web page you requested. The page might be temporarily unavailable", see the Microsoft Knowledge Base article titled: "Certain Web sites and HTML Help features may not work after you install security update 896358 or security update 890175" located at http://support.microsoft.com/kb/892675/. The article describes the reasons for the issue and provides workarounds. Note: OE00146971 Type: Known Issue Online Help unavailable for editor's dialog boxes --------------------------------- Online help for dialog boxes in the Procedure Editor is not available. The Help buttons on the dialog boxes do not work because the color-coding editor control only supports MicrosoftRTM WinHelp (.hlp) files and not MicrosoftRTM HTML (.chm) files. ================================================ Documentation - Electronic Documentation ================================================ Note: OE00146978 Type: Known Issue Search of PDF files for UNIX Platforms --------------------------------- On UNIX platforms, the search index is not automatically attached to the documentation PDF files. To attach the index file so that you will have search capabilities, follow these steps: 1. From the Adobe Acrobat Reader, click on the Search icon. The Adobe Acrobat Search dialog box appears. 2. In the Adobe Acrobat Search dialog box, click on the Index button and choose Add. 3. From the drop down list of files, select the oeidx.pdx file and choose OK. ================================================ Documentation - Help ================================================ Note: OE00146973 Type: Known Issue Accessing online help for CSSPIN ActiveX Control --------------------------------- If you press F1 to get help on the CSSPIN ActiveX Control, you will get an error indicating it cannot find the help file. To access the help for the CSSPIN ActiveX Control, do the following: 1. Select Start->Program->OpenEdge->Help. The OpenEdge Online Help file appears. 2. In the left pane, double-click the ActiveX Control Help folder to expand it. Then, select the CSSpin Control help topic. Note: OE00146975 Type: Known Issue Accessing online help for CSCOMBO ActiveX Control --------------------------------- If you press F1 to get help on the CSCOMBO ActiveX Control, you will get an error indicating it cannot find the help file. To access the help for the CSCOMBO ActiveX Control, do the following: 1. Select Start->Program->OpenEdge->Help. The OpenEdge Online Help file appears. 2. In the left pane, double-click the ActiveX Control Help folder to expand it. Then, select the CSCombo Control help topic. Note: OE00146976 Type: Known Issue Non-existing examples mentioned in online help for CSSPIN --------------------------------- The CSSpin Active X Control Help file mentions the following example: Example Location Project File Form/Basic File SPINDEMO.VBP SPINDEMO.FRM These example files do not exist. ================================================ Documentation - Progress Developer Studio for OpenEdge ================================================ Note: OE00211510 Type: Product Notice Infragistics assembly and namespace changes in version 2011.1 --------------------------------- With support for Infragistics Version 2011.1, several of the assemblies, DLL's, and corresponding namespaces have been changed in OpenEdge Release 11.0. As a result, you will need to change any existing code that uses the affected assemblies. To see a list of the changes: 1. Go to the following URL: http://help.infragistics.com/NetAdvantage/WinForms/2011.1/CLR2.0/html/Win_Deplo yment_Overview.html. 2. Select the link, "Known Issues and Breaking Changes". 3. Select the link, "Breaking Changes in 2011 Volume 1". Note: OE00215957 Type: Workaround Problems with context-sensitve help in Progress Developer Studio for OpenEdge --------------------------------- When launching context-sensitive help in Eclipse, Help Not Found errors sometime occur even when help is available. The error message is, "The context help for this user interface element could not be found." If you get a Help Not Found error after pressing F1, or clicking the help icon in the UI, try one of the following: 1. Click on some other element in the UI and press F1, or click the help icon again. 2. Click on "Search for . . ." link in the help pane. A list of relevant topics appears. ================================================ Graphical User Interface - ================================================ Note: OE00227488 Type: Known Issue No .R File Properties tab for 64-bit Windows products --------------------------------- The file properties sheet for an r-code (.r) file does not include the .R File Properties tab when you install the OpenEdge products (either 32- or 64-bit) on a 64-bit Windows machine. ================================================ Graphical User Interface - ABL ================================================ Note: OE00221498 Type: Behavior Change Behavior changes when cropping and stretching images --------------------------------- In OpenEdge releases earlier than 11.3, cropping images (using the FROM option of the Image phrase, or the optional parameters of the LOAD-IMAGE ( ) method) and stretching images (using the STRETCH-TO-FIT attribute of the IMAGE widget) did not always work as specified. In many cases, the cropping and stretching were ignored or were performed incorrectly. These issues are fixed in OpenEdge Release 11.3. Applications which use these features may display images differently than in earlier releases. ================================================ Graphical User Interface - ActiveX ================================================ Note: OE00212914 Type: Known Issue Crystal Reports XI causes crash in some environments --------------------------------- Adding an instance of the Crystal Reports XI ActiveX Report Viewer to a window causes a crash on certain platforms (such as Windows 7 or Windows 2008 Server) and with certain Report Viewer versions (namely V11.5 or later 11.X versions). This is a third-party issue, and occurs whether developing in Visual Studio 2010 or with OpenEdge. Note: OE00214005 Type: Known Issue VideoSoft IndexTab control does not display properly on certain platforms --------------------------------- The VideoSoft vsIndexTab OCX does not display at runtime on certain platforms (for example, Windows 7 64-bit). This is a third-party issue, and occurs whether developing in Visual Studio 2010 or with OpenEdge. ================================================ Management - ================================================ Note: OE00146518 Type: Known Issue Working with Properties --------------------------------- If an "-Xbootclasspath:", "-Xbootclasspath/a:", or "-Xbootclasspath/p:" entry that contains spaces in the argument value has been added to the JavaTools.properties or AdminServerPlugins.properties file, the entry must be manually edited to include quotes around the entire argument value (value to the right of the colon). Note: OE00146951 Type: Known Issue Random errors with mapped drives on MSW --------------------------------- Due to Microsoft Knowledge Base Article #294816, we do not support the running of a Progress application from a Network Share for Windows Terminal Services or Citrix running on Windows 2000 Server or Windows 2000 Advanced Server. Terminal Services users might see errors like "Disk or Network Error" or "C0000006: In Page I/O Error", etc. This happens due to a bug in the Windows operating system where the network redirector only creates one file control block (FCB) for all user connections so that when the first user to open the files logs off, the other users lose their connections to files. To work around this problem, place the program and associated data files on a localvolume, not network share. Note: OE00146953 Type: Known Issue Error when default language not installed --------------------------------- While adding a product after an installation has been completed, if you attempt to change the default language to a language that has not yet been installed, and the language is one listed with a non-alphabetic character (e.g. -, (, )) an error will result that will not accurately reflect the problem. The error should not prevent the installation from continuing. This problem is apparent on Windows/NT platforms only and does not occur on UNIX. The workaround is to select entries from the pull-down list boxes. Note: OE00146954 Type: Known Issue Uninstall fails with Proshell.dll in use --------------------------------- The uninstall will fail if any of the files it attempts to remove are busy. Use of the Windows Explorer has been known to cause this condition of rendering the file proshell.dll as in use, thus preventing the uninstall from succeeding, however this may not be obvious at the time of uninstall. Note: OE00146959 Type: Known Issue ubroker.properties file is renamed ubroker.properties-sav --------------------------------- When uninstalling the ubroker.properties file is renamed ubroker.properties-sav and copied to the temp directory. Note: OE00146965 Type: Known Issue Cannot use an older version of PROMSGS with a current release --------------------------------- Through the automated OpenEdge installation process, Progress Software Corporation programmatically ensures that a current OpenEdge installation has the most recent OpenEdge messages in the PROMSGS files. This approach also ensures that you always have the most up-to-date OpenEdge messages throughout a release's lifecycle. Do not perform any tasks related to the PROMSGS files outside of the standard OpenEdge installation process; for example, attempting to use the PROMSGS environment variable to point to any versions of a PROMSGS will have unpredictable and potentially undesirable results. For example, the PROMSGS files installed with the OpenEdge Release 10.1B contain the most up-to-date messages to support OpenEdge Release 10.1B. After the initial install, if you install add-on products, or OpenEdge install service packs that are released after the 10.1B Release date, Progress again programmatically provides any newer or more recently updated PROMSGS files. As each OpenEdge add-on product or service pack is installed, the installation program checks to ensure that the newest copy of the PROMSGS file is being used by all products. ================================================ Management - Management ================================================ Note: OE00233710 Type: Known Issue Some fields may be missing when you preview the Enable Multitenancy for Tables --------------------------------- When you preview the Enable Multitenancy for Tables page, some fields may be missing. This happens if the schema area you assigned for the field has a forward slash (/) in the name of the area assigned. Note: OE00238776 Type: Known Issue Adding remote AdminServer with wrong authentication throws an exception --------------------------------- If you try to add a remote AdminServer with incorrect authentication, immediately after you have added and deleted the same AdminServer, OEM throws an exception and no Remote AdminServer resources are displayed in the Resources Grid. ================================================ Migration - ================================================ Note: OE00229441 Type: Known Issue Document dataslots get converted to String dataslots on process migration --------------------------------- After you migrate projects from the Savvion 7.6.1 or 8.0 to OpenEdge 11.3, Document datalots defined in the Savvion process are converted to String dataslots in OpenEdge. Note: OE00235653 Type: Migrated ABL datatypes migrated from Savvion 8.0 are shown as Business Objects --------------------------------- After you migrate a BPM project created in Savvion BPM Studio 8.0 to OpenEdge 11.3, ABL datatypes that are defined as Business Objects in Savvion are displayed as Business Objects in the Form Editor in OpenEdge. However, these ABL datatypes will function as native ABL datatypes in OpenEdge 11.3. Note: OE00236688 Type: Limitation Outline view does not display rule wizards for migrated projects --------------------------------- Rules created in Savvion 8.0 projects are not displayed when the RuleWizards option is selected in the "Outline" view in the OpenEdge BPM Designer perspective. The RuleWizards option in the "Outline" view does not work for Savvion BPM Studio 8.0 projects that are migrated to OpenEdge 11.3. Note: OE00236773 Type: Migrated Bar and pie charts are not displayed in Summary reports for migrated projects --------------------------------- After you migrate simulation projects created in Savvion BPM Studio 7.6.X to OpenEdge 11.3, bar charts and pie charts are not displayed in Summary reports in OpenEdge. Note: OE00237253 Type: Workaround Converting to Multiple Process project does not delete the project's references --------------------------------- After you migrate a Savvion 8.0/7.6.X project to OpenEdge 11.3, converting it ito a Multiple Process project does not delete the project's old reference. You must select "Refresh" on the project context menu to delete the project's old references in OpenEdge. Note: OE00240318 Type: Workaround OpenEdgeDDLOperationHandler gets suspended after migration --------------------------------- The OpenEdgeDDLOperationHandler may get suspended after migrating Savvion 7.6.x or 8.0 projects to OpenEdge 11.3. This happens because of changes in the OpenEdgeDDLOperationHandler class files. To fix the issue, copy the OpenEdgeDDLOperationHandler application folder from \server\ebmsapps to \jboss\webapps\deploy\sbm.war\ebmsapps, and then start the EJB and Portal servers. After the servers are started, you must uninstall and reinstall OpenEdgeDDLOperationHandler. Do one of the following: - Use these commands: 'removept', 'create', and 'install' from the BPServer Admin utility - Use "Administration" tab > "Applications" > "BP Server" on the Business Process Portal ================================================ OE Mobile - ================================================ Note: OE00237111 Type: Known Issue Some browsers display a prompt for credentials when Session.logout() is called. --------------------------------- When a Mobile Web App calls the progress.data.Session logout() method and the security model in effect is HTTP Basic, some browsers display a dialog box that prompts for a user name and password. The only way to dismiss the dialog box is to cancel out of it -- even entering valid credentials does not cause it to go away. If the user does cancel out of the dialog box, the logout proceeds as expected. However, there should not be any dialog box displayed at all. Chrome and Opera are two browsers known to display this dialog box; Safari and Firefox do not. Note: OE00239471 Type: Known Issue Cannot use CORS with HTTP Forms authentication in Firefox --------------------------------- It is not possible to use Firefox to run an OpenEdge Mobile Web App that uses a cross-domain request to log into a Mobile Web application that uses the HTTP Forms authentication model. If you do, the login fails, throwing an NS_ERROR_FAILURE error object. Note: OE00239477 Type: Known Issue Cannot use CORS with HTTP Basic authentication in Firefox --------------------------------- It is not possible to use Firefox to run an OpenEdge Mobile Web App that uses a cross-domain request to log into a Mobile Web application that uses the HTTP Basic authentication model. If you do, the login fails, throwing an NS_ERROR_DOM_BAD_URI error object. Note: OE00239489 Type: Known Issue BEFORE-TABLE functionality not implemented for OpenEdge Mobile --------------------------------- For Business entities that implement OpenEdge Mobile resources, the BEFORE-TABLE functionality is not implemented. In other words, before image data is not sent between the AppServer and an Open Edge Mobile App. Note: OE00239545 Type: Known Issue Mobile Native Apps are not validating a Web site's credentials --------------------------------- The process for connecting to a secured Web site using SSL/HTTPS involves verifying the Web site's server credentials against a local copy of the issuer's Certificate Authority (CA) certificate. This CA certificate verifies the authenticity of the Web site's identity. If for any reason, the Web site's server certificate fails the authentication, a warning is displayed notifying the user that the Web site's certificate is not trusted. In Mobile Native Apps, the verification to ensure the Web site's authenticity is not occurring, with the result that the SSL/HTTPS connection is successfully established. Without this verification, a potential security problem exists where a connection can be inadvertently made to a fraudulent Web site. ================================================ Open Client - Web Services Provider ================================================ Note: OE00161041 Type: Limitation Multiple Dataset parameters and RPC Encoded Web Services with Axis java clients --------------------------------- When defining multiple INPUT DATASET parameters for an OpenEdge web service that uses RPC/Encoded SOAP messages, do not use the NAMESPACE-URI option in the DEFINE DATASET statements. The Apache Axis Java client does not properly handle namepsace declarations when it sends a SOAP request for an RPC/Encoded SOAP message. As a result, an incorrect message will be sent and the data will not be loaded into the ProDataSet. Axis may have similar issues with OUTPUT DATASET parameters. SOAP responses from OpenEdge may not be properly deserialized. If the NAMESPACE-URI option is required, then either define the OpenEdge Web service to use Document/Literal or RPC/Literal SOAP messages. Alternatively, avoid the issue by passing only one dataset in the Web service call. ================================================ OpenEdge GUI for .NET - ================================================ Note: OE00169757 Type: Known Issue MessageQueue Microsoft Control does not work with Visual Designer --------------------------------- When you drag and drop the MessageQueue control from the toolbox to the Design Canvas in the Visual Designer, an error message appears. Note: OE00173368 Type: Workaround Workaround for Elegant Ribbon control and IsolatedStorageException --------------------------------- The Foss PersistentStateManager class automatically loads and saves application state in isolated storage, which does not work with the current OpenEdge .NET bridge architecture. Setting the LoadStateAutomaticallyFromIsolatedStorageForDomain property to FALSE disables the automatic state loading at application startup. Add this line to your program that uses the Elegant Ribbon control: Elegant.Ui.PersistentStateManager:LoadStateAutomaticallyFromIsolatedStorageForD omain = FALSE. This also means that changes in the quick access toolbar will not be loaded and saved automatically. If you need the changes to be kept, manually use the Load() and Save() methods of the PersistentStateManager class. Note: OE00180730 Type: Known Issue ABL extended .NET object subscribed to .NET event may be deleted prematurely --------------------------------- An ABL extended .NET object subscribed to a .NET event may be deleted prematurely. This bug can be observed with the following conditions: - An ABL extended .NET object, for example AForm, is visualized - A .NET object, for example a button, is not on AForm, but one of AForm's methods is subscribed as the handler for this button's event. - There is no reference to the button in the implementation of AForm. If AForm is closed, and therefore Disposed, and all ABL references to it go away, it will be deleted even though the button subscription is still outstanding. In other words, the button, in essense, still has a reference to the class due to the subscription. But this does not prevent the object from being deleted, as it should. Note: OE00181806 Type: Behavior Change All dates exchanged between ABL and .NET are now the same except 12 --------------------------------- All dates going from .NET to ABL and from ABL to .NET will be exactly the same except for 12 days. These are the dates 2/29 in the leap years that are represented by the Julian Calendar (on the Progress side) but not represented by the Gregorian Calendar (on the .NET side). (Since the Gregorian Calendar was not created until 10/15/1582, the .NET DateTime implementation is not correct.) These dates are: 2/29/100 2/29/200 2/29/300 2/29/500 2/29/600 2/29/700 2/29/900 2/29/1000 2/29/1100 2/29/1300 2/29/1400 2/29/1500 Note: OE00198019 Type: Limitation .NET controls that call back to the AVM on other threads are not supported --------------------------------- A .NET object might call back to the AVM to handle an event on a thread other than the main UI thread. It might also call a .NET method on a different thread where the method was overridden in a derived ABL class. The AVM does not support either of these cases and raises a run-time error if they occur. ================================================ OpenEdge Replication - Server ================================================ Note: OE00225519 Type: Known Issue OpenEdge Replication target may need to be rebased upon upgrade or back out --------------------------------- A change to the format of OpenEdge Replication's recovery control data was introduced in OpenEdge releases 10.2B07 and 11.2.0. In certain circumstances, the target database must be recreated by backing up the source database and restoring a copy of the database to be used as the target (rebase). The following releases have the two formats: - Format A - - Format B - 10.2B06 and earlier 10.2B07 and forward 11.0.0 11.1.0 11.2.0 and forward The upgrade rules are: - upgrading from a Format A release to a Format A release is seamless - upgrading from a Format A release to a Format B release is seamless - upgrading from a Format B release to a Format B release is seamless - upgrading from a Format B release to a Format A release requires a rebase Additionally, there is one exception to the upgrade rules. Upgrading from pre-10.2B07 to 10.2B07 requires a rebase of the Replication target database. Hotfix 10.2B0715 brings 10.2B07 into compliance with the rules and eliminates the need for the rebase. Finally, if the database has been upgraded to a different format version (A-> B or B->A) backing out that upgrade will require a rebase. ================================================ Porting - ================================================ Note: OE00152834 Type: Known Issue On Windows 7 platforms, sqlexp only works with a numeric port number --------------------------------- On Windows 7 platforms, sqlexp can only connect to the database server if the port is numeric. For example, specify the port number as 4050 rather than using a service name like "mydbservice". Note: OE00172068 Type: Known Issue fmconfig fails on Red Hat Linux 5 when libX.so is missing --------------------------------- fmconfig fails on Red Hat Linux 5 when the library libX.so is missing. To resolve the missing library, download and install libXp-1.0.0-8.1.el5.i386.rpm or higher, available at the ftp site listed below. You can then run the fmconfig command. To get the library: 1. Navigate to: ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/5rolling/x86_64/SL/libXp-1 .0.0-8.1.el5.i386.rpm 2. rpm -Uv libXp-1.0.0-8.1.el5.i386.rpm Note: OE00172320 Type: Known Issue Long connection times on Windows 64bit --------------------------------- Occasionally connecting a process to an OpenEdge database on Windows 64bit takes a long time. This is an open issue Progress Software is working with Microsoft to resolve (Microsoft Support Case: SRX080707601602). Conditions that appear to cause the slow connection include: * The database buffer pool that is larger than 1.7 GB. * The C: drive on the machine is smaller than 14 GB. If you encounter slow connection times, please report the conditions to Progress Software so that more data can be provided to Microsoft to help resolve the issue. Note: OE00177172 Type: Known Issue Windows 64bit requires more memory for the Operating System --------------------------------- In Windows 64-bit, the operating system requires 2GB of free memory for acceptable OpenEdge performance. If your shared memory allocation (database buffer pool) leaves less that 2GB of free memory, then performing even simple operations, such as finding a record that is in memory, is extremely slow. ================================================ Progress Developer Studio for OpenEdge - ================================================ Note: OE00227916 Type: Limitation Errors with .Net form and AppBuilder design in same project --------------------------------- If you work with the Visual Designer and the AppBuilder in the same project you may get the following error when the project is restarted: Invalid use of stacked input-blocking statements. Session is being terminated. The error occurs because the Visual Designer and the AppBuilder have separate WAIT-FORs. and happens when the Visual Designer is closed before, but was started after the AppBuilder. This error can possibly be avoided by controlling the order Forms and Design Windows are opened and closed, but this may not resolve all issues that can be caused by two WAIT-FOR statements and the general recommendation is to not work with AppBuilder designs and Forms in the same project. Note: OE00228959 Type: Workaround Eclipse switches to the Console View when the OE Web Server writes to the log --------------------------------- Eclipse switches control from the Servers view to the Console view whenever OE Web Server writes log. This is standard Eclipse behavior where-in the Console view gets the control whenever the standard output or error streams change. Note: OE00230387 Type: Known Issue Content assist does not function properly for SharedAVM in ABL Scratchpad --------------------------------- After assigning a database connection to a SharedAVM, when you select the SharedAVM option from the AVM selection drop-down menu in the ABL Scratchpad view, and then initiate content assistance (), the ABL Scratchpad view does not display DataAware proposals, variables, and program constructs. Also, it does not provide color coding for the database fields. Note: OE00235562 Type: Known Issue LIKE keyword is not supported for files in the file system --------------------------------- When you generate business rules Vocabulary definition from the files in the local file system, database temp-tables containing the LIKE keyword are not supported. Note: OE00237487 Type: Known Issue Shortcut SHIFT-F2 (Check Syntax) does not work in UI Designer white canvas --------------------------------- The AppBuilder Scheme shortcut SHIFT-F2 (Check Syntax) does not work in UI Designer white canvas. Note: OE00238593 Type: Known Issue Adding Java facet to an OE project displays source folder twice --------------------------------- When you add Java facet to an OE project explicitly or it is implicitly added for example, as a result of JET project enablement, the source folder appears twice in the Project Explorer. This does not have any impact on the functionality. Note: OE00240266 Type: Limitation Deploying binary app on device produces "Appconfig definition missing error" --------------------------------- The binary (native) app (.ipa or .apk) created using "Export as binary app" from the Mobile Appbuilder or using "Export local" from PDSOE for Express mobile project displays the error, "Appconfig definition missing" when deployed and accessed from a device. PDSOE generates the proper appconfig.js as part of Express Mobile project creation, and this file contains all configuration information required to run the Mobile app. However, by default the appconfig.js file in Mobile App Builder is blank. To work around the error, you must copy the contents of your local /src/files/views/assets/js/appconfig.js from PDSOE to the Mobile Appbuilder javascript/appconfig.js before exporting to the binary file (.ipa or .apk). Note: OE00240286 Type: Known Issue Running a session-enabled tablet app launches in the Phone emulator --------------------------------- A mobile application created using the "Session-enabled tablet App" template, and run from PDSOE opens in the Phone emulator instead of the Table emulator. ================================================ Progress Developer Studio for OpenEdge - AppBuilder Support ================================================ Note: OE00236757 Type: Known Issue Binding a fill-in with the LIKE option does not adjust the width --------------------------------- When you change the binding of a Fill-in from the Property Sheet in the AppBuilder in the Developer Studio and configure the field to be LIKE a database table, the width of the Fill-in does not automatically adjust. In the standalone AppBuilder changing a Fill-in to be defined LIKE a database field automatically adjusts the width. ================================================ Progress Developer Studio for OpenEdge - Debugger ================================================ Note: OE00215646 Type: Behavior Change Progress Developer Studio for OpenEdge debugger behavior change --------------------------------- Starting in OpenEdge Release 11.0 and continuing in all subsequent releases, the Progress Developer Studio for OpenEdge debugger does not stop at the first executable line. Instead, the debugger stops at the line containing the first breakpoint. ================================================ Progress Developer Studio for OpenEdge - Visual Designer ================================================ Note: OE00195134 Type: Product Notice OpenEdge cannot compile/run GUI for .NET code generated using previous versions --------------------------------- When you edit GUI for .NET code generated using a previous version of OpenEdge Visual Designer, the generated code is updated to the current version of Progress Developer Studio for OpenEdge and thus might contain new language constructs that are not compatible with the previous versions of the compiler and the AVM, and wizard-generated code is incompatible with previous versions. Such incompatibilities can occur even when you do not explicitly use new features of the current version. To compile and execute GUI for .NET code, you must use an OpenEdge version that matches or is later than the Visual Designer version in which the code was generated. For example, source code opened in version 11.0 of the Visual Designer will no longer compile in 10.2B. ================================================ REST - ================================================ Note: OE00230162 Type: Limitation Clicking on REST applications with form-local authentication throws JSON error --------------------------------- When the authentication set in web.xml is set to /WEB-INF/appSecurity-form-local.xml, clicking on REST applications in OpenEdge Management throws a JSON parsing error. Note: OE00231887 Type: Limitation Multiple versions of OOABL overloaded methods cannot be exposed --------------------------------- When creating a REST or Mobile service using Progress Developer Studio for OpenEdge, you cannot expose multiple versions of overloaded OOABL methods. Note: OE00239165 Type: Known Issue Sending properly constructed JSON when passing values to an ABL procedure --------------------------------- When passing values to the parameters of an ABL procedure through a REST client, ensure that you send a properly constructed JSON else null values will be sent to the AppServer. Note: OE00239302 Type: Limitation PDSOE generates usupported mapping artifacts for REST applications --------------------------------- The REST mapping tool in Progress Developer Studio for OpenEdge allows you to map request information such as all headers or server context to simple ABL parameters even though this is not supported in 11.3. The mapping tool will be updated in the future to disable this type of operation. ================================================ Security - User Authentication ================================================ Note: OE00234601 Type: Workaround Authentication of users with blank domain names for proutil with multi-tenancy --------------------------------- Authorized users are not authenticated to run proutil commands if the commands require users to have certain privileges when the database is multi-tenant enabled and the login user's domain name is default (blank). This problem can be worked around by granting the required privileges on the fully qualified name through the Data Dictionary. For example, when granting user "audituser" audit archiver privilege, grant the privilege to both "audituser" and "audituser@" if the domain name of "audituser" is blank. ================================================ SQL - ESQL92 ================================================ Note: OE00159192 Type: Limitation ESQLC clients can specify an IP protocol version using a parameter --------------------------------- ESQLC clients will default to using the IPv4 protocol. The use of the IPv6 protocol can be selected by using the -ipv6 parameter on the connection URL. The following is an example of a connection URL where the use the of IPv6 protocol is desired: progress:T:myhost:5000:mydb:[-ipv6] The parameter is also available to use with connection URLs for the SQLDump, SQLoad, and SQLSChema utilities. ================================================ SQL - Server ================================================ Note: OE00233676 Type: Known Issue Execution of triggers or stored procedures causes _sqlsrv2 to crash --------------------------------- Prior to 11.3, while executing a trigger or a stored procedure, the _sqlsrv2 process crashed intermittently due to the Java Virtual Machine (JVM) crash on systems that use Oracle Java. In the 11.3 release, the frequency of these crashes has been reduced to a large extent because now the SQL server (_sqlsrv2) disables the JVM option UseBiasedLocking that causes the crashes. Also, in 11.3, two environment variables, PROSQL_JAVACPATH and PROSQL_JVMPATH, have been added. You can use these variables to switch between Javac (java compiler) and JVM by specifying the full path of Javac and JVM. Usage of these environment variables is optional and by default they are set to null (unused). ================================================ SQL - SQL ================================================ Note: OE00153600 Type: Known Issue SQL uses the Java compiler to compile the Java code for a CREATE --------------------------------- TRIGGER or CREATE PROCEDURE statement. If the Java compiler finds errors in this Java source code, it outputs diagnostic information describing the errors. A subset of the diagnostics is appended to the SQL-92 error message which is returned to the client. The entire set of diagnostics is stored on the server, in the SQL server's WRKDIR (working directory). If the owner of the stored procedure/trigger is OWNER, and the procedure/trigger name is XX, then all the diagnostics are in the file named OWNER.XX.LST in the SQL server's WRKDIR (working directory). The WRKDIR is identified by either the environment variable $WRKDIR, or on NT by the registry entry WRKDIR under the registry key for the Progress software installation. Note: OE00182091 Type: Behavior Change Display of null array is changed. --------------------------------- The ARRAY data type is a composite data value that consists of zero or more elements of a specified data type (known as the element type). If the result returned from an ARRAY data type is null, it used to be displayed as a string that consists of ? for each element and seperated by ;. To be consistent with all other data types, it will be changed to be displayed as null instead of a string with above format now. Same for the result returned from pro_element function. Note: OE00225837 Type: Workaround DDL to correct CRC errors when using BINARY DUMP/LOAD --------------------------------- In release 11.2, SQL introduces the following special syntax for Database Administrators who handle problems while migrating database tables from an older release database to a newer release database. In some cases, there may be a CRC mismatch error (when dumping and loading data using BINARY DUMP/LOAD). To correct this error, Database Administrators can run the following DDL command: Syntax: ALTER TABLE table_name SET PRO_FIELD_INFO PRO_SCHEMA_REPAIR For more information refer to the OpenEdge SQL Statements chapter of the OpenEdge Data Management: SQL Reference guide. ================================================ Web Services Client - ================================================ Note: OE00100789 Type: Known Issue Time zone information lost for some XML datatypes --------------------------------- The XML Schema datatypes, gYearMonth, gYear, gMonthDay, gDay, and gMonth, can optionally include time zone information. OpenEdge does not handle time zone information correctly for these datatypes. Any time zone input from the ABL is lost, as is any time zone information returned from a Web service for these datatypes. For example, "1953-10-4:00" becomes "1953-10". The one exception is that Z, indicating Universal Time (UTC), is retained (for example, 1953-10Z remains 1953-10Z). Note: OE00103414 Type: Known Issue Data types defined in imported schemas are not seen by the WSDL Analyzer --------------------------------- RN# 100B-00168 ============== When a WSDL document contains an XML Schema import element, the type and element definitions of the imported schema are not seen by the analyzer. A message indicating that a type or element definition could not be found will appear in the generated documentation. To work around the problem, copy the xsd:schema elements (and their contents) from the imported schema document and paste them as children of the wsdl:types element of the WSDL document. Also comment out the xsd:import element in the xsd:schema element. Double check namespace prefix definitions to ensure the prefixes in the copied XML are properly defined and can be referenced by other parts of the WSDL document. Note: OE00123804 Type: Known Issue Memory violation when connecting to a Web Service on AIX 5.3 --------------------------------- In order to use WebServices on AIX 5.3, the minimum Operating System requirement is AIX 5.3.04. You can find the version of AIX you are running using the oslevel -r command. ================================================ WebClient - ================================================ Note: OE00146960 Type: Known Issue The WebClient install does not accurately calculate disk space required --------------------------------- The WebClient install does not accurately calculate the amount of disk space required on the client side to do the install. Prior to the install the user should probably have around 25 meg of available disk space. Some of this is for temporary storage of installation files. Note: OE00147868 Type: Known Issue Do Not Use Notepad to Edit .htm Files --------------------------------- Do not use Notepad to edit the webclient.htm file or bootstrap.htm file for customizing your application install. When Notepad saves the file, it changes the line terminator characters and may make the file work improperly in the browser. Note: OE00147869 Type: Known Issue DLLs and EXEs That You May Have to Package with Your Application --------------------------------- Be aware that there may be Progress-supplied DLLs or EXEs that are used by your application that are not included in the end-user WebClient install. Strictly speaking, these DLLs and EXEs are not a part of ABL. For example, there are some DLLS or EXEs only used during application installation. Other DLLS may be required if the application uses procedures in the adecomm or adeshar directories that indirectly use DLLs. Progress excludes them from the install to keep WebClient as small as possible and keep install time over the Internet as fast as possible. If you need any of these files to install or run your application, include them in your application installation. Examples of these files are listed below by category. DLLs used by some procedures in adecomm/adeshar: dirsrch.dll fileinfo.dll proprint.dll EXEs that could be used by your install: * ini2reg.exe * regsvr32.exe (A Microsoft tool usually, but not always, installed on a typical PC) Note: OE00237344 Type: Product Notice 64-bit WebClient not available for OpenEdge 11.3.0 release --------------------------------- The 64-bit WebClient is not available for 64-bit Windows. It will be provided in a subsequent release. The WebClient Application Assembler, that ships with the 64-bit Developer Studio, is a 64-bit application but it can generate applications only for a 32-bit WebClient. However, you can still run a 32-bit WebClient on a 64-bit Windows machine. You can download the 32-bit WebClient install image from the Progress ESD website (http://www.progress.com/esd/). ================================================ WebSpeed - ================================================ Note: OE00194419 Type: Behavior Change 11.1 Webspeed Messenger installation behavior for Windows --------------------------------- From OpenEdge Release 11.1, Webspeed Messenger installation behavior on Windows has changed as below: 1) WebSpeed Messenger only installation: The msngrs.properties file is created in the $DLC/properties location. Prior to OpenEdge Release 11.1, it used to be the ubroker.properties file. This changed behavior on Windows is now consistent with the behavior on UNIX. Note: You can rename the msngrs.properties file to the ubroker.properties file. 2) WebSpeed Messenger only installation performed over the existing OpenEdge installation: a) The msngrs.properties file is created in $DLC/properties. b) The existing ubroker.properties file is saved as ubroker.properties-sav. This changed behavior on Windows is also consistent with the behavior on UNIX. ================================================ WebSpeed - Tools ================================================ Note: OE00096070 Type: Known Issue The compileAll option in WebTools has a limitation of URL length of 4096 chars --------------------------------- The compileAll option on AppManager in WebTools has a limitation of URL length being more than 4096 chars, depending of what web browser is being used. Try to limit the size of the compiles, number of files if you run into this problem. LIST OF ISSUES ADDRESSED IN RELEASE: ================================================ ================================================ Issue Number: OE00178775 Converting delta.df to delta.sql results in incorrect delta.sql When converting a delta.df to delta.sql with the DataAdministration tool this creates an incorrect delta.sql. Issue Number: OE00188510 The SQLGetData ODBC API returns invalid data length The last call to the SQLGetData ODBC function returns invalid data length in the StrLen_or_IndPtr output parameter when retrieving data in multiple parts, for example from a CLOB field. Sometimes, invalid truncation of CLOB data was observed. ================================================ ABL ================================================ Issue Number: OE00197989 Passing CAN-FIND( ... WHERE ...) to a class method fails Passing the CAN-FIND function as input to a method that has a logical input parameter fails, if the CAN-FIND is called with a WHERE clause. It can cause an error at compile time ("Parameter for is not type compatible with its definition. (12905)") or the method may get the wrong input value. Issue Number: OE00216654 ABL client crashes on very long WHERE clause query ABL client crashes when executing a query with extremely long selection criteria. Issue Number: OE00219085 Sliding decimal format doesn't work with backspace Using the backspace key in a decimal fill-in or browse cell with a sliding decimal format (for example, ">>,>9.99<<") may not work as expected. The cursor may move two digits to the left instead of moving a single digit. Issue Number: OE00220794 Trigger won't run after setting FORMAT attribute in a trigger Setting a fill-in's FORMAT attribute during the execution of a trigger that was fired as a result of the fill-in losing focus may cause the trigger not to work on subsequent events. For example, setting a fill-in's FORMAT attribute in the VALUE-CHANGED trigger of a browse widget will cause this issue if the VALUE-CHANGED event occurs due to the user clicking on the browse when focus was in the fill-in. Issue Number: OE00222085 CASE statement not working with LONGCHAR When using SUBSTRING of a LONGCHAR as the basis for a CASE statement, only the first WHEN clause works correctly. Anything that doesn't match the first WHEN clause will end up resolving to the OTHERWISE block. Issue Number: OE00222172 Run time error for properties of built in classes is wrong The error 14634 displayed when trying to run GetPropertyValue(), SetPropertyValue(), or DYNAMIC-PROPERTY for properties of built-in objects is wrong. The ABL does not support these methods used with built in classes, and the error message needs to reflect this. Issue Number: OE00222226 Runtime error stget out of storage The following piece of code will cause a compile time error because of the extra parenthesis on the right side. (The error is that compile time arguments cannot be passed to an internal procedure): RUN pTest IN THIS-PROCEDURE ((2 * 2) + 4)). This is the same in OE10 and OE11. However, if you happen to put this code in a "persistent run" like this: ... TRIGGERS: ON "CHOOSE" PERSISTENT RUN pTest IN THIS-PROCEDURE ((2 * 2) + 4)). ... there is no compile time error. The code will even run fine in OE10. But in OE11, the session will crash with error "stget out of storage". Issue Number: OE00222274 AppBuilder crashes when compiling after db changes When checking the syntax of a v8 smartviewer, after making on-line db schema changes within a separate session, the session goes away silently, with no errors. Issue Number: OE00222908 Long menu labels with accelarators can crash client The ABL GUI client can crash displaying a window if menu items have labels with more than 72 characters and long key sequences for accelerators (such as CTRL+SHIFT+F1). Issue Number: OE00223037 RETURN ERROR AppError from trigger invalidates error object When using a "RETURN ERROR AppError." statement from within a database schema trigger, the AppError object gets deleted when the trigger ends, even if there are references left to it elsewhere in the session (for example, because the trigger stores a reference in a temp-table maintained outside the trigger). Issue Number: OE00223210 Fwd slashes to reference xml file in READ-XML method; error 1303 Using forward slashes to reference an XML file in the READ-XML method results in the following errors: Error reading XML file ''. (13035) READ-XML encountered an error while parsing the XML Document: FATAL ERROR: file '', line '0', column '0', message 'unable to open primary document entity '''. (13064) Issue Number: OE00223376 READ-XML truncates temp-table field names READ-XML truncates dynamic temp-table field names if they are longer than 32 characters. Issue Number: OE00223445 MouseDoubleClick event on Tree node doesn't restore minimized .W Setting the WINDOW-STATE attribute of a minimized window to WINDOW-NORMAL (3) doesn't always restore the window when WINDOW-STATE is set in a trigger for an UltraTree mouse double-click event. Issue Number: OE00223775 Multiple calls to X-Document:SAVE() terminates session abnormall Invoking the X-Document:SAVE() method causes an attribute of the root element to be deleted. Invoking the X-Document:SAVE() method a second time against a document whose root element has more than two attributes, terminates the session abnormally. Issue Number: OE00223870 Windows Update (MS Sec. Bulletin MS12-060) replaces MSCOMCTL.OCX Windows Update for 08/14/2012 pushed a new version of MSCOMCTL.OCX. The update is described in Microsoft Security Bulletin MS12-060 - Critical at http://technet.microsoft.com/en-us/security/bulletin/ms12-060. Controls in this OCX used in OpenEdge GUI applications become unusable. Issue Number: OE00223969 Infinite loop in editable browse with VALUE-CHANGED trigger An editable browse that has a VALUE-CHANGED trigger that applies ENTRY to the browse causes an infinite loop upon entry of an editable cell. Issue Number: OE00224001 OE 11.1 client COPY-LOB corrupts XML When using COPY-LOB to copy an XML file from a database CLOB to a file, the resulting XML file is corrupted. A few characters are missing from the beginning. This only occurs when a remote win32 client is connected to a database server on a 64-bit platform. Issue Number: OE00224019 SYSTEM ERROR: Attempt to define too many indexes for area 6 data SYSTEM ERROR: Attempt to define too many indexes for area 6 database Issue Number: OE00224068 Error (2881) compiling a large number of procedures When a client runs a procedure that compiles a large number of procedures, the rcdaxxxx file grows and the compiling procedure eventually fails with the error: SYSTEM ERROR: Corrupted run-time segment chain. (2881) without compiling all the procedures. Issue Number: OE00224179 Unexpected "Default Beep" sound during interaction with a window An unexpected "Default Beep" sound is produced when the user clicks on the title bar of a window in an OpenEdge application. Issue Number: OE00224669 Identical LONGCHARS written with WRITE-XML/JSON not equal Two identical LONGCHARs written with WRITE-XML or WRITE-JSON can fail an equality test under the following circumstances: - using -cpstream UTF-8 - the codepage of the LONGCHARs is fixed to UTF-8 Issue Number: OE00224688 Error loading OCX's type library if version is non-integer You might get the following error in AppBuilder when trying to select a control in the AppBuilder's Choose Control dialog: An error occurred opening the type library for the control. This can occur if the type library version has a number after the decimal point e.g. "1.2". Version numbers that correspond to an integer (e.g. "1.0") do not suffer this problem. Issue Number: OE00225093 Compiler is inconsistent in behavior on FOR FIRST. Compiler is inconsistent in behavior on FOR FIRST shows error 91 after FOR FIRST BLOCK ends. Issue Number: OE00225218 Client doesnt close with QUIT in OCX event and IOEverywhere 1 The Quit statement doesn't cause the application to exit when executed from an OCX event handler. However, any subsequent keystroke will close the application. Issue Number: OE00225371 Wrong index key created if char field built with function calls. When using a UTF-8 database, the wrong index keys can be created for indexed character fields. This occurs only when the result of calling an ABL date-time function is to converted to character string and then that string is assigned to an indexed character column in a database table. Issue Number: OE00225418 JsonObject:GetLongChar() gives error (12008) with UTF-8 The JsonObject:GetLongChar() method will generate the following error if the AVM is started with -cpinternal UTF-8: Invalid character code found in data for codepage UTF-8 (12008) Issue Number: OE00225426 find-by-rowid gets error 7328 & 10041 when using named buffer Using the method find-by-rowid on a named buffer results in error 7328 & 10041 Issue Number: OE00225633 WAIT-FOR Application:Run breaks ALT keys When using a COM control that is implemented in .NET, then using the .NET event loop (e.g. WAIT-FOR System.Windows.Forms.Application:Run()), ALT key sequences on the numeric keypad might no longer generate the intended non-ASCII characters in OE widgets. One example of such a key sequence is the Euro symbol ALT-0128. Issue Number: OE00225692 2nd READ-XML into same dynamic dataset misses data Using READ-XML to construct a single dynamic prodataset, if you load 2 XML files with the same dataset name but different table names, for the second READ-XML the tables are added to the existing dataset. If the tables created by the second READ-XML() have fields that are being renamed because the XML node name matchess an ABL keyword, those fields are not populated when data is loaded from the XML into the table. Issue Number: OE00225722 65536: maximum number of sub-transactions A savepoint counter overflows after 65535 assignments. As a result not everything is being restored during rollback leading to various database corruptions. Issue Number: OE00225759 LOAD-MOUSE-POINTER doesn't work for a browse The LOAD-MOUSE-POINTER method doesn't work for a browse widget. The arrow cursor is shown instead of the cursor set by LOAD-MOUSE-POINTER. Issue Number: OE00226146 Task Manager shows incorrect windows in the Applications tab The Windows Task Manager may show one or more windows labeled "Progress" which are not part of the application being run. These windows are not meant to be visible and do not affect the execution of the application. Issue Number: OE00226272 Memory leak with DELETE OBJECT and object refs in a temp-table There is a small memory leak which occurs if an object is deleted using the DELETE OBJECT statement and there are references to the object in a temp-table. For every reference to the object in a temp-table, a small amount of memory is leaked when the object is deleted using the DELETE OBJECT statement. Issue Number: OE00226278 FIND FIRST causes a memory leak in an ABL class When calling a ABL class method that adds new object instances to an array, for some reason if a FIND FIRST is run within the method against an empty temp table, then there is a memory leak. Issue Number: OE00226415 FIND on global BUFFER in internal procedure can crash client A program can use a global BUFFER for a table, and FIND on this BUFFER in an internal procedure. There is a corner case where a long running program, performing such a FIND on the BUFFER in a loop, can crash the client. The following code demonstrates such a situation, run against the sports2000 database: RUN findcust. PROCEDURE findcust: DEF VA i AS INT64 NO-UNDO. DO i = 1 TO 0x100000000: FIND FIRST customer WHERE customer.custnum = 1 NO-LOCK NO-ERROR. END. END. MESSAGE "Completed". This is more likely to occur in programs with few global BUFFERs and few FIND statements. Issue Number: OE00227300 SYSTEM-DIALOG GET-FILE changes session current directory When a SYSTEM-DIALOG GET-FILE statement without the RETURN-TO-START-DIR option is followed by a SYSTEM-DIALOG GET-FILE statement with the RETURN-TO-START-DIR option, the second SYSTEM-DIALOG changes the session current directory to the location of the file selected in the first SYSTEM-DIALOG. Issue Number: OE00227502 RAW-TRANSFER method and statement are different with BLOB/CLOB The RAW-TRANSFER method and statement behave differently with regard to BLOB/CLOB fields. Issue Number: OE00227527 Clicking on a toggle-box may cause session to crash Clicking on a toggle-box while the PROCESS EVENTS statement is executing may cause the session to crash. Issue Number: OE00227530 COPY-LOB of CLOB to file not observing NO-CONVERT When executing the COPY-LOB statement from a CLOB to file using NO-CONVERT, the AVM will incorrectly convert the CLOB data to the -cpstream codepage. COPY-LOB for a LONGCHAR to file with NO-CONVERT will correctly leave the data in the LONGCHAR's codepage in the file. Issue Number: OE00227645 RefreshBrowse removes record from smartDataBrowse RefreshBrowse removes record from smartDataBrowse with SDO built against a temp table. Issue Number: OE00228986 Alert box or system dialog box cancels dialog box modality If an alert box (MESSAGE ... VIEW-AS ALERT-BOX) or system dialog box (SYSTEM-DIALOG) is displayed while a dialog box is active, upon dismissing the alert box or system dialog the dialog box will no longer be modal with respect to the window which displayed it. Issue Number: OE00229105 Spurious pixels displayed after install of 11.1.0.013 After installing the 11.1.0.013 hotfix and then starting the GUI client, there is a pixelated area displayed in the top left hand side of the desktop. Issue Number: OE00229507 Crash with DYNAMIC-NEW() or STATIC property with exhausted -mmax Calling DYNAMIC-NEW to instantiation a class that has never been loaded in the client during the current session can cause the client to crash. Accessing a STATIC property on a class that has never been loaded during the current session can also cause the client to crash. This happen only when the -mmax value is almost exhausted, and r-code segments have to be swapped out to load the new class. Issue Number: OE00230746 Client hang with STOP in OCX event and IOEverywhere 1 The client can hang when executing a STOP statement from a codejock choose event. After the STOP the code appears to return out of the ocx correctly until it gets to the last END PROCEDURE in the Execute procedure. At this point it appears to hang and does not restart the startup procedure. Issue Number: OE00230773 COPY-LOB from MEMPTR with large STARTING at crashes UTF-8 client The COPY-LOB command can crash the AVM under the following circumstances: - the COPY-LOB is copying from a MEMPTR to a LONGCHAR - there is a STARTING AT option - the -cpinternal is UTF-8, or any other double- or multi-byte codepage (does not occur with single-byte codepages). Issue Number: OE00230818 COPY-LOB from memptr to longchar with OVERLAY causes crash COPY-LOB from memptr to longchar with OVERLAY causes crash when there is a codepage conversion where the number of bytes differ after the conversion. Issue Number: OE00231180 Error 11963 when importing XML with space delimiters in keys When attempting to use bprowsdldoc to generate ABL code from the XML Schema of a wsdl, or when attempting to read the XML Schema directly in the ABL, the following error occurs when there are space separated lists of keys in the parentkey and/or childkey attributes of the XML Schema msdata:Relationship element. ADD-RELATION join pairs list entry not valid--list must have unqualified field names with no embedded blanks, in parent-fld,child-fld order, e.g. 'cust-num,cust-num'. (11963) Issue Number: OE00231477 DYNAMIC-INVOKE of static method may crash client process The client process may crash when invoking a static method dynamically where the hierarchy has some classes with interfaces and no static members and there are no active objects on that class. Issue Number: OE00231522 prefetched icb usecount is 0. When accessing multi-tenancy table SYSTEM ERROR: bfPrefNext: prefetched icb usecount is 0. When executing FOR EACH NO-LOCK remotely on a multy-tenancy table. Issue Number: OE00231962 Incorrect result when pasting in a date field Pasting a date into a date field when the cursor is sitting at the end of the field causes the digit before the cursor to be overwritten. Issue Number: OE00231969 LIST-ITEM-PAIRS returns wrong values for blank labels Incorrect values may be returned by the SCREEN-VALUE and INPUT-VALUE attributes when the LIST-ITEM-PAIRS attribute is used to populate the list of a DROP-DOWN-LIST combo-box. If the list includes an item with a blank label (an empty string) the INPUT-VALUE and SCREEN-VALUE attributes will return 0 (zero) and ? (unknown), respectively, instead of returning the value that corresponds to the item's label. Issue Number: OE00232017 Memory violation with logical field and non standard format When using a memory mapped procedure library that performs an assignment statement with a logical field with a format containing a blank value, e.g. "ERROR/ ", this can result in a session crash, memory violation error 49. Issue Number: OE00232070 COPY-LOB CLOB may cause crash ABL clients may crash when trying to execute COPY-LOB where the source is a CLOB. The issue only happens when running rcode. Issue Number: OE00232156 Displaying multi-byte characters with @ integer truncates value When using -cpinternal UTF-8 and displaying UTF-8 multi-byte (multi-column) characters with DISPLAY @ using INTEGER field formats, it's possible for the character value to be truncated. The number of columns displayed is determined by the number of bytes in the INTEGER format, not the number of columns in the character data being displayed. Issue Number: OE00232181 COPY-LOB longchar to CLOB might corrupt longchar When using COPY-LOB to copy a LONGCHAR to a CLOB object when there is a code page conversion from a multi-byte codepage to a single-byte codepage, the longchar data may get corrupted. Issue Number: OE00232188 WRITE-JSON causes 5635 error when writing Array elements When using WRITE-JSON to write out a temp-table with array fields, the following error is returned for a large amount of array data unless the omit-initial-values argument is specified and the value of the array field elements are equal to the initial value for the data type. SYSTEM ERROR: -s exceeded. Raising STOP condition and attempting to write stack trace to file 'procore'. Consider increasing -s startup parameter (5635) Issue Number: OE00232332 Error 7 and crash when compiling / checking syntax Checking syntax / compiling the following code in Procedure Editor in OpenEdge 11.x results in error 7 and a session crash: DEFINE VARIABLE h AS HANDLE NO-UNDO. run test in h:INSTANTIATING-PROCEDURE (dataset ds). SYSTEM ERROR: Illegal choice found in semantic stage. (7) Issue Number: OE00232681 FILE-INFO:FILE-CREATE-DATE and FILE-INFO:FILE-MOD-DATE 2GB limit FILE-INFO:FILE-CREATE-DATE and FILE-INFO:FILE-MOD-DATE are only displayed for files < 2GB within prowin32.exe. Issue Number: OE00232758 Illegal instruction error (47) using IMPORT-NODE on AIX64 The following error occurs on 64-bit AIX when executing the X-DOCUMENT:IMPORT-NODE() method to copy a root node from one X-DOCUMENT to another: SYSTEM ERROR: Illegal instruction. (47) Issue Number: OE00233166 compile xref-xml crashes when internal proc has > 130 params Compiling a procedure with xref-xml where the procedure has an internal procedure with more than 130 parameters crashes the session. Issue Number: OE00233171 STARTING AT option is ignored when doing a COPY-LOB() from a fil STARTING AT option is ignored when doing a COPY-LOB() from a file to a LONGCHAR Issue Number: OE00233202 Enhancement -clientConnectTimeout for non SSL connections A customer has requested that there is a timeout for the CONNECT method so that it can fail instead of hang in the event that there is a network issue. Issue Number: OE00233324 COPY-LOB to CLOB with UTF-8 fails on Linux 64-bits Using COPY-LOB to copy a file into a CLOB and using the STARTING AT option, on 64-Bit Linux with UTF-8 causes the following errors to be returned. Source file starting at 4 does not contain characters (14509) Failed to create/update blob from file . (11275) COPY-LOB failed to copy file to large object. (11300) Issue Number: OE00233498 Object type DYNAMIC-PROPERTY GPFs if assigned non-object type. DYNAMIC-PROPERTY either doesn't throw a Progress error or core dumps when trying to assign to an object property dynamically with a non-object value such as an integer, decimal type, or a string with only numbers in it. Progress should reliably throw an error that can be caught and handle or suppressed with NO-ERROR in this case. Issue Number: OE00233514 SET_CALLBACK not being triggered correctly call back not being triggered in some cases Issue Number: OE00233630 CHR function handles values above documented maximum The CHR function was documented as only accepting values up to 65534. However, the CHR function can accept larger values if -cpinternal is set to UTF-8. Issue Number: OE00233675 Crash w/COPY-LOB NO-CONVERT from file to CLOB in Temp-Table The COPY-LOB statement with the NO-CONVERT option may crash the client when copy from a file directly into a CLOB field in a temp-table. Issue Number: OE00233916 ABL Override .NET method System.Object parameter runtime error If an ABL method overrides a .NET method which includes a parameter defined as a System.Object, attempting to call it will generate a run time error if the value passed to the parameter is not explicitly cast to be a System.Object. This is due to the fact that we do not implicitly box parameters passed to ABL methods. Issue Number: OE00234628 RCODE-INFO limitation size issue RCODE-INFO limitation size issue crashes Progress/OpenEdge client Issue Number: OE00234741 -utf8chardisp 3 displays subsequent rows incorrectly In 11.2.1, a new startup parameter -utf8chardisp 3 was introduced to address an issue with DISPLAY of a multi-byte CHAR value @ an INT or DEC field in a frame, when using -cpinternal UTF-8. This introduced a regression for subsequent DISPLAYs of the frame when displaying the original INT or DEC field in the frame. The values would be pushed to the right, and any other fields on the frame to the right of the field would not appear. Issue Number: OE00234923 Very long WHERE criteria in a query crashes remote client Query with very long WHERE criteria crashes the remote database client. Issue Number: OE00235359 Exception from CATCH block not caught while in trigger If within a trigger block, there are nested blocks and an exception is thrown from within the CATCH block of the innermost-block (for example, a re-throw), a CATCH on the outer block fails to catch that exception. This only happens within trigger blocks; within the main block of a procedure or within an internal procedure the outer block will catch the exception. Issue Number: OE00236632 IMPORT-PRINCIPAL with encrypted/garbage data crashes client IMPORT-PRINCIPAL with encrypted/garbage data crashes client Issue Number: OE00236683 Quoted method name used in event Subscribe method causes crash If the event method name is quoted in the Subscribe method, the session crashes with the following stack in the protrace. (The crash has been seen on 64-bit OSes.) smHandleNakedIProcSubscribe smProcessEventOpArg smProcessTypedEvent smwdatr smegen smrhsc smueop Issue Number: OE00236767 Temp-table BY-REFERENCE and buffer parameters The ABL client may not find records in a temp-table that was passed BY-REFERENCE if the temp-table buffer is passed to a procedure/method as a parameter. Issue Number: OE00237348 SYSTEM-DIALOG GET-FILE sometimes displays old-style dialog box The SYSTEM-DIALOG GET-FILE statement sometimes displays the old-style Windows Open dialog box instead of the newer Windows Explorer-style dialog box. This behavior occurs unpredictably. Issue Number: OE00237403 _dbdescription.p has NO-ERROR missing The 11.2 version of "C:\Progress\DeveloperStudio3.7\eclipse\plugins\com.openedge.pdt.project_1 1.2.0.00\runtime\_dbdescriotion.p" has a NO-ERROR option missing on line 35. Issue Number: OE00237405 Crash after using FIELDS in FIND trigger After doing a FIND with a FIELDS list, followed by another FIND of the same record but with a different FIELDS list in the FIND trigger (into a different buffer), the client will crash when it then trys to do an update of that record. Issue Number: OE00237731 Changing FORMAT in a LEAVE trigger can cause error (633) During the LEAVE trigger of a fill-in, if you change the fill-in's FORMAT, you might get the following error message: ** Character at position must be (633) This regression started in OE 11.2.0. Issue Number: OE00237826 2 FINDs on different indexes in a multi-tenant database fail Incorrect search occurs when running 2 FIND statements in a multi-tenant database, where the first FIND uses one index and the second FIND NEXT uses a different index which was repositioned by the first FIND. Issue Number: OE00237898 Application crashes when accessing an ActiveX Automation object When the application is trying to access a method from an ActiveX automation object and passes the wrong parameter type for one of the parameters, OpenEdge crashes generating a protrace. Issue Number: OE00238090 Error 995 with dynamic query When using a dynamic query with a primary inactive index, this results in error 995: Index CustOrder is inactive and cannot be referenced. (995) The problem only happens if the inactive index is made primary. The -noinactiveidx parameter has no effect on this behaviour. Issue Number: OE00238534 Dyn query with long query string crash in client/server mode Client executing a dynamic query with a long query-string crashes when attempting to get (GET-FIRST / GET-LAST / GET-NEXT) a record in OpenEdge 11.x. ================================================ ABL DLL ================================================ Issue Number: OE00134561 Client crash invoking shared library > 33 parameters on AIX An ABL client can crash when calling a shared library routine that takes more than 33 parameters on 64-bit AIX platforms. The client session displays the following error when it crashes: SYSTEM ERROR: Illegal instruction. (47) ================================================ ABL Internationalization ================================================ Issue Number: OE00124868 Unable to convert to codepage IBM278 in OpenEdge 10.x Conversions to codepage IBM278 fails with error 6063 in OpenEdge 10: Code page conversion table for to IBM278 was not found in convmap.cp. (6063) Issue Number: OE00223812 COLUMN-LABEL with multi-byte chars have excessive width in UTF-8 When using -cpinternal UTF-8, if the COLUMN-LABEL of a field contains multi-byte characters, the width allowed for the field in the frame in the GUI client can be calculated much wider than necessary. This depends on the number of multi-byte characters and where they are in the COLUMN-LABEL string. Issue Number: OE00232273 Error (6063) using -cpinternal CP950-HKSCS and promsgs.tch A client session started with -cpinternal CP950-HKSCS (e.g. using DLC/prolang/tch/cp950-hk.pf) and using the Traditional Chinese PROMSGS file (promsgs.tch) will display the following message: Code page conversion table for BIG-5 to CP950-HKSCS was not found in bconvmap.cp. (6063) Messages from may not be displayed properly. (24) ================================================ ABL Language Issues ================================================ Issue Number: OE00230755 COPY-LOB w OVERLAY truncates chars when source is a CLOB fie COPY-LOB with OVERLAY option truncates the last characters of the overlayed string if the source is a TEMP-TABLE or a database table CLOB field and the target is a LONGCHAR variable. Issue Number: OE00231118 COMPILE statement with MIN-SIZE=TRUE generated larger size R-COD The COMPILE statement of the OpenEdge 11.1 running on the 64-Bit IBM AIX platform ONLY, incorrectly generates a larger size R-CODE when its MIN-SIZE option is set to TRUE. Issue Number: OE00236329 Memory violation using PAGED, KEEP-MESSAGES and stream-handle The client process may crash if you try to write to a stream that has been opened with the OUTPUT TO statement with the KEEP-MESSAGES option in a internal function or method in a different procedure/class where the stream was defined (by using stream-handle). ================================================ ABL XML ================================================ Issue Number: OE00233436 READ-XMLSCHEMA crashes 11.2 client with memory violation error When reading specific XSD files, the READ-XMLSCHEMA( ) method crashes the OpenEdge 11.2 client session and generates protrace files indicating a memory violation errors. ================================================ Adapter for SonicMQ ================================================ Issue Number: OE00222711 Still running error handler raises stop condition Still running error handler raises stop condition long after the connection to the SonicMQ broker is dropped ================================================ ADE Tools and Runtime ================================================ Issue Number: OE00129771 Dev Studio hangs when opening a read-only file in AppBuilder Developer Studio hangs after getting error (98) with errno=13 when opening a read-only file in AppBuilder. Issue Number: OE00223958 SDO viewObject procedure override does not execute Code placed in an SDO (Smart Data Object) viewObject procedure override does not execute when the application Window containing the SDO is executed. Issue Number: OE00230954 _user.d to MT database through _admin.p fails on _tenantId With a MT database using _oeusertable domain authentication, a _user.d (dumped from another MT enabled database) fails in the GUI Database Adminstration with _TenantId is a system field and its value cannot be updated. (16011) Issue Number: OE00233855 Issues dragging MS OCX objects onto app builder smart window Issues dragging MS OCX objects onto app builder smart window Issue Number: OE00233900 Encryption message when dumping schema definition in -RO mode When dumping .df from a database using -RO mode, it dumps data fine but gives encryption error even though the TDE is not enabled. Error text: The dump file will not contain any encryption definitions for the objects. Error: Database must not be READ-ONLY (15001) The EncryptionPolicy object may only be used with a writable Database Issue Number: OE00236179 Security Administrators does not work for multiple databases In the Data Admin tool, if you have multiple databases connected and set the Security Administrators for one of the databases, you will not be able to set it for the other databases in the same session. Issue Number: OE00237260 firstBufferName function trips over decimals > 2,147,483,647 The firstBufferName function in query.p trips over decimals larger than 2,147,483,647. (example: 3000000000.123) If such a value is encountered before a valid buffer name it will return the value before the decimal point as the buffer name, instead of returning the correct buffer name. This is because the firstBufferName relies on the INT() function to determine if a token with a period in it is a numerical value instead of a buffer.field pair. So it runs into the 32-bit limitations, and if the limit is exceeded it thinks it encoutered a valid buffer name. ================================================ ADE Tools and Runtime Tools ================================================ Issue Number: OE00232771 Getting error Query/RESULTS not supported on database type MSS Getting error Query/RESULTS not supported on database type MSS ================================================ ADE Tools and Runtime Translation Manager ================================================ Issue Number: OE00110396 Error 12272 when creating a zip file in Translation Manager Error 12272 is raised when trying to create a zip file of a kit in the TranMan - "A variable or array element passed as an INPUT or INPUT-OUTPUT parameter to a DLL cannot contain the Unknown value. (12272)" ================================================ AppServer ================================================ Issue Number: OE00229749 Error 16506 incorrectly appears after wrong username/password When an AppServer client passes incorrect credentials that are used to connect to a database from within the Connect procedure and the connect statement is in a transaction, this causes the AppServer agent to disallow all future connections. Whenever another user attempts to connect to the AppServer from that point forward, the Connect procedure dies without ever being loaded. Issue Number: OE00237339 Crashes when returning multiple datasets with many tables Calling a procedure that passes multiple datasets to or from an AppServer causes the process to crash (the process sending the datasets), if the combined number of temp-tables in the datasets is larger than 200. ================================================ AppServer Broker ================================================ Issue Number: OE00237968 Appserver does not start with a long PROPATH OE 11 Appserver won't start if length of the PROPATH is greater than 1033 characters. ================================================ Auditing ================================================ Issue Number: OE00231388 4GL client memory violation Client is running their application and getting SYSTEM ERROR: rmmak failed, retcode=1 when modifying records for tables / fields that are Audited with Progress Auditing. ================================================ Database ================================================ Issue Number: OE00181281 .df fails to load against a database with many extents on Linux Linux platforms fail to process keys and socket events if a database with too many extents is connected in self-service/single-user mode when a .df is loaded or the debugger is initialized. Issue Number: OE00197703 aiarcinterval cannot be queried Neither the -aiarcinterval nor the After-image Management Archival Method can be queried. Issue Number: OE00204407 Proshut -by on repl target takes 5 minutes with Repl license Running a proshut -by against a replication target database may take 5 minutes if using a Replication license instead of a Replication plus license. Issue Number: OE00205473 Probkup message from failed backup across network hangs process Probkup message, from sending the backed up file across a network, where the network has registered failed writes hangs the probkup process. It sees it as an end of file and response with Please enter the next device/filename or type "quit" to exit. Need to have the backup end whenever there is a failed network connection rather then waiting on some response. Issue Number: OE00212487 _UserIndexStat data is wrong _UserIndexStat records do not reinitialize back to zero for a new user connection. Issue Number: OE00223055 idxbuild -TF >0 with mergethreads mis-reports memory usage It has been determined that the message in the .lg file: Max merge pool entries estimated at: 91841 w/memory usage: 1812987904 has an overflow bug in it. Issue Number: OE00223147 Database activity drops suddenly, clients stops responding Database activity drops suddenly, clients stop responding, while waiting for latches to be released. Issue Number: OE00223299 Proshut process does not return after immediate shutdown. Proshut process does not return to calling process or script after and immediate shutdown has been issued and the process was killed. Issue Number: OE00223542 _mprshut process assoc. with keyeventrdr goes runaway with CPU _mprshut process assoc. with keyeventrdr goes runaway with CPU Issue Number: OE00223950 Intermittently key event reader process doesn't shutdown Intermittently the _mprshut key event reader process does not shutdown after an emergency shutdown. Issue Number: OE00224728 db conv to OE 11 with multitenancy causes required credentials After a database conversion from a database without any credentials defined under 10.2B to version 11.0 or 11.1, and after Multi-tenancy is enabled for that converted database credentials are then requested when connecting to that database. If a user is then created in that database (by logging in to the database by pressing ESC and therefore bypassing entering a user and password) then on future restarts of the database no access to that database is possible anymore to the database. (all database data becomes unavailable to anyone) Issue Number: OE00227173 Temp sort file grow every time that a query is executed When running a search that has any wildcard in a word-index, the search will create an srt file on the db server. If the query returns a large of number of rows (greater than 100,000) then space in the sort file is not entirely re-used and the .srt can grow very large. Issue Number: OE00227977 Differences in OE11 schema after running conv1011 During conversion the utility (dbutil conv1011) adds the _File._category column and sets its value to blank space instead of a string of one blank character. Issue Number: OE00229505 prefetchfactor can cause a hang with no-lock queries Using prefetchfactor has been shown to cause a hang with no-lock queries. The hang occurs when the network buffer is filled to exactly the percentage specified in prefetchfactor after rounding. This caused and issue with a "<=" vs "<" check in the networking code. Issue Number: OE00230964 conv1011 change the BI cluster size from 16Mb to 16kb conv1011 change the BI cluster size from 16384 kb to 16 kb. Issue Number: OE00231103 Index becomes active after interrupting idxactivate session When idxactivate is aborted with Ctr-C (hangup signal), the idxactivate takes it as a successful end of processing and results in marking an index active. Issue Number: OE00231815 "Begin JTA Lock Application at Block" message running script While running a backup script, an informational message "Begin JTA Lock Application at Block" goes to the screen and requires acknowledgement to continue processing. Issue Number: OE00232267 -DbCheck raises 'bad compression size' error When -DbCheck encounters an index with keys with 32 and 64 bit values, in the deletion process the SYSTEM ERROR is raised: (4423) SYSTEM ERROR: Index 2102, block 2078517024, element no. 1: bad compression size. (2816) prev size = 1, cs = 8, ks = 54, is = 15, key count = 1. (14037) Index 2102 block validation error data: nment is 150, nlength is 1980, level is 0, current key is 1, offset is 12, func is cxDoDelete (14031) Invalid Index Block Detected (14036) SYSTEM ERROR: Invalid Index Block FATAL Issue Number: OE00233280 Restore of database is failing with memory violation in bkxtn Restoring a full backup of a database into an existing copy of the database, consistently causes a memory violation in the bkxtn function(rkt/src/dbmgr/bk/bksubs.c). Issue Number: OE00234366 Some AppServer processes are not shutting down. Some AppServer processes are in a deadlock situation and do not appear to be shutting down. After trimming AppServer processes, they continue to be running. These processes are not visible in OpenEdge Explorer but continue to exist on an Operating System level and are consuming resources. Issue Number: OE00237395 SUBSTITUTE function in 11.x client crashes 10.2B _MPROSRV OE11 client executing a query containing the SUBSTITUTE function against an OE10.2B database causes _MPROSRV to crash. ================================================ Database Database Utilities ================================================ Issue Number: OE00230263 dbtool record fixup fails with 8579 error dbtool option 6 - record fixup fails with ERROR - failed to start a transaction. (8579) Issue Number: OE00234569 Index rebuild takes an other 7h after completed to end Index rebuild which completed after 2h takes another 7h to end on Windows 2008 R2. Issue Number: OE00234703 error (49) with idxbuild all A memory violation error (49) is received when performing idxbuild all on database. Performing the idxbuild on individual tables is successful. ================================================ DataServers ================================================ Issue Number: OE00182162 Client crashes table maximum no. of columns with max column widt Client crashes when the table contains maximum no. of columns with max column width Issue Number: OE00219377 protomss should have option to disable description warnings Protomss should have option to disable description warnings since MSSQL does not use description fields this will generate large number of irrelevant warnings making it difficult to spot true problems. Issue Number: OE00219750 MSSDS displays wrong err msg when row size exceeds buffer limit Microsoft SQL Server DataServer displays confusing error message when row size exceeds buffer limit. The procedure editor also resets itself but still connected to MS SQL Server which causes to lose the ABL code. Issue Number: OE00222491 For each query > "" <> TRUE fails on SQL table A joint condition with a string evaluation in the ABL query results in a corrupted SQL query Issue Number: OE00224297 Client crash checking syntax against MSS DataServer Client crashes when checking syntax a query in the format similar to the following against DataServer for MS SQL Server: FOR EACH a USE-INDEX x, EACH b USE-INDEX y OF a: Issue Number: OE00225208 Table labels removed after Update / Add Table Definitions Table label is set to '?' after performing Update / Add Table definitions against an existing table. Issue Number: OE00225738 No run time err for muti-field primary idx when "Try primary for No run time error for muti-component primary index when "Try primary for ROWID" is selected during protoMSS. Instead it displays wrong record. Issue Number: OE00225776 Rerun same ABL query with FIELDS() -> different SQL query If the exact same ABL query is being run multiple times (= from the same internal procedure, and with the same where clause) and that query has a FIELDS() list, on the second run the Oracle dataserver with generate a new SQL query with a different list of fields in the SELECT when it should re-use query created during the first one. In addition, the second SQL statement does not include the fields specified in the ABL FIELDS() list, so the ABL code will not be able to run as expected. Issue Number: OE00226396 Table parameters does not get created in sh holder with protomss Table named "parameters" does not get created in schema holder with protomss. Issue Number: OE00226418 Open Query with outer-join might cause an SQL error An Open Query with OUTER-JOIN causes one of the following SQL errors when the two tables in the query contain multi-component primary or unique indices: 37000: [Microsoft][SQL Server Native Client 10.0][SQL Server]The correlation name 'T1' is specified multiple times in a FROM clause. 37000:[Micorsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) could not be prepared. Issue Number: OE00227426 ODS creates unreleased lock scenario with NO WAIT SQL to Oracle Oracle DataServer creates unreleased lock scenario with NOWAIT SQL to Oracle which is causing Oracle error ORA-00054. Error text: ORA-00054: resource busy and acquire with NOWAIT specified Issue Number: OE00228894 MSSDS manual does not address RAW data type support MS SQL Server DataServer guide does not address anything about RAW data type. It does not mention whether we support it or not. On the other hand, it maps with Character data type in the schema holder. This creates confusion when RAW data type does not work. Issue Number: OE00229315 DataServer crash assigning primary key with Linux 64-bit DataServer session crash assigning primary key when r-code has been compiled on UNIX (HP-UX, IBM AIX, Solaris) and executed on Linux 64-bit and vice versa. Issue Number: OE00229770 'column ambiguously defined' error for outer-join query If the join index key is defined on multiple field components, open query returns 'column ambiguously defined' error with outer-join, for oracle dataserver. Issue Number: OE00230825 Delta .DF sets FOREIGN-POS 0 causing Load Aborted error Attempting to load delta.df into MSS DataServer schema holder fails with an empty error message box, followed by "Load Aborted". Delta.df contains statements that attempt to update /set FOREIGN-POS to zero. Issue Number: OE00230843 MSSDS needs Batch Mode Delta SQL utility MS SQL Server DataServer needs a Batch Mode Delta SQL utility to perform delta from command line or program running in batch mode for deployment scenario. Issue Number: OE00230844 OpenEdge to Schema Image delta.df for OE DataServer Customer needs to be able to generate delta.df comparing DataServer schema holder with OpenEdge database to find differences so the differences can be applied to schema holder and MS SQL Server to run already compiled code against OpenEdge database. Issue Number: OE00232449 Different cursor usage in OE11 vs. OE10 shown in SQL Profiler The MS SQL Server Profiler utility shows different results in 11.1 compared to the same query executed via the same ODBC driver against the same database in 10.2B. Cursor profile had changed due to block cursor integration in 11.0 but has been restored to its original 10.2B cursor profile with proper inclusion of block cursors that does not alter the rest of the cursor profile. Issue Number: OE00233705 SQL statement omits table refs using OUTER-JOIN with Oracle Dsrv Executing ABL query that references 4+ tables, each using OUTER-JOIN syntax, against DataServer for Oracle fails to execute with error ORA-00904 because generated SQL query omits some table references. Issue Number: OE00233797 SQL Statement returns the wrong result set using OUTER-JOIN Executing ABL query that includes multiple OUTER-JOIN statements and INDEX-REPOSITION, can cause partial or wrong results to be returned. Issue Number: OE00233920 Dyn join query with no-join-by-sqldb resulting into join by serv Running a dynamic join query with -nojoinbysqldb startup parameter or query-tuning (no-join-by-sqldb) is not translated to join by client and is taking large amount of time in query execution. Issue Number: OE00234731 Begins operator does not return values in MSSQL dataserver. The query does not return any values though the conditions for begins operator looks satisfied. Please advice. Query does not return any values, for each tab1 where tab1.reference begins tab1.payment_id: Query returns values if used a trim function, for each tab1 where tab1.reference begins trim(tab1.payment_id): Both the fields are of same datatype Varchar. Reference varchar (42) payment_id varchar(30) Values in mssql database: reference payment_id 000116345500003 0001163455 000116223600002 0001162236 Issue is reproduced. Issue Number: OE00235231 Incomplete data returned with '-Dsrv qt_debug,SQL switch' set The '-Dsrv qt_debug,SQL' may affect the results returned by a query, by failing to report some records. session. Issue Number: OE00235616 Client crash with query after applying 11.1.0.023 PROWIN32 crashes when checking syntax / executing specific queries after applying hot-fix 11.1.0.023. Issue Number: OE00235892 ODS calls 2 new oracle sys tables which are not in the 11.2 doc Oracle DataServer queries two new Oracle system tables (sys.cclol$ and sys.cdef$) which are not listed along with other system tables listed in table 30 of chapter 5. Issue Number: OE00235922 varchar(max) col for SP from SQL Server for shows as x(1) in DD Variable or column defined as varchar(max) or nvarchar(max) in MS SQL Server Stored Procedure pull to schema holder with display format x(1) with Nvarchar data type in the Data Dictionary. The display format should be x(320) with NlongVarchar data type. This is only apparent with SNAC 10 driver. Using legacy SQL Server driver maps the fields correctly in the OE Data Dictionary Issue Number: OE00237195 Unable to create a record in ABL with DataServer for MS-SQL If the table contains more than 128 columns of Large Object Type (VARCHAR (MAX), VARBINARY (MAX), TEXT, NTEXT etc.) and are mapped to OpenEdge CHARACTER in the schema holder, the client is unable to create a record in ABL with DataServer for MS-SQL Issue Number: OE00237198 prowin32.exe crashes when trying to read data from DataServer If the table contains more than 128 columns of Large Object Type (VARCHAR (MAX), VARBINARY (MAX), TEXT, NTEXT etc.) and are mapped to OpenEdge CHARACTER in the schema holder, prowin32.exe crashes when trying to read data from DataServer for MS-SQL Server ================================================ DataServers MS-SQL ================================================ Issue Number: OE00211239 Client crashes executing query referencing sql view in ms sql Client crashes when executing a query against a ms sql server database that references a view. The MS SQL Server db is created via protoMSS using computed columns Issue Number: OE00223564 OpenEdge 11.0 SQL DataServer 32-bit r-code crashes 64-bit client When code that is to be executed by the DataServer engine is compiled with a 32-bit version (resp. 64-bit) of OpenEdge 11.0 (or 11.1) it crashes (producing a protrace) when run on a 64-bit (resp. 32-bit) version of OpenEdge 11.0 (or 11.1). Issue Number: OE00226541 MATCHES returns false when variable is left side of the match MATCHES returns false when variable is left side of the match running against MS SQl Server DataServer ================================================ DataServers ORACLE ================================================ Issue Number: OE00228859 R-code with SEND-SQL-STATEMENT crashes when moved to diff. UNIX In 11.1, r-code that features "RUN STORED-PROC send-sql-statement" crashes the client when moved between UNIX systems. ================================================ Diagnostics ================================================ Issue Number: OE00205511 debugger:initiate & prodebugconfig may fail on Windows 7 Executing debugger:initiate() method on Windows 7, when port 9999 is in use, generates the errors: An error occurred when trying to establish communications for using the Debugger; Error code is: 10022. (11628) Unable to startup PROGRESS Debugger. (4106) Also, executing the prodebugconfig command on Windows 7, when port 9999 is in use, miscalculates the port and suggests the use of the busy port 9999 to connect to the prowin32 process. ================================================ Documentation ================================================ Issue Number: OE00223220 Type 1 area limits should reference reserved space table Type 1 area limits table should reference reserved recovery space table Issue Number: OE00223879 Missing ampersand in ABL reference for &ELSE preprocessor In OpenEdge Development: ABL Reference, on the syntax reference page for &IF, &THEN, &ELSEIF, &ELSE, and &ENDIF preprocessor directives, the ampersand is missing from &ELSE. Issue Number: OE00232056 Documentation Typo 'dsrutil db-name -C connectagent database ..' There is a typo in the documentation for 'dsrutil db-name -C connectagent database {name|ALL}'. Issue Number: OE00233460 PRGRS_WARNING_SUPPRESSIONS is not documented in Oracle Dsrv doc PRGRS_WARNING_SUPPRESSIONS is not documented in the DataServer for Oracle manual. Issue Number: OE00237112 The commitCustomers() method in Business entity class is faulty In the documentation (Coding AppServer services for OpenEdge Mobile OpenEdge section of Development: Mobile Applications) defines the following sample method for CRUD operations on the Customer table: METHOD PRIVATE VOID commitCustomers(INPUT pcFieldMapping AS CHARACTER,INPUT piRowState AS INTEGER ): BUFFER eCustomer:ATTACH-DATA-SOURCE (DATA-SOURCE srcCustomer:HANDLE,pcFieldMapping). FOR EACH eCustomer. BUFFER eCustomer:MARK-ROW-STATE (piRowState). IF piRowState = ROW-DELETED THEN DELETE eCustomer. END. /* rest of the code */ END. The FOR EACH block for deleting a customer record is confusing. Clarification is required. ================================================ Graphical User Interface ================================================ Issue Number: OE00200270 Cannot open file with OpenEdge client from Windows Explorer When right-clicking on an ABL source file in a Windows Explorer window and choosing to open it with the OpenEdge Graphical Client, the client fails with error "Cannot find or open file .db, errno = 2. (43)". Issue Number: OE00221108 Error 382 with SmartPanel pupdsav if query returns 0 rows Using a SmartPanel to navigate/populate a SmartDataBrowse returns error 382 after performing the following sequence of actions: Add a record -> Reset values -> Cancel action -> Add another record. This only occurs if the SDO query returns zero rows. Issue Number: OE00224270 Selection-list and combo-box don't show Unicode items correctly The selection-list and combo-box widgets may not display items containing Unicode characters correctly. Issue Number: OE00227038 REFRESH() in ROW-LEAVE trigger loses characters in UTF-8 session In a Unicode session (started with -cpinternal utf-8), calling the REFRESH() method of a browse widget from within a ROW-LEAVE trigger on the same browse widget a character field will truncated the data if it contains extended characters (ASCII value higher than 127). The number of characters remaining will be ( - ), with a maximum of half the string being lost. Issue Number: OE00231790 SYSTEM-DIALOG GET-DIR return value gets corrupted In some cases, the return value from "SYSTEM-DIALOG GET-DIR" gets corrupted. Rather than returning the full directory name, it returns the first 8 characters + 3 garbage characters (the garbage characters are the same within a session, but vary between sessions). ================================================ Installation ================================================ Issue Number: OE00182600 Installation on Windows creates corrupted registry keys Several keys under HKEY_CURRENT_USER\Software\PSC\PROGRESS and HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS are corrupted after installation on Windows. For example, a key that should be "11.2" appears as "11.28859-1(C0)". Issue Number: OE00226967 Password encryption utility bin/genpassword missing Password encryption utility bin/genpassword is missing in database license installation ================================================ Management ================================================ Issue Number: OE00198155 dbconfig error MaxServers (PRPMsg010) DBCONFIG reports error PRPMsg010 when maxservers GT 512 in the related conmgr.properties file. This is in error, the limit on max servers is the limit on available system resources. Issue Number: OE00217196 Background processes fail to start due to code page mismatch When using OpenEdge Explorer for database configuration and there's a difference in international settings for code page, collation table, cpstream, etc between the database (conmgr.properties) and the contents of %DLC%\startup.pf, the background processes (aiw, biw, apw, wdog) fail to start. Issue Number: OE00232222 Container list appears empty for database restore job template Can't select a container name in OpenEdge Management Database Restore job template Issue Number: OE00232764 OEMgt EmailAction Failed (9612) after installing SP 10.2B07 OEMgt EmailAction Failed (9612) after installing SP 10.2B07 Issue Number: OE00234676 large schema db under OEM causes huge memory usage and CPU spike When OEM is monitoring a database with a very large schema, the AdminServer may consume more than 1 GB of RAM and experience out of memory exceptions accompanied by CPU spikes. Issue Number: OE00235585 Bookmarks added for Appbuilder file are being removed All bookmarks added for Appbuilder file are being removed, when we save the Appbuilder File in Design Editor. Issue Number: OE00235631 Problem re-allocating tenant space after deallocation. Problem re-allocating tenant space after deallocation from Management interface. Issue Number: OE00236245 During shutdown of the adminserver it is possible to get an NPE During shutdown of the adminServer, it is possible to get a NullPointerException in the log file if polling of system resources occurs during the shutdown. Issue Number: OE00236495 Startup of OpenEdge Management may fail due to Jetty exception OpenEdge Management may fail to start due to an InvocationTargetException while starting the Jetty web server. Issue Number: OE00237772 Insert query for reports contains many concatenation operators The Insert queries run against _sqlsrv2.exe when running reports against Fathom Trend database contains lots of concatenation operators. ================================================ Management Management ================================================ Issue Number: OE00233710 From OpenEdge Explorer we cannot assign tables to tenants When enabling Multi-Tenancy for tables, it is not possible to assign custom areas on a per-tenant basis. ================================================ OE Managed Adapter ================================================ Issue Number: OE00231486 OutOfMemoryError: permGen space in ejbserver OutOfMemoryError: permGen space in ejbserver if large number of BPM Processes use OE Adapters. ================================================ OE Mobile ================================================ Issue Number: OE00233569 Mobile Service creation fails inside Developer Studio The generation of a Mobile Service fails inside Developer Studio with the following error: "Service creation failed with error: null" This happens only when the service is based on a Business Entity which refers TEMP-TABLE which has a field defined with the keyword LIKE. Issue Number: OE00234727 Accept-Language truncated when passed to REST service If a REST service definition maps HTTP header Accept-Language to a method input parameter, under certain circumstances the value is truncated when passed to the method. Issue Number: OE00235806 Bad JSON catalog generated when schema file is referring to .p When using the Define Service Interface wizard to create a Mobile resource for a procedure, by default it selects the .p as the schema file. You can then select the required schema (e.g. ProDataSetA). When default or selected schema file has schema definition (temp-table or dataset) with incremental names then the user selected schema definition is not being considered in annotation (Schema attribute value). The issue is observed only when the Temp-Table has incremental (appending) names to that of the existing Temp-Table. Issue Number: OE00236809 Decimal parameters not passed to rest adapter from mobile app When using an invoke method to pass back a DECIMAL parameter to the restbroker a zero value is received. When using decimal fields in a temp-table this works fine and other data-types (character, integer, etc...) work fine. ================================================ Open Client ================================================ Issue Number: OE00212444 DataSet Generation Differs for .NET 2.0 The strongly-typed classes generated for a static dataset differs with .NET 2.0 versus .NET 1.1. This causes problems during proxy generation. Issue Number: OE00220200 .NET OpenClient tracing logs cannot be read by other processes When a .NET OpenClient application has tracing turned on, the generated log files cannot be read by any other processes while the OpenClient process is running. The OpenClient process needs to close the log or terminate before other processes can read the logs. Issue Number: OE00223924 Error 12324 occurs when passing .NET DSet to DSet-Handle Retrieving a dataset (not via handle) from the AppServer, where the dataset contains a temp-table with a non-unique index, will fail with error 12324 when you pass the retrieved dataset back to the AppServer and the input parameter is a dataset-handle. ERROR condition: Remote mismatched fields or mismatched BEFORE-TABLE attribute for temp-table parameter or dataset member parameter. (12324) (7211) Issue Number: OE00224024 .NET Open Client Cannot Connect Using IP Address In OpenEdge 11.1, the .NET Open Client product cannot connect to an AppServer using an IP address. Issue Number: OE00225555 .NET Open Client - AppServer in SENDING after _CancelAllRequest When calling _CancellAllRequests from a .NET Open Client connecting to the AppServer via AIA, the AppServer agent remains in SENDING status. Issue Number: OE00226627 WSACancelBlockingCall Exception in .NET Open Client If the .NET Open Client sends a message out on the UDP socket but gets no response and times out, the retry mechanism fails to catch this and .NET ends up throwing a WSACancelBlockingCall exception. Issue Number: OE00236004 11.2 Proxy Generator removes hyphens from dataset table names When a temp-table of a dataset has a hyphenated name, ProxyGen removes the hyphen when used as the value of the TableName property. ================================================ Open Client .NET ================================================ Issue Number: OE00233608 .NET OpenClient is incompatible with European numeric format European numeric format causes problems when passing decimal values to a .NET OpenClient ================================================ OpenEdge Architect ================================================ Issue Number: OE00228405 DevStudio build w/multiple source not working as expected In the project properties, under the Progress OpenEdge --> Build --> Tab Source , If multiple directories are defined only the first one seems to be taken into account and setting as source container of new class wizard. ================================================ OpenEdge GUI for .NET ================================================ Issue Number: OE00200958 PAUSE NO-MESSAGE requires visible window Using PAUSE NO-MESSAGE requires a visible ABL Window to be present or it shows the default window even if there are visible forms on the screen. 1) The only reason PAUSE needs a visible window is so that the user has some way of cancelling the PAUSE, however when NO-MESSAGE is used there should be no need for this. 2) An ABL Form should suffice in such a case where a PAUSE is fired and needs to be tied to something visible which would allow the user to cancel the pause. Use the -pausefix startup parameter to enable the following behavior: When executing 'PAUSE n', with or without the NO-MESSAGE option, the AVM should pause for n seconds even if the window governing the pause is not visible or does not have a status area. If the governing window isn't visible it should not be made visible to execute the pause. Issue Number: OE00224318 Error assigning interface instance to obj defined as interface Error 13448 (classes are incompatible) is raised when an object instance that implements a .NET interface is assigned to a variable defined as that interface type. This only happens when the object instance was created with a private constructor. Issue Number: OE00224850 Focus lost in embedded ABL window when using Alt-Tab or Ctrl-Tab When using ALT-TAB or CTRL-TAB to switch back and forth between a GUI for .NET application that uses ABL Windows embedded in .NET forms and other Windows applications focus is never returned to the embedded ABL Window. Issue Number: OE00225070 Focus lost after dismissing MESSAGE VIEW-AS ALERT-BOX If an alert box is displayed when focus is in an enabled browse cell in a window which is embedded in a .NET form, focus will appear to be lost when the alert box is dismissed. Issue Number: OE00225229 NullReferenceException in .NET Bridge when using ACTIVE-FORM A NullReferenceException may occur when an application references the ACTIVE-FORM system handle. Issue Number: OE00225853 Unable to access Panel after dragging out of TabGroup In a form containing 2 Panels, grouped as a TabGroup with UltraDockManager, a Panel that is dragged out of the group cannot be accessed/moved if ShowCaption = False. Issue Number: OE00228262 AVM crash calling GetClass on object implementing .NET interface An OOABL class can implement a .NET interface. If there is a call to the GetClass() method on an object o this type, or the Progress.Lang.Class:GetClass() method is used on the class, the AVM will crash. Issue Number: OE00228411 Memory leak using .NET classes When using .NET classes that override the GetHashCode() method, it is possible that the AVM will maintain a reference to a .NET object, thus causing a memory leak. This can happen when changing a property of .NET object causes a different return value from GetHashCode(). An example of this is the classes implementing the Infragistics.Documents.Excel.IWorksheetCellFormat interface. Issue Number: OE00228519 Infragistics Pear Theme Causes Problems With UltraCheckEditor If the Infragistics "Pear" UI theme is used, any instance of an UltraCheckEditor control (check box) will become checked if the UltraCheckEditor's enabled property is set to false when the Pear theme is loaded. Issue Number: OE00228803 Checking DialogResult throws invalid handle (3135) error When checking the DialogResult following a WAIT-FOR ShowDialog() call, an invalid handle error is returned if the following conditions are true: - The WAIT-FOR used by the application is a 'WAIT-FOR System.Windows.Forms.Application:Run()' - The ABL Window that is calling the .NET Dialog has an ON "ENTRY" trigger defined in it The error that is returned is: "Invalid handle. Not initialized or points to a deleted object. (3135)" Issue Number: OE00229047 Dev. Studio "untranslatable attribute" not used with CastUtil Using the option "Add untranslatable attribute to all Visual Designer generated strings" in Developer Studio for OpenEdge does not add the untranslatable attribute (e.g. :U) to all auto-generated strings. Settings in the InitializeComponent method that require calls to Progress.Util.CastUtil will not have the untranslatable attribute set. Issue Number: OE00231315 System menu on wrong monitor with UltraFormManager Using a dual-monitor configuration on Windows 7 (assuming monitor #1 is on left and monitor #2 is on right), if a form using UltraFormManager is moved onto monitor #2 and maxmized, then the default icon in the top-left hand corner of the form (to display menu with "Restore / Move / Size / etc.") is clicked then this menu appears on monitor #1. Issue is reproducible outside of Progress so appear to be related to Infragistcs UltraFormManager. Issue Number: OE00232589 Compiler crashes on "CAST (Application:OpenForms[0]..." prowin32 crashes when compiling a line containing: CAST (Application:OpenForms[0], Progress.Windows.Form) Issue Number: OE00234057 Closing an ABL Window with a .NET child form causes crash If a .NET form is parented to an ABL window by setting
:ProWinHandle:PARENT, closing the parent window without closing the .NET form first crashes the session with an Access Violation exception. Issue Number: OE00235763 Error 12882 calling method in .Net inherited class In some situations calling a method in an inherited .Net class can result in the error message 12882. For example: Could not access element 'mFinished' of class 'codegen' using object of type 'codegen' - caller compilation is out of sync with class compilation. (12882) ================================================ OpenEdge GUI for .NET Data type ================================================ Issue Number: OE00232352 Error (65) passing .NET property to a method expecting LONGCHAR Passing a .NET object property (type System.String) whose value is larger than 32K to an ABL method expecting a LONGCHAR generates the following error: SYSTEM ERROR: copdtm - maxdlen, data item too large, try to increase -s. (65) ================================================ OpenEdge Replication ================================================ Issue Number: OE00154383 Tablemove doesn't work in Replication. Tablemove doesn't move the records into the target database. Issue Number: OE00228024 RPAGENT.EXE RPSERVER.EXE startup fails when spaces in directory Replication Server and Agent fail to start when the installation directory contains spaces eg: C:\PROGRAM FILES\OPENEDGE\DLC\BIN. Problem introduced in 10.2B07 and 11.1.0, fixed in 10.2B08 and 11.2.0. Issue Number: OE00231317 jta - rprepl target -C monitor - not updating 'last transaction' dsrutil (rprepl) monitor of the target database has a field near the bottom labelled "Last Transaction Applied to Target", it is not being updated when a JTA transaction runs. It does get updated when ABL or non-JTA SQL transactions run. ================================================ OpenEdge Replication Replication ================================================ Issue Number: OE00226985 increase limit of -pica queue to 1000000 The -pica queue limit has been increased to 1000000. ================================================ OpenEdge Replication Server ================================================ Issue Number: OE00225519 Installing OE10.2B07 Service Pack breaks Replication The replication server fails during startup when reading recovery file: (-----) Failed to read recovery file, errno = 0 (11691) The RCB for this database cannot be opened. Error -5 ================================================ OpenEdge Replication Utilities ================================================ Issue Number: OE00199297 Autostart after transition can only start a primary broker Replication is unable to autostart a secondary broker after transition. ================================================ Porting ================================================ Issue Number: OE00220820 proprint.dll is missing from 64-bit OpenEdge for Windows proprint.dll is missing from 64-bit OpenEdge for Windows. This DLL is necessary for printing with adecomm.pl/_osprint.p. ================================================ Progress Developer Studio for OpenEdge ================================================ Issue Number: OE00196574 StaticFileDestination creates recurring directory tree When using the Static File Destination option for a Project Build property, if the folder is part of the same workspace then each time the project is refreshed a new recurring folder is created. Issue Number: OE00222151 PDSOE doesn't create include files during compilation Progress Developer Studio for OpenEdge doesn't detect that files use WSMETA NAME="wsoptions" CONTENT="include" in Speed Script and the corresponding include file is not generated when html is compiled from OpenEdge Editor. Issue Number: OE00222582 Buffer in method parameter crashes the debugger Defining a buffer as a method parameter can crash the Progress Developer Studio for OpenEdge debugger. Issue Number: OE00226094 AppBuilder perspective fails to render window borders In the PDS:OE AppBuilder perspective, if the AppBuilder is run in embedded mode the window borders for the Object Pallette and the AppBuilder main window are not rendered. The pro*tools window is rendered as expected. Note that the area for the window borders is there, and is functioning as expected even though it's not drawn (clicking and dragging where the title would be will move the window, clicking where the X button would be closes it.) Issue Number: OE00230279 View Design option is in disabled state for an ABL Form/dialog/M When opening a form in the editor, pressing Shift-F9 doesn't open design view unless it has already been opened in the designer via a menu, then you can use Shift-F9 and F9 to toggle between the interfaces. To reproduce: - Open a form in the editor - Hit Shift-F9 Nothing happens... Issue Number: OE00231924 DB-REQUIRED AppBuilder generated code is read-only The Eclipse code editor incorrectly marks an entire procedure block as read-only if the procedure is flagged as Db-required in the AppBuilder. The body of this type of procedure should be editable as this is where developers need to implement their own (database-bound) logic. Issue Number: OE00232507 cannot always add OCX control to ABL window using PDS Using Appbuilder in PDS, one cannot add an OCX control to a window on the first try. This works outside of PDS. It usually works after a couple of tries, or a focus switch. Behavior is inconsistent. Sometimes it takes 2 or more tries and then it works. Issue Number: OE00232522 OEA error 3234 on _idecompile.p if project name contains umlaut OEA error 3234 on _idecompile.p if project name or file name contains any Unicode characters. Issue Number: OE00232558 Run procedure with oeideservice.i on startup breaks UI Designer The integrated AppBuilder in Developer Studio doesn't work if a procedure that references {adecomm/oeideservice.i} is executed as part of startup, for example from _idestartup.p. Issue Number: OE00232578 No Move-To-Top in Outline View of AppBuilder/UI Designer It is not possible to move a widget that are hidden under other widgets from the outline Outline View. Move-To-Top and Move-To-Bottom items in the Layout menu are not enabled when a widget is selected in the Outline View of the UI Designer (AppBuilder) perspective and there are no Move-to-top and Move-to-bottom actions on the Ouline View. Issue Number: OE00232579 Dev. Studio integrated AppBuilder "SaveAll" undo all changes. Developer Studio integrated AppBuilder. Using File->SaveAll undo all changes in the source code when the graphic view is open. Issue Number: OE00232588 AppBuilder integration fails if project name contains space The AppBuilder integration fails if the PDS:OE project has a space in it's name. New AppBuilder UI designs can't be created - the wizard fails to load the list of templates, and since selecting a template is required creating the new file can't be completed. Opening an existing .w file in the AppBuilder gets the design pane stuck on the "Loading AppBuilder" message. Issue Number: OE00232642 AVM sometimes crashes when the UI Designer is closed AVM sometimes crashes when the UI Designer is closed. We are closing the Appbuilder designer file from the designer canvas and OpenEdge AVM crashes and a graphical client error dialog is shown on UI. We need to restart the AVM for the things to work again. Issue Number: OE00232893 Exception changing int. AppBuilder Grid unit if non-US locale java.lang.NumberFormatException when changing the integrated AppBuilder Grid units if the underlying OS is running with NON-US locale (Decimal separator is non dot "." but comma ","). Issue Number: OE00232935 Cannot add trigger to .W file that defines variables LIKE Cannot add trigger code to .W file that has a variable defined LIKE a database table. Selecting "Add Trigger" doesn't display the options to generate the trigger code. Issue Number: OE00233101 AppBuilder UI Designer does not respect read-only When a read-only .w is opened, the designer view is still enabled thus allowing one to move widgets around. When one then uses Shift-F9 to view the code, the following errors is generated : Unable to open file: c:/RTBWorkspace11/.metadata/.plugins/com.openedge.pdt.project/DV1/p49677ln k.tmp. Errno=13. (98) Issue Number: OE00233205 New widgets are not listed in Add Trigger Wixzard The widgets list in the Add Trigger Wizard does not show recently added widgets, until the w file is switched back to design view once after adding the widget. Issue Number: OE00233210 Refresh of file doesn't refresh AppBuilder Outline View If a .w is modified outside of the Developer Studio, refreshing the file within the Developer Studio does not update the Outline View for the AppBuilder Designer - new widgets that are added don't show, widgets that have been removed are still listed. At the same time, the Outline View for the Text Editor do get updated. Issue Number: OE00233213 Can't move widgets to top in AppBuilder Design in PDS In the classic AppBuilder, if widgets overlap each other in a way that one fully covers another, it's possible to get to the bottom widget via the "List Objects" button; this pops up a dialog where the widget can be selected and there is a "Move to Top" button to bring it to the foreground so it can be moved around etc. In the PDS Integrated AppBuilder the Outline View replaces the "List objects" dialog, but it does NOT offer a way to bring objects to the foreground. This makes them unreachable for repositioning/resizing. Issue Number: OE00233307 Outline View adds wrong widget when copied in Dialog Outline View shows wrong widget when copied in a Dialog. If you copy and paste a button in the Outline View a new widget dialog-box(parent) gets added instead of the button. Issue Number: OE00233345 Can't add triggers for OCX events in integrated AppBuilder It's not possible to generate event procedures for OCX events in the AppBuilder when integrated in Progress Developer Studio. This is possible in the classic AppBuilder. Via the Section Editor, you can go to the Triggers section, select the CtrlFrame for the ActiveX/OCX. Issue Number: OE00234141 Save IDE Events are not triggered when using the ABL UI Designer The IDE Events, before-save and after-save are not triggered when using the ABL UI Designer. Issue Number: OE00234399 It is not possible to add widgets to a window in a shared AVM When using a Shared AVM in the Progress Developer Studio, you are not able to add ABL GUI Widgets to an ABL GUI Window. Issue Number: OE00235261 The ABL Scratchpad uses different code page settings The ABL Scratchpad seems to convert any entered text to UTF-8 when it is entered. It should use the same code page settings as the ABL Editor, and work the same way. Issue Number: OE00235371 "Dynamic Launcher Dialog" is misisng in OE 11.2 "Dynamic Launcher Dialog" is misisng in OE 11.2 ================================================ Progress Developer Studio for OpenEdge AppBuilder Support ================================================ Issue Number: OE00191811 Save-as in AppBuilder in Dev. Studio uses wrong path for files The AppBuilder generates several files when saving a SmartDataObject or a SmartBusinessObject. These are generated in the same directory as the SmartDataObject and referenced by relative paths in the generated code. This does not work correctly when you run the Appbuilder from within Progress Developer Studio for OpenEdge. This introduces several problems: - When you do a save-as several code fragments still point to the old code. - When you do a save the relative paths are not corrected. Issue Number: OE00234036 Can't create AB file in PDSOE project with non-default directory If you are using a non-default directory (i.e. not under the workspace directory) in the PDSOE and try to create an AppBuilder file you will get an error that the file is read-only or the path specified is invalid. The directory in the error indicates it is trying to save the file under the workspace directory not the directory designated by the project. Issue Number: OE00234332 Cannot save SmartObject opened via edit master When you open a SmartObject item via the Edit Master option from another SmartObject, you can't save the file as you get an error saying the file is either Read-only or path is invalid. Issue Number: OE00238144 The Properties Window is missing in AppBuilder in Dev. Studio The Properties Windows cannot be invoked from anywhere in the Progress Developer Studio integrated AppBuilder and is thus never visible. Issue Number: OE00239588 Error opening .w file with the same fieldname in multiple tables The integrated AppBuilder is throwing an unexpected error, ttwidget already exists (132), when opening .W files in the UI Designer if there are widgets referring to fields in different tables that have the same name (and these fields are in the same frame). ================================================ Progress Developer Studio for OpenEdge Editing ================================================ Issue Number: OE00228354 Syntax Check in Architect Ignores -sw Startup Parameter If the -sw startup parameter is specified in order to suppress the dead code warning message (number 15090), doing a syntax check in the Architect editor will display the 15090 warning message. ================================================ Progress Developer Studio for OpenEdge Project ================================================ Issue Number: OE00231747 Mobile service fails to associate with REST manager instance The Mobile service that you create on the Create a Mobile service page of the New OpenEdge Project wizard fails to associate with a REST manager instance despite selecting the REST manager instance checkbox. ================================================ Progress Explorer ================================================ Issue Number: OE00227468 AdminServer taking long time to start and query (terminates) AdminServer taking long time to start and query ultimately terminates with 9908 error. ================================================ Report Builder ================================================ Issue Number: OE00229704 PRORE32 returns error 16395 in 11.1 using DataServer schema Report Builder Runtime Engine (PRORE32.EXE) shipped with OpenEdge 11.1 returns error 16395 when attempting to display a report that was created against a DataServer schema and the -U -P parameters are supplied in the RB-DB-CONNECTION override parameter. ** -P and -U startup parameters require an authentication enabled domain (16395) Issue Number: OE00237404 Report Engine crashes when overriding databases Report Engine (the Report Builder runtime report generator) may crash when overriding database connection parameters. The crash is reported in prore32.exe. ================================================ REST ================================================ Issue Number: OE00233339 Appserver memory leak via REST Adapter The AppServer agent has a memory leak due to LONGCHAR memory allocations that do not get de-allocated when passing ProDataSet and Temp-Table parameters to/from an Application Server and the REST Adapter. Issue Number: OE00234056 Add millisecond logging to the REST Adapter log from Java OC The Rest Adapter logging using the Java OpenClient is only accurate to the second and cannot be configured. The database engine and application servers currently report millisecond timings as do other non Java OpenClient components of the REST Adapter. This is a request for the Java OpenClient built-in logging subsystem 1. Created by OE to: Report Millisecond Timings 2. Be Configurable Issue Number: OE00238929 httpclient authorizationinfo object has memory leak httpclient authorizationinfo object has memory leak ================================================ SQL ================================================ Issue Number: OE00216767 SQL engine prepares query containing JOIN and UNION incorrectly For SQL queries containing a JOIN and a UNION, the SQL engine may choose an incorrect index when preparing the query. This may cause incorrect results to be returned from the query. Issue Number: OE00216909 JDBC not working with service name JDBC driver is not working with service name in connection URL in Windows 7 and Windows 2008. Issue Number: OE00222266 JDBC connection abort error when running sql with case stmt JDBC "connection abort: recv failed" error when querying database using select with parametrized case statement in it. The sqlsrv2 process creates protace file. Issue Number: OE00223152 SQL command is hanging after to migrate from 10.1A to 10.2B SQL command is hanging after to migrate from 10.1A to 10.2B. This can occur with a query involving the MINUS set operator where the MINUS occurs in a derived table in the query and there is more than one table on either side of the MINUS operator. This could also occur with the INTERSECT set operator. Issue Number: OE00223251 Catalog name not found in OpenEdge 10.2B Catalog name not found error thrown in OpenEdge 10.2B when create table as select contains derived table. Issue Number: OE00223727 _sqlsrv2 process runs for ever when using multiple IN ( values ) While running a query which involved 17 tables join, correct join order is not selected due to which query runs very slow. This problem is independent of values in IN list. Issue Number: OE00224063 Strange characteres on column names using ODBC When connected via ODBC driver and use column name alias that contains special characters, these characters are not been displayed correctly. This happens only on the label (title) of the column, not for the data returned. Issue Number: OE00225045 SQLSCHEMA can fail if table name is a reserved word. SQLSCHEMA can fail if table name is a reserved word and resulting .dfsql is incomplete. Issue Number: OE00225145 Failures in sql temp database storage management In prior releases, it is possible for the sql temp database storage management to fail with an internal error, where the error has the text: "Unhandled exception with JDBC driver in function dsmObjectCreate called from sts_srtt_t::create_tndx on .SRTT_Temp_1". This failure was not accompanied by other useful error cause information. As of this release, this failure will often be accompanied by more detailed error description information. This error description information will be written to the database .lg file for the primary database. The primary database is the database to which the application first connected. Issue Number: OE00225292 SQLSCHEMA output does not preserve CRC Tables created using SQLSCHEMA output does not preserve CRC, which causes binary load to fail. Issue Number: OE00225723 SQL query slowdown after update index statistics Prior to 11.2 release, a query that normally runs in 3 or 4 seconds without updating statistics, it takes about 20 seconds after update them involving some tables and joins. Following is the update statistics command. UPDATE TABLE STATISTICS AND INDEX STATISTICS AND ALL COLUMN STATISTICS FOR pub.tableName; Issue Number: OE00226093 Getting ASSERT FAILURE errors that result in dead _sqlsrv2 Getting ASSERT FAILURE errors that result in dead _sqlsrv2 process. Issue Number: OE00227054 _sqlsrv2 memory keep going up and does not realese _sqlsrv2 memory (total virtual memory size) keeps going up using BPM and OpenEdge database. This excess memory use can occur when a sql customer database contains LOB data, or uses JBOSS with connection pooling and a heavy sql workload, or uses other connection pooling system and a heavy sql workload. Issue Number: OE00228093 Internal error when updating a view from another view When trying to update a record in a table via its view using another view in a data selection, the query fails with internal error in psr_tree.cxx Issue Number: OE00228218 SQL92 - Updating field in SQL Trig assigns array flds to NULL Updating a field in a table using a SQL Trigger causes all array fields in the table to be set to NULL. Issue Number: OE00228664 SET ROWCOUNT session parameter New statement SET ROWCOUNT created. Issue Number: OE00228821 internal error in SQL ENGINE at 2850 in /vobs_sql/sql/src/rds/ss SQL code triggerring internal error in SQL ENGINE at 2850 in /vobs_sql/sql/src/rds/ssm.cxx. Issue Number: OE00229326 Undefined symbols in libesql92.so Several symbols in libesql92.so are undefined. This prevents libesql92.so from being linked using runtime linking on AIX when those symbols are referenced in an ESQL/C program. Issue Number: OE00230770 Used Heap manager solution to control _sqlsrv2 memory usage Used Heap manager solution to control _sqlsrv2 memory (total virtual memroy size) usage Issue Number: OE00231096 Error in SQL ENGINE at 1508 in /vobs/sql/src/sts/sts_sortaggr.cx This internal error may occur if client application call sql FETCH for a statement after an error occurs with last FETCH call (without closing the statement). For example, if FETCH call to sql for a statement returned error, then rather than closing the statement , if client application calls the FETCH again, sql engine may return this internal error. Issue Number: OE00232564 select crashes _sqlsr select with predicate on ROWID, ANDed with some other predicate on an index key, in where clause may crash _sqlsrv2 ================================================ SQL Server ================================================ Issue Number: OE00223136 Query with large WHERE IN clause crashes _SQLSRV2 Prior to 11.2 release, running SQL query with large number of constant values in WHERE IN clause crashes SQL database server (sqlsrv2). Issue Number: OE00233676 Intermittent dead _sqlsrv2 processes. Prior to 11.3, while executing a trigger or a stored procedure, the _sqlsrv2 process crashed intermittently due to the Java Virtual Machine (JVM) crash on systems that use Oracle Java. Sometimes when the problem occurs the server process dies holding a buffer that results in an abnormal shutdown. In 11.3 release, this crash frequency is reduced to a large extent because now the SQL server (_sqlsrv2) disables JVM option -UseBiasedLocking, which was causing frequent crashes. ================================================ SQL SQL ================================================ Issue Number: OE00209582 Connection refused and timeout errors Connection refused and timeout errors with multiple SQL connects. This problem occurs when a secondary broker is used for OE sql connections, and the -Ma startup parameter value for the secondary broker is different from the -Ma paramater value for the primary broker. Issue Number: OE00223707 All users can access the schema metadata Access to the database schema metadata is accessible to all users and cannot be revoked, in OpenEdge releases prior to 10.2B07. This occurs when access is done using ODBC or JDBC catalog API's. Issue Number: OE00225837 Cannot binary dump and load non-PUB tables due to CRC errors Cannot binary dump and load non-PUB tables from older version(pre 10) database to new database due to CRC errors caused by schema difference in the original database. Issue Number: OE00228663 Different error status for primary key and unique key constrain Three different error statuses for primary key, unique key constraint failures, and unique index failure - current implementation of these constraints are just implemented as unique indexes. ================================================ TTY ================================================ Issue Number: OE00179486 Attribute applied to wrong row when CHUI browse is backscrolled This problem can be seen in the character client when the DCOLOR attribute is applied to fields in certain rows in a dynamic browse ON ROW-DISPLAY. The user scrolls forward in the browse until the colored fields have scrolled out of the viewport at the top, and then moves the cursor back up through the viewport. When the cursor reaches one of the rows in the viewport that was previously colored, the colors appear again even though a different row is now in that position. If the user continues to move the cursor up until new rows scroll into the viewport at the top, the spurious colors disappear. If the user still continues to move the cursor up until the fields that should be colored come back into the viewport, those fields are colored correctly. ================================================ Web Services Client ================================================ Issue Number: OE00205600 Support for SOAP 1.2 The OpenEdge Web Service client now supports SOAP 1.2 Issue Number: OE00220557 Failure initializing SOAP Call: (11762) Failure initializing SOAP Call: Cannot match signature for operation getProcessInstanceDataSlotFromPIID' (11762) Issue Number: OE00225021 Error (11478) consuming a Webservice over HTTPS Error loading WSDL document :internal error: Receive status (11748). Issue Number: OE00233867 AVM leaves environment variable in inconsistent state The AVM uses an internally set environment variable during the initialization of the SOAP library that is left in an inconsistent state, pointing at random data (possibly nulls) ================================================ WebClient ================================================ Issue Number: OE00200227 WCAA fails to open .wcp with .NET If you add .NET information (e.g. including UltraControls or a .NET Framework installer) to a WebClient project, then save the project without generating a version, the WebClient Application Assembler will fail to open the project file the next time you try to open it. It will display a blank error message. Issue Number: OE00231410 Webclient upgrade falsely believes upgrade is already installed. Webclient upgrade falsely believes upgrade is already installed. When upgrading WebClient from 11.1 FCS to hotfix 11.01.016, the installer should prompt for WebClient update dialog box, but instead it generates this message: The setup has detected that version 11.01.000 of WebClient is already installed. This setup updates WebClient to the same version that is already installed, therefore this update is not needed. Do you want to install the update anyway? When the Yes option is clicked, it does not update to 11.01.016 correctly. Issue Number: OE00231749 DYNAMIC-NEW w/relative path doesn't download As Needed compon When calling DYNAMIC-NEW on a WebClient application for a class that is in a As Needed (lazy) component, and using relative path (not relative to the application's working directory), the component will not get downloaded and the application will issue error 14284 Issue Number: OE00234696 WebClient installer not installing .Net 4.0 If WebClient application requires the existence of .NET 4.0, and is packaged with the .NET 4.0 installer, the WebClient application installer does not install .NET 4.0 on Windows if .NET 4.0 does not already exist on the machine. ================================================ WebClient WebClient Initializer ================================================ Issue Number: OE00230885 Application is not launched after WebClient installation WebClient application is not launched after WebClient installation ================================================ WebSpeed ================================================ Issue Number: OE00223665 poor performance of cgiip.exe on 10.1C and higher poor web server performance under heavy load of cgiip.exe on 10.1C and higher Issue Number: OE00225308 WebSpeed agent crashes when updating to utf oracle db thro ODS WebSpeed agent crashes updating a record through trigger in to the utf oracle database. The schema holder is also UTF-8. The agent uses -cpinternal and cpstream 1252. The gui client works fine. Issue Number: OE00226680 Error trying to start workshop using wsisa.dll Error trying to start workshop using wsisa.dll Issue Number: OE00229828 DisconectService method example is wrong in asphelp.htm The DisconnectService() method example in asphelp.htm under %DLC%\webspeed\wsasp is not correct. it is just a copy from CustomizeErrorMessages example. Issue Number: OE00233058 DisconnectService() method never works for wsasp.dll messenger The DisconnectService() method never works for wsasp.dll messenger which causes maxClientInstance to be exhausted. ================ PROGRESS TOOLING ================