Progress OpenEdge 11.1.0 Readme

Ports: All
Date: June, 2012
Copyright (c) 1984-2012 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_<release#>_VERSION.htm (Lists fixed issues by Version)
  * PROGRESS_OE_<release#>_ISSUE.htm (Lists fixed issues by Issue Number)
  * PROGRESS_OE_<release#>_COMPONENT.htm (Lists fixed issues by Component)



1. Installation
2. ABL
  Language Issues
  Web Services client
3. Adapter for Sonic ESB
4. ADE Tools and Runtime
  Data Dictionary
  GUI Rendering
  Translation Manager
  Web Rendering
5. AppServer
6. Database

  Database Utilities
  Failover Clusters
7. DataServers
8. Documentation
  Electronic Documentation
  Progress Developer Studio for OpenEdge
9. Graphical User Interface
10. Management
11. Open Client
  Web Services Provider
12. Progress Developer Studio for OpenEdge
  Visual Designer
13. OpenEdge GUI for .NET
14. Porting
15. SQL
16. Web Services Client
17. WebClient
18. WebSpeed

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.

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
  - Choose "Progress OpenEdge Deployment Components"
  - Choose "Microsoft .NET Framework" download page

Note: OE00175812  Type: Known Issue
Windows 64-bit Silent Install does not work
The Windows 64-bit Silent Install does not work.  To install  the Windows
64-bit OpenEdge product, you must run the install interactively.

Note: OE00176073  Type: Known Issue
Embedded Microsoft .NET Framework will not install in a Windows 64-bit OS
OpenEdge embeds a 32-bit  English version of the Microsoft .NET Framework in
the OpenEdge installer.  This 32-bit .NET Framework does not install on any
Windows 64-bit operating system.  If you require the .NET Framework (for
ProxyGen or using the OpenEdge Ultra Controls for .NET, for example), you must
first install a 64-bit version of the .NET Framework.  You must install the
64-bit .NET Framework when using either the 32-bit or 64-bit versions of

To download different languages of the .NET Framework 3.0 as well as the
Windows 64-bit version:
  - Login to
  - Choose "Progress OpenEdge Deployment Components"
  - Choose "Microsoft .NET Framework" download page

Note: OE00183985  Type: Limitation
Compatibility messages displayed during OpenEdge install on Windows 7
Two messages stating that the programs have known compatibility issues are
displayed during the install of all OpenEdge products on Windows 7. Both of
these issues are related to the Microsoft JVM.

After the messages are displayed, you are prompted to "Check for solutions
online, run program or cancel."  Choose "run program" and the install
successfully completes from this point.

Note: OE00201877  Type: Limitation
OpenEdge support on Windows XP
OpenEdge supports Windows Service Pack 3 and later for the Windows XP platform.

Note: OE00222209  Type: Known Issue
Silent installation of Progress Developer Studio for OpenEdge may abort
Using the generated response file (%DLC%\install\response.ini) to perform a
silent installation may cause the installation to abort.

The install program may not add required responses to the silent response file
when installing the Progress Developer Studio for OpenEdge product. The
problem occurs when installing on a system that does not have a previous
instance of DeveloperStudio3.6 installed.

To workaround this problem, add the following 4 lines to the response file:

[Install Options]


Note: OE00217697  Type: Behavior Change
New startup parameter causes AVM to re-read records with missing FIELDS
If a query with a field list (FIELDS or EXCEPT option of the record phrase)
reads a partial record, and a field is subsequently referenced that is not in
the field list, the AVM normally raises a runtime error (8826). With the
-rereadfields startup parameter, the AVM instead suppresses this error and
re-reads the full record from the database.

Note: OE00218781  Type: Behavior Change
The DECIMALS attribute for a temp-table buffer-field object is now READ-WRITE
In releases prior to OpenEdge Release 11.1, the DECIMALS attribute for a
temp-table buffer-field object was READ-ONLY.  It has been changed to be
READ-WRITE for temp-table buffer-field objects (but not for database
buffer-field objects).

Note: OE00220791  Type: Known Issue
Repair for ABL "SAVE CACHE" failure on converted database (Release 10 to 11.0)
Execution of the ABL "SAVE CACHE" statement causes a memory access violation on
a Release 11 database, that was converted from a Release 10 database with
PROUTIL CONV1011 in OpenEdge Release 11.0.0.

The problem is caused by an incorrect value in the Progress internal SCHEMA
definition. You can correct the problem by running the DBTOOL utility. Enter
dbtool <database> and select the "Schema Validation" option.

Note:  Databases converted with OpenEdge 11.1.0 do not encounter this problem.

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: OE00124868  Type: Behavior Change
EBCDIC codepages no longer provided in convmap.cp
For OpenEdge 10.0A, EBCDIC codepages are not provided in convmap.cp shipped
with the product. For example, there is no codepage conversion possible from
IBM278 to ISO8859-1.

Customers who require codepage conversions to or from EBCDIC codepages can use
the following steps to allow these conversions:

1. Uncomment "INCLUDE weuroebc.dat" in
2. Rebuild convmap.dat into a new convmap.cp with the proutil utility.

proutil -C codepage-compiler <path-to-convmap.dat> <path-to-new-convmap.cp>

3. If the new convmap.cp is not in the [install-dir], make sure the PROCONV
environment variable is set to point to the location of the new convmap.cp.

EBCDIC codepages are provided only for conversion to a supported OpenEdge
codepage. The EBCDIC codepages must not be used for the AVM codepage
(-cpinternal), a CLOB codepage in a table, or as the database codepage.

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

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

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.

Note: OE00211327  Type: Behavior Change
XML documents no longer support GB_2312-80 encoding
OpenEdge can no longer handle XML documents with an encoding of GB_2312-80. The
correct encoding is GB2312. This affects the READ-XML() and WRITE-XML() methods
for a temp-table or DATASET-HANDLE, the SAVE() and LOAD() methods of an
X-DOCUMENT object, and the SAX-READER and SAX-WRITER objects.

ABL - Language Issues

Note: OE00104223  Type: Known Issue
To access large objects remotely, client and server must be OpenEdge 10.0B
Prior to OpenEdge Release 10.0B, LOBs could not be exchanged between a client
and a server on machines with different hardware architectures. In order to
access large objects remotely, both the client and server must be OpenEdge
10.0B or higher.  Use of prior OpenEdge versions will result in error messages
indicating a failure to update or retrieve a large object.

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.
( Copyright 2003 XMethods, Inc.  All rights reserved. Any use
of these services by you shall be for demonstration purposes only.


Note: OE00220427  Type: Behavior Change
READ-XML will fail to read a NOTATION element
In previous versions of OpenEdge, you were able to to define an element in a
temp-table with the XML-DATA-TYPE "NOTATION." The WRITE-XMLSCHEMA( ) method
would write this to an XMLSchema file, which the READ-XML( ) method could
consume when loading data into a temp-table from an XML file. However, the
XMLSchema generated is invalid, as NOTATION elements must not be defined in the
schema. Non-OpenEdge consumers of this XMLSchema will generate errors when
reading it.
As of OpenEdge 11.1.0, the READ-XML( ) method fails to read this XMLSchema and
provides the following error:
READ-XML encountered an error while parsing the XML Document:
'element/attribute '<fieldname>' is of NOTATION type'. (13064)

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 OpenEdge Architect/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

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

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.

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.

Note: OE00210034 Type: Product Notice
Changes in Database Administration utility menu options
The Database Administration utility menu options have changed:

For dumping and loading, the menu option previously titled "
Security Authentication Records", is renamed to "Security Domains".  For
  Admin -> Dump Data and Definitions -> Security Domains
  Admin -> Load Data and Definitions -> Security Domains

For database options (Admin -> Database Options...), the name of two options
have changed:
- "Use Application User Id for Auditing" is renamed to
  "Use Application Domain Registry"
- "Disallow Blank UserId" is renamed to "Disallow Blank UserId Connections"

For security, the menu options and labels have changed.
- "Authentication System Maintenance" is renamed to "Domain Maintenance",
  as shown:
  Admin -> Security -> Domain Maintenance
- "Security Authentication Systems" is simplified to "Authentication Systems",
  as shown:
  Admin -> Security -> Domain Maintenance -> Authentication Systems
- "Authentication System Domains" is simplified to "Domains", as shown:
  Admin -> Security -> Domain Maintenance -> Domains
- The new title of the dialog box is "Domains".
- Field names on the Domains -> Create dialog box are changed:
  "Type" is renamed to "System Type"
  "PAM Options" is renamed to "System Options"

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
  adm2/image 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 into the target directory for a WebClient

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.

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 (<sdo>_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

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

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

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 <None> or <All> 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

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:


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

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.


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 <n> not unique (<widget-name>) 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 <name>. (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 <viewer-name>:<field-name>.

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

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
BUFFER-FIELD RowUserProp was not found in buffer <dataset-buffer-name>.(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

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,

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
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

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

The product module <product-module1> and the product module <product-module2>
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

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 <number> Instance
Number <number> Language  Name "<language>". (132)

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

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.

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

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.

Database - Database Utilities

Note: OE00070876    Type: Known Issue
PROUTIL IDXFIX -silent is not silent
Running PROUTIL IDXFIX with the -silent parameter does not suppress the display
of repetitive messages or prevent repetitive messages from being written to the
log file.

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.

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

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
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 chatacter 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.

DataServers - DB2

Note: OE00218712    Type: Known Issue
Failure to migrate data from OpenEdge to DB2/400 with create RECID option
Simultaneously using CREATE RECID and Move data options in the OpenEdge to
DB2/400 migration utility results in an application crash.  You might encounter
other problems with record I/O and other database operations using the CREATE
RECID option.  Progress recommends that you avoid using the CREATE RECID option
during OpenEdge to DB2/400 migration in release 11.1.

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

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.
CREATE Temptbl.
IMPORT Temptbl.
/* create a record in the foreign DB */
CREATE test.
BUFFER-COPY Temptbl EXCEPT fld1 TO test.


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.


This syntax is for setting the buffer size for the RECID area,

    (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: OE00202425    Type: Product Notice
Increased stack size limit in MS SQL and Oracle DataServer
To increase DataServer processing capacity for an SQL statement, the WHERE
clause stack size limit has been increased from 8192 bytes to 30000 bytes.
Consequently, your run-time stack size requirement for the application might
increase and you might receive the following run-time error message:

SYSTEM ERROR: stkpush: stack overflow. Increase -s parameter.
SYSTEM ERROR: stkditem: stack overflow. Increase -s parameter

The workaround is to increase the stack size limit of your ABL application
using the -s session startup parameter. The recommended limit is 128.

Note: OE00203930    Type: Known Issue
Usage of MS SQL Server legacy LOB data types in stored procedures
The ODBC layer throws an error in the following two cases when it finds legacy
LOB data types in stored procedures in your DataServer application:

1.When you use the legacy large object (LOB) data types, ntext\text\image, as
OUTPUT parameters in a stored procedure definition in a DataServer application.

2.When you use current large object (LOB) data types,
nvarchar(max)\varchar(max),varbinary(max), as OUTPUT parameters in a stored
procedure definition in a DataServer application with a non-native ODBC driver.

The ODBC layer throws the following error message:
"37000: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid parameter 1
(''):  Data type 0x63 is a deprecated large object, or LOB, but is marked as
output parameter.  Deprecated types are not supported as output parameters.
Use current large object types instead."

The DataServer application will stop execution if the error condition is not
handled.  By handling the error during the RUN STORED-PROCEDURE statement, such
as with the OpenEdge ABL NO-ERROR option in the following ABL code, the
application can continue to execute even though an output parameter is not
received after running the stored procedure:

Define variable <ix> as integer.
Define variable <flag> as logical initial FLASE.
<Server LOB type mapped to OE CHAR>) .
    IF INDEX (ERROR-STATUS: GET-MESSAGE(<ix>), "Invalid parameter'') > 0
  <put the logic here>
  <flag> = TRUE.
     IF <flag> = FALSE THEN
     CLOSE STORED-PROCEDURE <proc-name> WHERE PROC-HANDLE = <handle1>.

Note: OE00208671    Type: Limitation
In MSS DataServer, TRIM option is unsupported in the COPY-LOB statement
Although, the OpenEdge 11.0 and 11.1 releases were intended to enable you with
the ability to use TRIM option in the COPY-LOB operations, the feature
implementation is ongoing and is likely to be included in the coming releases.

In OpenEdge 11.0 documentation, please disregard the utilization of TRIM phrase
in the "COPY-LOB Statement" discussion in the "OpenEdge Development: ABL
Reference" manual.

Note: OE00211239    Type: Product Notice
Re-pull definitions before executing an SQL view with a PROGRESS_RECID computed
It is recommended that you refresh the schema definitions of any SQL view
containing the PROGRESS_RECID computed column by re-pulling the schema
definitions from the server to the schema holder. This prevents the OpenEdge
client from crashing while utilizing the SQL view with incorrect schema

Note: OE00213341    Type: Limitation
Clustered constraint modification/addition through Delta SQL utility
MS SQL DataServer does not support clustered constraint modification or
addition through the Delta SQL utility. A clustered index is not only an index
but also acts as a method for storage. Any addition or modification to the
clustered index on an existing MS SQL server database table has overheads
associated with it. The DataServer has to discard the existing clustered index
in order to rearrange data containing new components within the table. Since a
clustered index is a part of all other indexes on a table, all the indexes will
be rebuilt. SQL server will require space to accomplish both data rearrangement
and movement.

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

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: OE00219645    Type: Limitation
8k support for OUTPUT LOB parameter in MS SQL Server stored procedures
MS SQL Server DataServer (henceforth MSS DataServer) provides  support for MS
(henceforth LOB) as INPUT/OUTPUT parameters in a stored procedure. You can pull
these foreign objects into your schema holder and map the parameter types to an
OpenEdge BLOB/CLOB by choosing "Default to OpenEdge LOBs" option on a schema
pull, and then you can execute MS SQL Server stored procedures from MSS
DataServer application.

The OUTPUT LOB parameter support in MSS DataServer is contingent on ODBC driver
or MS SQL Server support for LOB as stored procedure output parameter. For
example, not all ODBC drivers for MS SQL Server provide support for LOB as
stored procedure output parameter. Moreover, ODBC driver can only retrieve the
output parameters of a stored procedure using bound buffer mechanism.

Therefore, the support for OUTPUT LOB parameter value is limited to 8000 bytes
that also includes the null terminator byte for VARCHAR (MAX). Therefore, MSS
DataServer can only retrieve OUTPUT LOB parameter value upto a maximum of 8000
bytes. The excess data is truncated by the ODBC driver.

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 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
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
  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
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

To see a list of the changes:

1. Go to the following URL:

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

2. Click on the "Search for . . ." link in the help pane. A list of relevant
topics appears.

Graphical User Interface - ActiveX

Note: OE00212914    Type: Known Issue
Crystal Reports 11 causes crash in some environments
Adding an instance of the Crystal Reports X1 ActiveX Report Viewer to a window
causes a crash on certain platforms (such as Windows 7 or Windows 2008 Server,
with Visual Studio 2010).  This occurs with Crystal Reports X1 ActiveX Report
Viewer V11.5 or later 11.0 versions.  As this is a third-party issue, the crash
might occur with OpenEdge 11.0.

Note: OE00214005    Type: Known Issue
VideoSoft IndexTab control does not display properly in some environments
The VideoSoft vsIndexTab OCX is not displayed at runtime in certain
environments (e.g., Windows 7 64-bit with Visual Studio 2010). This is a third
party issue and  therefore, the same behavior can be seen in OpenEdge 11.0.

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 or 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 file is renamed
When uninstalling the file is renamed
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.

Note: OE00215824    Type: Known Issue
No validation when deleting users from a database
The OpenEdge Management Console does not perform any validation when you delete
the last user from a database, whereas the Data Admin tool prevents deletion or
displays a confirmation dialog allowing you to change security settings to give
access to all data when you attempt to delete the last user.

If the database option to disallow blank user ids is set in OpenEdge Management
Console, deleting the last user will prevent any user from logging into the

The following validations/actions of the Data Admin tool, do not take place
when using the OpenEdge Management console:

* A confirmation dialog is not displayed when deleting the last user.
* The security administrator fields are not set to "*" to give access to
everyone when the last user is deleted.
* An error message or confirmation is not displayed when deleting the last
security administrator.
* Does not prevent you from deleting the current user when other users exist.

Note: OE00216855    Type: Behavior Change
Default tenant Partitions now contains only multi-tenant partitions
The Default tenant's Partitions collection now contains only the multi-tenant
partitions. In earlier releases, the Default tenant's Partitions collection
also included the shared partitions.

Note: OE00221347    Type: Known Issue
Paging bar for users in the Edit tenant page shows incorrect information.
In OpenEdge Management console, paging bar for users in the Edit tenant page
shows incorrect information. A search shows a number of blank pages even though
there are no users of that particular tenant.

Note: OE00221834    Type: Known Issue
Load of .df file fails for multi-tenant tables with no area defined for indexes
In Database Administration Console (DAC), the Data Definitions (.df) file fails
to load for multi-tenant tables with no area defined for indexes.

Management - Management

Note: OE00215906    Type: Behavior Change
OpenEdge Management command-line utilities now require username and password
The Fathom command line utility now requires the use of -user and -password
parameters.  A valid OpenEdge Management HTTP user name and password must be
provided when you run any command that makes use of the HTTP server.

The configuration backup job for OpenEdge Management requires the use of
FM_HTTPUSER and FM_HTTPPASSWORD environment variables. These variables are
passed to the Fathom command line utility for the values of -user and

Note: OE00219852    Type: Known Issue
Uninstalling Sonic from OpenEdge Management might generate exceptions on Linux
Uninstalling SonicMQ from OpenEdge Management as part of running the unglue
command might fail on Linux due to an issue with the version of InstallShield
used by Sonic MQ 6.1.  These exceptions may be ignored and the unglue operation
will succeed.

Note: OE00221238    Type: Known Issue
Edit security administrator link is disabled with the OE 11.0 container
In the Database Administration Console, the Edit security administrator link in
the Security Summary section is disabled when working with the OE 11.0
container and 11.1 Admin Server service. The link will not be available after
the first time you make any changes to the Edit security administrator page.

Note: OE00221740    Type: Known Issue
Refresh of alerts happens continuously after clicking Mark Seen and Mark Unseen
In OpenEdge Management Console, refresh of alert happens continuously after
clicking "Mark Seen" or "Mark Unseen" on an alert.

Open Client - .NET

Note: OE00216895    Type: Behavior Change
.NET DataColumn.DefaultValue not set correctly if ABL initial value = ""
Starting in Releases 10.2B and 11.1, if an ABL CHARACTER field has an initial
value of "", its corresponding .NET DataColumn.DefaultValue property will also
be set to "". But in the .NET client, when a new row is created for the
DataTable, the default value of the DataColumn will be DBNull, and not "" as

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

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.

Progress Developer Studio for OpenEdge -

Note: OE00221899    Type: Known Issue
Loading images in Samples or Tutorials from Progress Developer Studio
You may experience long loading times for images after downloading from the
Samples or the Tutorials sections on the Welcome page for Progress Developer
Studio for OpenEdge.

Note: OE00221900    Type: Known Issue
Welcome page issue in Progress Developer Studio for OE on Eclipse 3.7.1
The Welcome page is not shown when selecting Progress Developer Studio for
OpenEdge in the Welcome dialog. This happens when:

- You install Progress Developer Studio for OpenEdge on Eclipse 3.7.1.
(Progress Developer Studio for OpenEdge ships with Eclipse 3.6.)

- There are multiple Welcome pages in the installation.

A workaround is to use the Help menu in the Samples or Tutorials sections and
select the Home icon.

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

Progress Developer Studio for OpenEdge - Editing

Note: OE00201924    Type: Known Issue
Progress Developer Studio Outline view errors with &IF preprocessors in DO blocks
When preprocessors are used to conditionally include or exclude code statements
inside DO blocks, the Progress Developer Studio Outline view doesn't show all the code
elements correctly.

Note: OE00202892    Type: Known Issue
Errors generated when adding or removing comments in SpeedScript files
In Progress Developer Studio, an error can occur when you comment a SpeedScript file
using Toggle comment, or Add block comment from the context menu.  A
StructuredDocumentRegionManagementException error appears in log files if the
file contains "`" tags (used for displaying the value of an ABL variable in
HTML fields).

The error also occurs if you use CTRL+Z to remove comments.

Progress Developer Studio for OpenEdge - Visual Designer

Note: OE00195134    Type: Product Notice
Cannot compile/run generated code in previous versions
When you use the Visual Designer to edit GUI for .NET code created in an
earlier OpenEdge version, the generated code is updated to the current version
of Progress Developer Studio and thus may contain new language constructs that are not
compatible with previous compiler and AVM versions. Additionally,
wizard-generated code may be incompatible with previous versions. Such
incompatibilities can occur even when you do not explicitly use new features
from the current version.

Therefore, 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 10.2B of the
Visual Designer will no longer compile in 10.2A.

OpenEdge GUI for .NET -

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:

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:


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.

Note: OE00199787    Type: Behavior Change
Warning 16679 may appear when an embedded window is implicitly destroyed
Warning message 16679 appears when an ABL window that is embedded in a .NET
form is destroyed during destruction of the form. Applications should destroy
an embedded ABL window when the form it is contained in receives the
FormClosing event. If an application does not clean up an embedded ABL window
before the FormClosed event is received, the ABL window will be destroyed but
the procedure that created it will still be running. This can cause the AVM to
crash if the procedure subsequently refers to a widget that has already been

Note: OE00217294    Type: Behavior Change
previousState property of Progress.Windows.Form is no longer public
Previously, Progress.Windows.Form had a public property called previousState.
previousState is now an internal property rather than a public property; the
property is no longer accessible through ABL.

Note: OE00218594    Type: Known Issue
R-code that uses the UltraControls for .NET is incompatible between versions
OpenEdge 11.1.0 includes Infragistics NetAdvantage for .NET v2011 Vol 2
Copyright (c)
2001-2011 Infragistics, Inc. All rights reserved.

The UltraControls for .NET version changes in between OpenEdge releases. You
must recompile any r-code created in OpenEdge Release 10.2A, 10.2B, or 11.0.0
before running the code in OpenEdge 11.1.0.

For information about any changes to the controls in 2011.2, see

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 is missing
fmconfig fails on Red Hat Linux 5 when the library 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:

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.


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:


The parameter is also available to use with connection URLs for the SQLDump,
SQLoad, and SQLSChema utilities.


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

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

Note: OE00212547    Type: Known Issue
SQL fails to identify a DBA user at the first query in an auxiliary database
While parsing the first query in an auxiliary database, OpenEdge SQL does not
identify a DBA user. Therefore, any metadata (including statistics) might have
only a regular tenant view. As a workaround, you can run a dummy query (for
example: select * from sysprogress.syscaltable) when you use the auxilary
database for the first time. During the execution phase of the dummy query, the
correct state of the DBA is known and is recorded in the rss layer.

Note: OE00220355    Type: Known Issue
Limited scalar functions are supported by tenantid_tbl and tenantname_tbl
Only the following scalar functions are supported by the tenantid_tbl and
tenantname_tbl virtual columns:
-case - result expr

They also support the aggregate functions MIN, MAX, COUNT.

SQL - Tools

Note: OE00195893    Type: Workaround
The SQLLOAD utility fails on IBM AIX while loading a huge table
While loading a huge table containing many columns (of size 32k or more), the
SQLLOAD utility may fail and display a NO MEMORY error message. This happens
only on the IBM AIX machine.

This problem occurs due to failure in allocating the required memory from the
heap. The following two workarounds can solve this issue:

- Increasing the data segment size limit by using the ulimit command:
     ulimit -d unlimited
- Using the SQLLOAD option, -r, to specify a lower number of rows to be
inserted as a block:
     sqlload <all other options> -r 30

By default, the SQLLOAD utility tries to fit 50 rows into a block. Lowering
this number may solve the issue.
If the SQLLOAD utility fails despite of reducing the number of rows in a block
to 30, you can try and reduce it further.

Note: OE00220807    Type: Known Issue
Incorrect behavior by SQLDUMP while dumping multi-tenant group data
The SQLDUMP utility has the ability to dump multi-tenant group data for groups
defined on multi-tenant tables.  It does so, when requested by the "-g" command
line option.

If any of the groups to be dumped has 0 (zero) tenants associated with itself,
then no group data is dumped.

Note: OE00221575    Type: Known Issue
SQLSCHEMA fails to dump multi-tenant table definitions with indexes and groups
The SQLSCHEMA utility does not dump proper index or constraint definitions for
multi-tenant tables which have indexes, constraints, and groups defined on
them, and have tenants attached to the groups.

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

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

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:

EXEs that could be used by your install:
* ini2reg.exe
* regsvr32.exe (A Microsoft tool usually, but not always, installed on a
typical PC)

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 file is created in the $DLC/properties location. Prior to
OpenEdge Release 11.1, it used to be the file. This changed
behavior on Windows is now consistent with the behavior on UNIX.

Note: You can rename the file to the file.

2) WebSpeed Messenger only installation performed over the existing OpenEdge

a) The file is created in $DLC/properties.
b) The existing file is saved as

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.



Issue Number: OE00129394
     Error (9986) (7175) connecting to AIA from .NET Open client

The error 7175 occurs when connecting to AIA from a .NET Open Client :
Additional information: Communication layer message: General Error: An
http protocol error occured: A HTTP response is not available (9986) .

The AIA connects directly to the AppServer port.

Issue Number: OE00136057
     Cursor-offset of a fill-in with unicode characters fails

Changing the cursor-offset of a fill-in with multi-byte unicode characters
results in an incorrect cursor-offset.

Issue Number: OE00147968
     COMBO-BOX:SCREEN-VALUE behavior if LIST-ITEM-PAIRS has blank val

If a combo-box list-item-pairs contains a blank character string as a
possible value, the combo-box will show inconsistent behavior with regards
to how the screen-value is handled.

Issue Number: OE00156053
     gethostname >30 characters returns -1 which results in 528 error

On Linux, the gethostname function when the hostname is >= 30 characters
returns a -1 for a return code.  This results in Progress setting the
hostname in the .lk file to nulls when using procopy and prodb.  The
creation of the lk file fails with 528 error indicating invalid .lk file.

Issue Number: OE00164470
     x and y attributes not being cased properly

when there are variable whose names are  x and y, then co-ordinate
attributes X and Y for frame definition do not get correct cased on
correct case action.

Issue Number: OE00169765
     Warning (3619) is displayed for LENGTH function with -checkdbe

When using -checkdbe, warning message (3619) is displayed when compiling
the LENGTH function with only one parameter.

Issue Number: OE00174009
     Adding field in Progress Developer Studio gives warning message loading delta df

Adding or copying a field using the DB Navigator in Progress Developer Studio sets
_field._decimal to 0 instead of a question mark (unknown), even if the
data type is not decimal.

Issue Number: OE00176452
     Font color incorrect for class named like schema element

In a OpenEdge project with OpenEdge DB connected to it, define a class
file, provide the class name as one of the table name of connected DB. the
color coding of class name gets color coding of schema elements. This
misleads user from identifying an schema element from class name or
variables whose names are same as schema elements.

Issue Number: OE00183485
     SAX parser does not convert customized code pages

Tha SAX parser does not perform correct code page conversions in a
callback procedure when the -cpinternal code page involved is a customized
code page, and the callback input is a LONGCHAR.

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.

Issue Number: OE00194003
     Double Colon Field References Can Get Error 7351 at Runtime

Using double colon references for dynamic buffers where the field name is
either timezone or mtime will cause error 7351 to be raised at runtime.

Issue Number: OE00092390
     SEARCH function and FILE-INFO handle return incorrect results

When using the SEARCH function or the FILE-INFO handle with multi-byte
characters such as those found in Traditional Chinese Windows and BIG-5,
or SHIFT-JIS (Japanese) or UTF-8, it returns incorrect results. The file
used with the SEARCH function is NOT on the PROPATH, yet it returns a
value, rather than ? as it should because the result is unknown.

If a .pl file is found in your propath it returns the result that the file
was found in the procedure library.

e.g.<<kanji chars>>

Issue Number: OE00115943
     Error 4059 with translated format for LOGICAL variable

Error 4059 (Attribute <attribute> for the <widget id> has an invalid value
of <yes/no>) may occur when the format string for a LOGICAL variable is
translated and the translated format is longer than the original format.

Issue Number: OE00116839
     OUTPUT TO PRINTER PAGE-SIZE 0 does paged printing in GUI client

The PAGE-SIZE 0 option of the OUTPUT TO PRINTER statement does not do
continuous (unpaged) printing in the Windows GUI client.

Issue Number: OE00135940
     Incorrect string length in string XREF file when using -ulayout

String lengths may be incorrect in the string XREF file when the -ulayout
startup parameter is used. This issue affects TranMan since TranMan uses
the data in the string XREF file.

Issue Number: OE00170747
     "!" in label only works if browse is realized or default has "!"

Using "!" in the LABEL of a browse column to make it stacked does not work
when the browse column's label is changed before the browse widget is
realized, unless the original label in the data source also is stacked.

Issue Number: OE00193252
     DELETE-LINE method breaks up carriage return/linefeed pairs

The editor widget's DELETE-LINE method does not always calculate the
beginning and end of the line correctly, breaking up carriage
return/linefeed pairs

Issue Number: OE00193780
     SUBSTRING, ENTRY, and LENGTH statements fail w/ colon syntax

In the SUBSTRING, ENTRY and LENGTH statements, if the argument that is the
target of the operation is qualified (that is, it uses the colon syntax),
the statement compiles but does nothing at runtime. (Note that this does
not apply to the functions that have the same names -- they work
This is true whether the qualifier is an object reference, THIS-OBJECT, or
a handle variable referring to an attribute.
For example,
   SUBSTRING(THIS-OBJECT:x, 1, 1024) = "".
has no effect on the data member 'x'.

Issue Number: OE00195481
     Error 10068 when using chained object references in OO

When using chained object references in OO, you can get error  "Lead
attributes in a chained-attribute expression (a:b:c) must be type HANDLE
or a user-defined type and valid (not UNKNOWN). (10068)"

Issue Number: OE00195770
     Dataset creation from XML fails with identical unique index name

If a dataset, that contains unique indexes with the same name from 2
different tables, is created from an XSD the fill event-handlers fails
Parameters for procedure <name> (table <name> and table <name>) do not
match. (12311)
By-REFERENCE Parameters for procedure <name> (table <name> and table
<name>) have indexes that do not match. (12312).

Issue Number: OE00196325
     Error 9324 concatenating a LONGCHAR and a CHARACTER variables

The error: ' Attempt to exceed maximum size of a CHARACTER variable.
(9324) ' is generated assigning the result of concatenating a LONGCHAR
variable and a CHARACTER variable to a CHARACTER variable.

Issue Number: OE00202083
     UTF-8 CLOB field as parameter bigger than 32K fails silent

When passing a temp table as a parameter to or from an appserver
procedure, if the temp table contains a UTF-8 CLOB and the clob contains
more than 32K of data, then the call to the appserver will fail silently.

Issue Number: OE00203773
     READ-JSON doesn't parse unicode escapes if source is UTF-8

If a source JSON structure contains a Unicode escape sequence ("\u...." ),
that sequence is not correctly converted to a character when parsed by the
READ-JSON method.

Issue Number: OE00204535
     UNDO, THROW invalidates thrown error object

Calling an error object which has been saved away and THROWn, but not
caught, causes this error:

Invalid handle.  Not initialized or points to  a deleted object (3135).

Issue Number: OE00205152
     Invalid result of string(logical, format) in UTF-8 environment

The result value of string(logical, format) in a UTF-8 environment may
return spaces if the format contains multi-byte characters.

Issue Number: OE00206569
     UNBOX function fails with error 223

In some circumstances the UNBOX function fails with this error at compile

Incompatible data types in expression or assignment (223)

Issue Number: OE00206829
     XML-NODE-NAME attribute isn't passed back with dataset parameter

when a dynamic dataset is passed as a parameter to a procedure that
associates the dataset with a static dataset, the XML-NODE-NAME attribute
is not passed back to the calling procedure with the dynamic dataset.

Issue Number: OE00208712
     SAX-PARSE() crashes session if URL > 226 char & HTTP URL blocked

The SAX reader object SAX-PARSE() method crashes the ABL client session
when the SET-INPUT-SOURCE() method gets input a HTTP URL that is greater
than 226 characters and the client fails to connect to the site for some

Issue Number: OE00210976
     Browse scrollbar down button becomes unresponsive

In some cases, the scroll down button on a browse scrollbar stops
responding. The other parts of the scrollbar keep working, as does
keyboard scrolling.

Issue Number: OE00211447
     A prodataset before-buffer doesn't know its parent dataset

A prodataset before-buffer doesn't have its dataset attribute set even
though it is part of a prodataset.

Issue Number: OE00212181
     Colors for enabled browse cells rendered wrong

BGCOLOR and FGCOLOR for browse columns misbehave if the browse's
COLUMN-MOVABLE attribute is true and columns are enabled. If the columns
are moved after the color attributes have been set, a cell that receives
focus is rendered with the colors based on the column numbers at the time
the colors were set instead of the current column colors.

Field A is column 2 and Field B is column 3. Both are enabled fields.
Field A has the BGCOLOR set before moving columns. Field A and Field B
have their columns switched. Now Field B gets focus - it's rendered with
the colors Field A is supposed to have.

Issue Number: OE00214235
     Literal strings truncated onscreen when using -ulayout

Literal strings may be truncated onscreen when the -ulayout startup
parameter is used to compile and create UTF-8 r-code.

Issue Number: OE00214492
     Frame height incorrect after modifying virtual height

A frame's height may be calculated incorrectly if the frame's

Issue Number: OE00214981
     xsdto4gl doesn't recreate tt indexes w/DESCENDING components

An .xsd file created by WRITE-XML  includes the attribute
'prodata:descending="true"' for descending components of a temp-table
index, but it does not include a corresponding
'prodata:descending="false"' for ascending components. This is true even
if the original temp-table definition included an explicit ASCENDING
keyword for some component. The temp-table definition created from this
.xsd by the xsdto4gl utility also does not include the ASCENDING keyword
for any ascending index components, which means that the generated
temp-table definition may not match the original definition. If the
original temp-table definition had a DESCENDING component followed by an
ASCENDING component, the WRITE-XMLSCHEMA and the xsdto4gl utility will not
restore the ASCENDING keyword, and when the index is used the component
that originally sorted ASCENDING will sort DESCENDING.

Issue Number: OE00215128
     Crash while handling event when using reusable objects cache

The session may crash while handling an event if the reusable objects
cache is active.

Issue Number: OE00215221
     ABL window with OCX flickers on launch when .NET form present

An ABL window with one or more OCX controls may flicker when being
displayed. The window may appear to lose focus momentarily or its title
bar may switch from activated to inactivated repeatedly. This behavior can
occur in applications which have displayed a .NET form. It may also occur
if the -nozgrouping startup parameter is used. The flickering is more
pronounced in windows which contain multiple OCX controls.

Issue Number: OE00215230
     Tooltip reappears when scrolling or resizing

The tooltip of a hidden widget will reappear if the containing frame or
window is scrolled or resized.

Issue Number: OE00215440
     Application slowdown using session:multitasking-interval

The fix for OE00176716 "Events lost if MULTITASKING-INTERVAL greater than
0" introduced a performance issue.

Issue Number: OE00215554
     -inp causes error 2939 with preprocessors

Increasing the value of -inp above 32000 with code that contains a
preprocessor results in error:

Preprocessor expansion buffer overflow. (2939)

Issue Number: OE00215635
     -IOEverywhere prevents resizing of windows with Codejock

In some cases using the new startup parameter -IOEverywhere can prevent
windows from being resized.  In this particular case where the CodeJock
OCX is involved, there appears to be a conflict in the functionality of
-IOEverywhere and SESSION:SET-WAIT-STATE function.

Issue Number: OE00215672
     Compiler crash with :U attribute on quoted class names

When using the :U attribute on quoted class names this can result in a
compiler crash when checking syntax or compiling if ASSIGN is used.

Issue Number: OE00215988
     Error 11773 in WS client if response header callback procedure s

The following error may be raised when an ABL client invokes a method of a
web service when a response header callback procedure is set:

Error receiving Web Service Response: Wrong XML token encountered during
primitive type deserialization (11773)

Issue Number: OE00216144
     Triggers with extended characters do not work with UTF-8 client

Triggers with extended (non-ASCII) characters do not work with UTF-8
client. If compiling source code containing an extended character in a
trigger, the compiler will fail with the following error:
  Unknown event: <event-name> (3438)
When retreiving a keylabel of a keypress from the LAST-EVENT:LABEL
attribute, the keylabel will have garbage characters in it. This causes
problems in the AppBuilder when entering a keyboard event.

Issue Number: OE00216181
     Overridden AddMessage Doesn't Retain Error Info

When using classes that inherit Progress.Lang.AppError and an override of
the AddMessage method is added to the class, calling that method results
in the error information not being retained.

Issue Number: OE00216203
     profiler:write-data crashes avm

profiler:write-data crashes avm

Issue Number: OE00216267
     Logical fill-in auto completion fails with -cpinternal UTF-8

The LOGICAL fill-in auto-completion feature fails to find a match if the
first letter of the format value is a multi byte character. This issue
occurs when -cpinternal UTF-8 is used.

Issue Number: OE00216517
     Incorrect table name shown for table when passed BY-REFERENCE

A buffer defined in a method of a class for a temp-table is incorrectly
referenced when referencing the temp-table in another method.  In this
instance, the buffer is never used or in scope and, in fact, the method is
never called.

When this occurs the following error may occur:

<buffer-name> must be an unabbrivated name or a buffer known query (7327)


This sometimes ends up in a crash with the following error:

SYSTEM ERROR: Memory violation. (49)

Issue Number: OE00217149
     Keeping the HELP (F1) button pressed down crashes

If the HELP (F1) button, which invokes an About Window or Dialog, is stuck
or is continuously pressed by the user, the session may crash and generate
a protrace file.

Issue Number: OE00217168
     QUERY-PREPARE crashes instead of showing error

When using QUERY-PREPARE, if the query statement is a string that contains
4GL code with a syntax error the compilation succeeds but at runtime
prowin32 crashes instead of giving an error message. A protrace file is

Issue Number: OE00217282
     READ-XML ignores XML elements reading from UNFORMATTED XML file

Populating a Temp Table using READ-XML to read from an unformatted XML
file results in a wrong record count. READ-XML fails to parse all the
elements and actually seems to be reading only the first one. The XML file
has been created using WRITE-XML  option Formatted set to FALSE.  However,
if the the same code is used to read a Formatted XML file, created with
WRITE-XML and Formatted set to TRUE then READ-XML is able to read all the
elements and correctly populates the temp table.

Issue Number: OE00217656
     err 15747 passing to input param defined Like Salesrep.MonthQuot

Error 15747 passing array to procedure input param defined Like

Value 189649658383 too large to fit in INTEGER. Line 0 in inoutIntArr1
C:\work\like\p75275_proctest-extent-bug2.ped. (15747)

Issue Number: OE00217697
     Automatically re-read record in case of error 8826

If a query with a FIELDS list has read a partial record, and subsequently
a field that is not in the FIELDS list is referenced, there would normally
be a runtime error (8826).  With the startup option -rereadfields, this
error is suppressed and instead we re-read the full record from the

Issue Number: OE00217889
     Win32 client crashes when COPY-LOB to Unix 64-bit DB server

When a Win32 OpenEdge 11 client is connected to a Unix 64-bit db, and the
client saves a picture in a BLOB db field using COPY-LOB and then
afterwards reads that db record and field again, the client session

Issue Number: OE00217903
     Error 40 repeatedly NEWing a class w/ NO-UNDO TT in transaction

Repeatedly NEWing a class that defines a NO-UNDO TEMP-TABLE inside a
TRANSACTION will eventually crash the session, produce a protrace and
procore files and generate error (40) (14675) similar to the following:

"SYSTEM ERROR: Attempt to define too many indexes for area <num> database
<dbi>. (40) (14675)"

The issue occurs only when the code is executed against the r-code of the
class and not against its source code.

Issue Number: OE00218015
     Code fails with error 14081 on 64-Bit Windows _progres.exe

Code that defines a variable using just the class name and not the fully
qualified class name will fail to compile when run in the character client
(_progres.exe) 64-Bit on Windows.  The same code will work with the
character client on a 32-Bit installation.

Issue Number: OE00218091
     DLL interface doesn't handle C float & double types on Win 64

On Windows 64-bit, OpenEdge doesn't handle the conversion from the ABL
DECIMAL type to the C float or double types and back correctly when
calling DLL functions. For example, a DLL function that returns a double
with a decimal value will be read as an integer value on the ABL side

Issue Number: OE00218123
     Error 13514 reading OE generated XML into temp-table

When reading xml that was generated from a static temp-table into the same
static temp-table using the READ-XML method, the following error occurs
the second and subsequent times the xml file is read within the same
session.  This only happens when the class reading the xml is uncompiled.

Temp-Table name 'ttLicense' in namespace '' not found in XML Document.

This problem did not occur in 10.2B05.

Issue Number: OE00218139
     Prefetch does not happen for no-lock forward-only queries

When fetching records over the network using a Static Open Query without
SCROLLING but with FORWARD-ONLY,  it appears that only one record is
transmitted per packet.

Issue Number: OE00218238
     Error(49) with READ-XML if schema file name and namespace long

When creating a dynamic dataset based on a schema-file and xml in a
longchar, if  the combined lengths of the dataset namespace-uri and the
schema-location parameter passed  to READ-XML exceeds a certain length,
then the application can crash with error (49), memory violation.

Issue Number: OE00218363
     Error 234 w/State-Reset AppServer in OE 11

Running a state-reset AppServer that connects to the OpenEdge database
using the default OS process user-id does not correctly reset the
connection's user-id to the original value after the AppServer client
disconnects.  One of the possible behaviors exhibited by this problem is
that the first client connection can run a procedure (testCon.p) and
access the database, while subsequent client connections can fail with a
database access error. The following error show this type of error:

** Insufficient access privilege for table  . (234)
** .\testCon.p Could not understand line 2. (196)

Issue Number: OE00218436
     FIND LAST fails on _TableStat

This error is raised when finding the last record in _TableStat :
**FIND FIRST/LAST failed for table _TableStat. (565)
FIND FIRST works as expected

Issue Number: OE00218437
     record locks not released using TABLE-SCAN

When executing a FOR EACH with TABLE-SCAN record locks are not released
until the end of the session.

Issue Number: OE00218679
     LAST-OF releases buffer in PRIVATE STATIC TEMP-TABLE

cause the buffer to be released, as demonstrated in the reproducible which
checks AVAILABLE on the buffer from within a LAST-OF condition block.

Issue Number: OE00218781
     Can't Set Decimals Property for Field in Dynamic Temp-Table

The DECIMALS property of the BUFFER-FIELD object is wrongly defined as
read-only.  It should be read-write.

Issue Number: OE00218818
     OCX causes crash when assigning property

When setting the ForeColor on the "HyperTicker" label control
(hticker.ocx), the session crashes leaving no protrace file.

Issue Number: OE00218877
     Random crash at rndelobj() when deleting dynamic buffer object

The OpenEdge client may crash when deleting a dynamic buffer object from a
database trigger for the same table.
The protrace file shows function rndelobj() in the call stack.

Issue Number: OE00218929
     Removing title from child frame fails with -cpinternal UTF-8

It's possible to remove the title from a static frame by setting the title
attribute to the unknown value before the frame is realized.
In OpenEdge 11.0, the title is not removed if -cpinternal is UTF-8. (Using
default ISO8859-1 codepage works fine)

Issue Number: OE00219197
     Error 3234 when moving/resizing window & multiple async requests

Mismatched number of parameters passed to routine handleIncommingMsg
jms/impl/message-header.p. (3234) if the client receives the response for
multiple asynchronous requests while moving or resizing a window.

Issue Number: OE00219240
     Creating many menu-items generates error 4025

There is a limit of 12,483 menu-items per session in the OpenEdge GUI
client. Exceeding the limit generates error 4025: **Unable to realize
<widget name>. (4025)

Issue Number: OE00219266
     Passing zero-length LONGCHAR to ABL functions crashes AVM

The following ABL functions can crash the AVM if passed a zero-lenth
This is a platform-specific issue. Some platforms might not crash. This is
known to cause a crash on CentOS 5.7 (64-bit) and Windows 64-bit.

Issue Number: OE00219323
     Crash calling GET-PARENT on X-NODEREF Attribute object

This was  introduced by the fix for bug# OE00197209.

Issue Number: OE00219375
     System Error kmkinit - 131 when using Dataset as REFERENCE-ONLY

There seems to be a problem when binding the Dataset and TempTable
definitions if they're are passed as REFERENCE-ONLY between classes.
Application crashes when trying to execute a FIND FIRST query in one of
the TempTables with error (131) IDX not found, however the dataset does
contain records as can be seen via an write-xml.

Issue Number: OE00219405
     Loading assemblies from -assemblies dir fails after timeout

When an application uses assemblies in the -assemblies directory , the AVM
can fail to load an assembly under the following conditions:
- there are some assemblies in the -assemblies directory that are not in
the assemblies.xml file;
- the assemblies.xml file contains at least one assembly from the
-assemblies directory;
- the AVM tries to load an assembly not in assemblies.xml from the
-assemblies directory more than 5 minutes after the AVM starts.
The attempt to load the assembly will generate the following message:
System.IO.FileNotFoundException: Could not load file or assembly
<assemblyname> or one of its dependencies. The system cannot find the file

The workaround is to include all referenced assemblies in the
assemblies.xml file.

Issue Number: OE00219429
     Fixed indeterminate array does not work as determinate array

In some situations fixed Indeterminate arrays are not behaving like
determinate arrays.  For example the IMPORT statement and the 11.0
JsonArray methods.

Issue Number: OE00219710
     REPOSITION-TO-ROWID method with array parameter raises error 316

Running <query handle>:REPOSITION-TO-ROWID(rowArray), where rowArray is an
indeterminant array of ROWIDs, raises error 3165.

Issue Number: OE00219847
     WRITE-JSON with LONGCHAR target crashes session on empty CLOB

Using the WRITE-JSON method with a LONGCHAR target variable fails and
crashes the session when a CLOB field is of zero length.

Issue Number: OE00220070
     AppServer memory leak when passing input dataset from WSA

The AppServer server will leak memory if being passed an input dataset
(static or handle) from a WSA client.

Issue Number: OE00220138
     READ-XML on empty temp-table incorrectly creates 1 record

Read-xml method on temp table .xml wiith no records incorrecly creates one
record populated with the initial values for the temp-table.

Issue Number: OE00220196
     Client crashes using TRIM functions on empty longchar variable

The client crashes when using the LEFT-TRIM or RIGHT-TRIM function on an
uninitialized LONGCHAR variable.

Issue Number: OE00220284
     -ulayout increases width requirements resulting in 4028

The width of a literal string widget is calculated incorrectly when the
-ulayout startup parameter is used. The miscalculation may result in error
4028 "LITERAL <string> will not fit in FRAME <frame> in PROGRAM".

Issue Number: OE00220304
     Crash applying START-SEARCH event to toggle-box column

The OpenEdge client crashes when the START-SEARCH event is applied to a
browse widget whose current column is a toggle-box column.

Issue Number: OE00220310
     DynObjects logging may report inconsistent memptr size

If you enable the DynObjects logging to track memptrs, in some cases the
size reported for the allocating and deallocation operations will not
match (such as when invoking the BASE64-DECODE() function).

Issue Number: OE00220506
     CR/LF is not output when using passthrough printing

Newline characters (CR/LF) are not output when passthrough printing is
used, resulting in printed output being displayed in one long line instead
of multiple lines. Passthrough printing is used when the printed output
contains printer control characters or the -Wa -wpp startup parameters are

Issue Number: OE00220533
     Temp-Tables with field of type CLOB causes DBI to grow excessive

In OE11.0 Temp-Tables with field of type CLOB causes DBI file to grow
excessively taking out disc space, the behavior is not observed under

Issue Number: OE00220745
     CALL object crashes after invoking function that returns LONGCHA

A dynamic invocation using the CALL object fails when a function is
invoked that returns a LONGCHAR, and the RETURN in the function passes
back a variable that was defined globally in the procedure containing the

Issue Number: OE00220787
     ASSIGN BUFFER is not taking SESSION TIMEZONE into account

to set a temp-table field with the value of NOW then the SESSION:TIMEZONE
is not taken into account. Using a direct ASSIGN tt.field_name = NOW
instead results in the correct value.

This issue only affect fields of type DATETIME, if the field is of type
DATETIME-TZ then both type of assignation work correctly.

Issue Number: OE00184385
     Calling external procedure SendMessageA no longer works

Calling the SendMessageA Win32 API function as an external procedure does
not have the expected effect. This issue occurs if the parameters in the
external procedure definition do not match the actual parameters of the
SendMessageA function.

ABL Language Issues
Issue Number: OE00216311
     Internal procedure with FOR EACH on REF-ONLY table causes crash

A program may contain a REFERENCE-ONLY temp-table. If the program contains
an internal procedure which performs a FOR EACH statement with a BY
clause, and the temp-table is not yet bound when this internal procedure
is called, this creates a situation which can cause the AVM to crash or

ABL Object-oriented ABL
Issue Number: OE00202453
     Ambiguous OO method call in chain fails

The AVM might not run the correct overloading of a method if the method is
called as part of a chain of references with 3 or more elements and the
overloading resolution was deferred by the compiler until run time.  In
this case, the AVM currently chooses the first overloading in the source
file. So, if the first overloading happens to be the one that is intended,
the call will work. The method call can be ambiguous at compile time for
any of the reasons that make method calls ambiguous: one or more arguments
provided by DYNAMIC-FUNCTION/DYNAMIC-INVOKE, temp-table/ProDataSet
parameters, array parameters, etc.

This incorrect run-time resolution leads to one of the following outcomes:

    o  The error, "Mismatched number of parameters passed to routine
<name>. (3234)," might be raised (this seems to be most common).
    o  The session might crash without further error.
    o  An error might be raised that parameters cannot be pushed onto the
    o  The correct method might execute because, by coincidence, the AVM
chose the intended overloading.
    o  The wrong method might execute, but not raise an error because it
does not use the arguments it receives in a way that would cause an error.
So, the outcome of the call might not be what the developer intended.

ABL Printer
Issue Number: OE00199898
     Can't access printer properties when printer name is non-ASCII

You may not be able to display a printer's properties in the SYSTEM-DIALOG
PRINTER-SETUP dialog box if the printer's name has non-ASCII characters.
You may also be unable to print to the printer using OUTPUT TO PRINTER {

ABL Web Services client
Issue Number: OE00216544
     WSDL Analyzer crashes when parsing WSDL document

The WSDL Analyzer crashes when parsing a specific WSDL document

Adapter for Sonic ESB
Issue Number: OE00209680
     StopReceiveMessages should be disallowed in messageHandler proc

StopReceiveMessages in messageHandler procedure causes messages to get
lost or session hang depending on coding so should get discouraged

Issue Number: OE00215955
     Session-Managed Native ESB Adapter causes AppServer exception

The Session-Managed Native ESB Adapter causes an unhandled exception in
the AppServer Broker if the combined length of the connection string
(composed of  a user-id, password, and information fields) exceeds 30,000
non-Unicode characters when connecting to an AppServer.

Adapter for SonicMQ
Issue Number: OE00214258
     ABL client hangs on RH Linux when using -SMQConnect

ABL client hangs on RH Linux when using -SMQConnect on Sending DATA
message  to the client

Issue Number: OE00214691
     CTRL-BREAK on alert-box does not raise STOP condition

CTRL-BREAK on an alert-box does not raise a STOP condition if the
alert-box is not parented to a visible window.

Adapter for SonicMQ Broker Connect
Issue Number: OE00220803
     SonicMQ Adapter fails to respond due to NullPointerException

Occasionally the SonicMQ Adapter (BrokerConnect) fails to respond with the
correct status due to NullPointerException in the AdminServer

ADE Tools and Runtime
Issue Number: OE00199732
     bproxsdto4gl utility not parsing XSD due to annotation limit

Error 13102 occurs when parsing an XSD file with bproxsdto4gl which has
many annotations.

Issue Number: OE00208930
     AppBuilder loses internal procedure code with mixed web/gui file

AppBuilder loses code in some internal procedures when it saves a
procedure. This happens when the code version is WDT_V2*, in this case
&ANALYZE-SUSPEND _VERSION-NUMBER WDT_v2r12 and the procedure &analyze
header has a 5th token that is pointing to a window as follows:
The code that manages this version of WebSpeed code do not expect a window
reference as the 5th element in the &analyze header and looks for a
corresponding template and ends up using the empty procedure template when
no matching template is found.

Issue Number: OE00215520
     Translation Manager can fail for long strings with UTF-8

If using Translation Manager with -cpinternal UTF-8, translations might
not be found for strings that contain non-ASCII characters and are longer
than 63 characters.

To work around this problem, you can run the following code against an
already-loaded translation database:
FOR each XL_String_info:
    XL_String_info.KEYOFSTRING =
SUBSTRING(RIGHT-TRIM(XL_String_Info.original_string, " "),1,63).
To revert the strings back to what they were originally, run the
FOR each XL_String_info:
    XL_String_info.KEYOFSTRING =
SUBSTRING(RIGHT-TRIM(XL_String_Info.original_string, "

Issue Number: OE00216212
     Error 6491 with resized section editor

Resizing the section editor may result in error 6491 when the editor is
redisplayed after running code in the AppBuilder.

Issue Number: OE00216950
     logical fld initial val other than ?/yes/no causes err 87 w/MSSQ

If the logical field's initial value is other than "?", or "Yes" or "no"
on the Schema holder, the interactive .d load on the foreign data source
(in this case MS SQL Server), causes error 87.


**Input value: male should be yes/no. (87)

The error seems to be harmless as if the .d contains records, it loads
fine.  This is a regression bug.  Using "Acceptable Error Percentage: 100"
on the .d load screen does not suppress this error.

Issue Number: OE00217008
     MSSQL DS Delta sql utility gives error 138

MS SQL DataServer Delta sql utility gives error 138 with specific sets of
options selected on the "Delta df to MS SQL Server Conversion" screen.

Error Message:

**df-info record not on file. (138)

Issue Number: OE00217212
     MSSDS Delta.sql util creates bad sql and date maps to decimal

Data Administrator > DataServer > MS SQL Server DataServer > Schema
Migration Tools > Generate Delta.sql OpenEdge to MSS... creates bad sql
for extent fields and also OE date maps to sql decimal data type on the
.sql file it generates.

there are 3 issues with the delta.sql utility:

1. Decimal data type missing precision and closing parenthesis is not
there - perhaps, because the OE date is being translated to decimal is the
reason.  Need more research by development.

2. Date data type is being translated to Decimal

3. For null capable field, "NULL" keyword is missing from the Delta.sql
generated .sql file.  On the other hand, protoMSS generated .sql shows
"NULL" keyword.  So consistency is missing from Delta.sql utility
generated .sql file

Issue Number: OE00218312
     Errors with pass-thru link after upgrade to 10.2B

After upgrading from 9.1E to 10.2B and running a SmartContainer with a
pass-thru link to an SDO, the following errors may be returned:

User-defined function 'rowAvailable' invoked  dynamically but could not be
found. (5639)
BUFFER-FIELD OpenOnInit was not found in buffer ADMProps. (7351)

Issue Number: OE00218549
     SmartBrowse not showing all data

A SmartBrowse loses its scroll bar making the user unable to scroll up to
previous rows.

Issue Number: OE00207778
     Infrequent error 8025 when trying to run config procedure

If you set the srvrExecutionTimeLimit property for an AppServer, you may
experience error 8025 for any of the connect, disconnect, activate,
deactivate, shutdown procedures if the agent has been idle for more time
than the value specified in the propery.

<proc-name> procedure ended with an ERROR condition. (8025)

Issue Number: OE00214625
     Create startup switch to enable consumer side Actional in AppSvr

A switch for the AppServer is required to enable consumer side reporting
when the provider side is disabled.

Issue Number: OE00217061
     GLOBAL SHARED TEMP-TABLE in PERSISTENT procedure crashes AppServ

If a State-Reset AppServer Connect Procedure runs a PERSISTENT procedure
that defines a NEW GLOBAL SHARED TEMP-TABLE, the DBI file keeps growing
causing the eventual Appserver process to crash with the error:

SYSTEM ERROR: Attempt to define too many indexes for area 6 database
DBI3112a03672. (40)

Issue Number: OE00217426
     Provide Actional Business Process Support in OE 10.2B

Provide Actional Business Process at Service / Operation level Support in
OE 10.2B

Issue Number: OE00217550
     State reset agent remains in a connecting state

Occasionally agents of the state-reset Appserver get stuck in a CONNECTING

Issue Number: OE00218046
     Actional-enabled AppServer crashes using multilevel datasets

When a multilevel dataset is filled with more than one record at the
second level, {actional/instrument.i} bails out without any error message
in the Server log file but with a client message indicating that the
AppServer agent has died.
The crash occurs when ABL instrumentation (actional/instrumentation.i) and
database monitoring are enabled at the same time.

Issue Number: OE00218115
     Async requests to shut down AppServer crashes client.

Client crashes after running an asynchrounous procedure on state-free
AppServer. This occurs when running the remote procedure after a
connection loss with the broker.

Issue Number: OE00220588
     Stateless AppServer agents remain running when Broker is stopped

Stateless AppServer agents remain running when Broker is stopped, if the
AppServer runs a startup procedure that has global temp-tables.

AppServer Internet Adapter
Issue Number: OE00217226
     AIA Basic Authentication Fails

When using AIA to connect to Tomcat via the IIS Tomcat Adapter and using
userid@password in the connection URL to do basic authentication to the
web server then authentication will always fail because we wrongly base64
encode the password.

Issue Number: OE00195674
     10.2B documentation contains decommitted auditing content

OpenEdge 10.2B documentation contains decommitted auditing content such as
backup and restore events. These entries should have been pulled from the

Issue Number: OE00218114
     Locks being applied to _db table when deleting _aud-audit-data r

When _aud-audit-data records are being deleted an intent exclusive lock
and an exclusive-lock are being applied to the _db table.

Issue Number: OE00197090
     Message 6760 only written to screen when restoring a backup

Message 6760 (date and time stamp of when the database backup was taken)
is only written to the screen when the database is restored. This
information is missing from the database log file.

Issue Number: OE00197745
     Error 13926 is not written to the database log file

Creation of this extent would exceed the maximum number of blocks for area
<area-name> (13926) is not written to the database log file when a DBA
attempts to add an extent to an area and the extent add failed as it would
exceed area limits.

Issue Number: OE00198292
     Connections to Remote DBs are logged in already conn DBs

When you are conneted to a database via Client Server, any future
connections via remote connections will be logged in any Client Server
connected databases .lg file

Issue Number: OE00200143
     Aiarchiver fails to start if space in db directory path

If the database path contains a space and the database is started via the
AdminServer by means of using dbman, Progress Explorer, OpenEdge Explorer
or OpenEdge Management then the AI Archiver daemon will fail to start.

Issue Number: OE00206289
     Error 6711 during db backup using custom made collation table

Performing offline backup using code page startup parameters fails with
error 6711.

Issue Number: OE00206925
     (9871) The DB Service rocket cannot be started at this time

The following messages were seen once by a user attempting to start their
(-----) Attempt to unlock DB service manager object for 0, PID 0.
(9871) The DB Service rocket cannot be started at this time.
(-----) Removed shared memory with segment_id: 32784
(334) Multi-user session end.

Issue Number: OE00208080
     Incremental.df dumps tables with SQL constraints

The Data Administration tool "Dump Data Definitions -> Create an
incremental .df" option includes in the .df file any table that has a SQL
constraint. When a table is dumped and loaded from the Data Administration
tool, SQL constraints will be lost.

Issue Number: OE00210040
     Interactive connections count does not decrease in .lic file

Interactive connections count in columns 7 8 9 in the database .lic file
and _lic VST does not decrease when secondary login brokers are being used

Issue Number: OE00211158
     AI Archiver reports insufficient space when there is space

If ai file is physically greater than archive location (regardless of how
much data is in the AI file) then the AI archiver incorrectly reports
there will not be sufficient space to archive the file.

Issue Number: OE00216028
     AIMGT records aiseq when backup completes

AIMGT records aiseq when backup completes in the archiver.log file
This is not necessarily the aiseq that was switched to when backup
started, during the online backup it is entirely possible that +n ai
switches occur before the online probkup completes.
After restoring backup, roll forward fails for the aiseq listed in the
archiver.log file backup record.

Issue Number: OE00216908
     Prorest a db in version 11.0 that was backed up in 10.2B

Prorest a db in version 11.0 that was backed up in 10.2B should report

Issue Number: OE00217005
     dbtool keeps giving the same err and fixes

When running the dbtool with the same option multiple times, it keeps
giving the same errors and fixes.
Steps for menu selection:

1. dbtool trend
2. Option 2 (SQL Width Scan w/Fix Option
3. 0 for single user connection
4. 5 for % padding
5. all for table
6. all for area
7. 4 for "display" verbose level

Issue Number: OE00217158
     Replication server blocked on private latch causing db to stall

Replication server can get blocked on private latch in pmObjectLockLock()
when more than 1 remote SQL user is connected to a SQL92 remote server.

Issue Number: OE00217558
     Database broker (_mprosrv) is ignoring TZ settings on Windows

Despite the TZ settings on Windows, the database broker does not display
time correctly in database log file.

Issue Number: OE00218667
     NO-LOCK query using multiple index hangs in Client/Server

A query using multiple indexes hangs with NO-LOCK and crashes with
SHARE-LOCK/Exclusive-Lock when run in Client/Server.
The same query runs without issue when run self-service or single user.

Issue Number: OE00219209
     dbtool truncates sql-width of extent fields

dbtool is truncating the sql-width of extent fields if the arrayWidth

Issue Number: OE00219685
     When copying a full ai extent manually the session crashes

_dbutil crashes when running rfutil aiarchive extent

Database Database Utilities
Issue Number: OE00220290
     AI Archiver gets enabled without AI subsystem being on

In case where enabling AI and AI archiver using online backup and typo's
been made pointing an ai archiving parameter to a non existent folder, the
AI enablement will fail, but AI manager will be enabled.

Database Failover Clusters
Issue Number: OE00198632
     OE clusters failing on Win 2008 R2

OpenEdge does not support clusters on Win 2008 R2

Database RDBMS
Issue Number: OE00215431
     OE Replication source DB may hang due to a deadlock on target DB

Source database running OE Replication might hang due to a deadlock
condition (naping and waiting for a latch) involving the replication

Issue Number: OE00215538
     Poll timeout of 0 causes excessive CPU usage with remote clients

When a server is processing many remote clients with entries in the
suspension queue, the activity on poll with a timeout of 0 becomes
excessive taking over all system CPU.

This is the current architecure of processing the suspension queue but it
does not scale, with large number of remote clients on AIX 7 series

Issue Number: OE00216627
     Remote clients not cleaned up after terminated _mprosrv process

Remote clients are not cleaned up after if an _mprosrv process terminated
due to a fatal error.

Issue Number: OE00217510
     Transaction backout fails with error 289

Transaction backout fails with error 289 bringing the database down

Issue Number: OE00175173
     Remote Oracle Dataserver connection hangs

A remote connection to an Oracle Dataserver hangs and is never

Issue Number: OE00199039
     Error 1101 and session death with MSS DataServer

When updating a record with > 32K of data via the DataServer for MS SQL
Server, it is possible for the session to generate error 1101 and

Issue Number: OE00204215
     Precision wrong for dec. fld with utf-8 w/ width selected for ex

protoMSS process is failing when utf data type and width is selected using
utf-8 client is connected to utf-8 schema holder.  The reason for failing
is because the precision of the decimal field is lower than the decimal

Issue Number: OE00210237
     Precision wrong for decimal extents when migrating schema

The precision is wrong for decimal extents when migrating schema from
OpenEdge to MS SQL Server and "Width" is selected.

Issue Number: OE00215712
     Application crashes without -znoposirc switch

Application could not be recompiled into version 11.0 without crashing if
the znoposirc switch was not turned on.

The "-znoposirc" switch is for backward compatibility and has the effect
of disabling the position-independent r-code feature developed in version
11.0 for the explicit purpose of decoupling column position on the server
from field position in r-code for customers' deployment requirements.

If the position-independent r-code feature will not work with the customer
application then the task that this feature set out to provide is not
working.  This is an 11.0 regression.

Issue Number: OE00216633
     protoMSS changes the field name and r-pos causes .d load err 87

protoMSS changes the field name "_userid" on the OE DB to "userid_" on
Schema Holder and change r-pos which causes .d load to fail with error 87.
This change of field name also causes the existing application fail to

Issue Number: OE00216717
     Table definiton incorrect after warning raised during pro-to-ora

Warning during pro-to-ora could leave the dataserver schema table
definition as follows:

- No description or dump name
- fields and table names are uppercased
- labels and initial values are incorrect
- datetime field is converted into 2 fields

Issue Number: OE00217275
     Err 3199 migrating OE db to MS SQL using protoMSS w/unicode opti

Error 3199 migrating OE db to MS SQL using protoMSS with "Use Unicode
Type" option selected. This error only occurs when the Data
Administration is directly spawn from Start > All programs > OpenEdge >
Data Administration

Error text:

Could not extract database name in CREATE DATABASE statement. (3199)

Issue Number: OE00217435
     Running FIND/GET CURRENT against OE11 Oracle DSRV crashes client

When using OE11 client against OE11 DataServer for Oracle schema holder,
running r-code that contains the statement FIND CURRENT or GET CURRENT
causes client session to crash.

Issue Number: OE00217439
     Running FIND/GET CURRENT against OE11 MSS DSRV crashes client

Running r-code that contains a FIND CURRENT or GET CURRENT statement while
connected to a DataServer for MS SQL Server schema holder causes the
client session to crash.

Issue Number: OE00217693
     Crash connecting w. full system name in -H to MSS Unified Broker

Client crashes when connecting to MSS database with Unified Broker via
NameServer if -H contains full system name. For example:

prowin32 -db schemaholder-1 -db sqlodbc -ld sports2000 -H -S 5162 -dt MSS -U uid -P pwd -Dsrv
svub,1 -DataService mssbroker1

Issue Number: OE00218763
     MS SQL DS -ABL MATCHES does not work to find tilde

ABL MATCHES fails to find tilde using '*~~~~*' in the WHERE Clause when
run against MS SQL Server DataServer.

Issue Number: OE00218913
     Err 6182 loading .d to MSS DB after dbtool sql-width fix migrate

Loading data to MS SQL server database through dictionary load utility
from Data Administration causes error 6182 on some tables even after
running dbtool to adjust sql-width to 100% padding and then migrated to MS
SQL Server using protoMSS using SQL width migration option.

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.

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: OE00217893
     Errors 6182 and 2651 querying NVARCHAR field in MSS DataServer

Errors 6182 and 2651 occur when querying NVARCHAR field and value used in
the ABL WHERE clauses exceeds the max-width of the field in MSS:

"You tried to compare or to update a character field with a value longer
than the maximum length. (6182)
Field num: 3, value: 1234567890123456789012345678901234567890. (2651)

Issue Number: OE00218303
     Changing width from x(8) to x(30) in SQL Server ignored

If you uncheck change width from x(8) to x(30) option in migration
windows, it is ignored & still changed to 30.

DataServers Oracle
Issue Number: OE00214717
     AppServer has abnormal shutdown when reading field in Oracle

AppServer agent shuts down abnormally with error "SYSTEM ERROR: Foreign
database cursor 1 not found(1471)", when accessing a DataServer table in a
persistent procedure that was started by a previous client connection.

Issue Number: OE00213419
     Debugger ignores breakpoints in ROW-DISPLAY trigger

The debugger (both the Progress Developer Studio and StandAlone versions) will skip
over breakpoints set in a browse's ROW-DISPLAY trigger.

Issue Number: OE00199233
     PROUTIL idxactivate supported for source database

The PROUTIL idxactivate utility is now listed in the OpenEdge Replication
User Guide as supported for a Replication-enabled source database (and as
unsupported for a Replication-enabled target database).

Issue Number: OE00199632
     DSRUTIL Monitor Utility Startup Menu Agents connected total

If you select Replication server status from the Startup Menu of the
DSRUTIL Monitor Utility, the OpenEdge Replication Monitor screen appears.
The Agents connected field shows the number of remote agents currently
connected to the server. Note that since the database is not going through
recovery, the number of Agents connected indicated under Recovery
information is correctly reflected as zero.

Issue Number: OE00221391
     Replication documentation refers to wrong properties file

The OpenEdge Replication User Guide for Version 11.1 has been updated to
reflect the fact that the transition-timeout parameter is configured in
the OpenEdge Replication server properties file (
not the agent properties file (

Graphical User Interface
Issue Number: OE00166837
     Hot keys on extended characters do not work with UTF-8 client

Hot keys (Alt-key mnemonics) for extended characters defined with '&' in
the label do not work with the Windows GUI client when -cpinternal is set
to UTF-8.

Issue Number: OE00184260
     New row added in SmartDataBrowser is not highlighted

When an Add operation is initiated from an UpdateSmartPanel linked to a
SmartDataBrowser, and the newly added row is exited with the tab key, the
new row is added to the end of the browse and has focus, but it is not
highlighted. This behavior is new in 10.2A; in previous versions, the
newly added row is highlighted, but it does not have focus. There is also
an OFF-END event fired in the browse after the new record is addded to the
end of the browse that was not fired in previous versions.

Issue Number: OE00215770
     Drop-down list-item-pairs combo-box missing screen value

A drop-down list-item-pairs combo-box will return an unknown screen-value
and input-value if the value entered in the fill-in portion does not match
one of the labels in a label/value pair.

Issue Number: OE00216948
     loading delta.df generates errors 23 and 10381

loading delta.df generates errors 23 and 10381

Issue Number: OE00218000
     Mouse cursor stays 'busy' if ActiveX doesn't have class cursor

If the mouse cursor is positioned over an ActiveX control while
SESSION:SET-WAIT-STATE("") is called to clear an active wait state, the
cursor may get stuck in the "busy" state until the mouse is moved away
from the control.
The client does become responsive again, even if the cursor indicates

This happens when the ActiveX control does not have a class cursor

Issue Number: OE00219967
     Session crashes when closing a dialog window without focus

The session crashes when a dialog window without enabled widgets and which
doesn't have the focus is closed with the windows X button, and ON 'LEAVE'
ANYWHERE and ON 'ENTRY' ANYWHERE triggers are in effect.

Issue Number: OE00219981
     Focus is placed into wrong window after closing a dialog box

When a dialog box belonging to one window is dismissed, focus may
incorrectly be moved to another unrelated window which had previously
displayed a dialog box.

Graphical User Interface ABL
Issue Number: OE00149494
     Child window fails to display after parent window is maximized

If a window is minimized and then is restored by right-clicking on its
button on the taskbar and selecting "Maximize", attempting to display a
new child window (a child of the maximized window) may appear to have no

Issue Number: OE00215199
     Silent Installation hang on the SendMessage() call on cluster ex

Intermittently, Silent installation hang on a SendMessage() call that
installation is making because it found the Cluster executable.

Installation Service Pack
Issue Number: OE00216568
     Adminserver not stopped by silent SP install

Adminserver not stopped by silent SP install

Issue Number: OE00216207
     OEM/OEE sets configuration to TRUE on error

If changes are made to the database configuration properties through
OEM/OEE and an invalid value is entered, the following message appears
"Invalid value for <PROPERTYNAME> property. ..."
On clicking Ok, all properties that have a 'checkbox' are then checked, ie
enabled, which will cause undesired behaviour on subsequent restart of the

Issue Number: OE00216367
     Using IE9 an unmanaged database connection cannot be created

Using IE9 an unmanaged database connection cannot be created

Issue Number: OE00216674
     Create button for a new database domain is greyed out in OEM

Unable to create a new database domain under OE Management/Explorer using
data adminstration as the button is always greyed out.

Issue Number: OE00216837
     OEM Jobs stop executing after 5 years of the start date.

OpenEdge Management jobs stop running 5 years after the time they were

Issue Number: OE00217915
     fmconfig -enable fails on HP-UX

The fmconfig -enable command fails on HPUX with the following errors:

ERROR: Remote monitoring is not supported with this version of JAVA:
ERROR: Remote monitoring on this platform requires a newer version of
JAVA:  HP-UX 1.5.0

Issue Number: OE00217948
     OE Mgt send false alerts when Userid and Password are required.

Monitoring an URL from OpenEdge Management when that uses the HTTPOnly
flag on cookies will fail with an alert.

Issue Number: OE00219163
     AdminServer crahes when using remote scripted db migrated 10.1A

OpenEdge Management stops responding/AdminServers crash after using
Storage Area View of a scripted database (migrated from 101a) running on a
remote server and remote monitoring is also enabled for that server.

Issue Number: OE00220558
     OE Management reporting many errors regarding vst for trend db

OpenEdge Management is reporting many Data storage errors in the
admserv.log file on startup associated with recGetValues for fields in the

Management Management
Issue Number: OE00216349
     OEM/Adminserver may coredump when monitoring filesystems

OE Management / Adminserver may coredump in osmetrics.dll when trying to
poll a filesystem where the name of the mount point is too long.

Message Number Change
Issue Number: OE00218061
     Errors 8845 and 9149 when registering database on AdminServer

When registering multiple databases with AdminServer using a batch script
causes Errors 8845 and 9149 for some databases

Name Server
Issue Number: OE00215500
     Nameserver shuts down due to closed socket

NameServer is sporadically shutting down with multiple errors 9362/9411
and 9412

Open Client
Issue Number: OE00212160
     Java Open Client SSL AIA Connection Fails With 7203 Error

Java program that makes an SSL AIA connection to the AppServer will fail
with error 7203 in 10.1C and later.

Issue Number: OE00215247
     .NET SSL client faile to connect to AppServer via OpenClient

.NET SSL client faile to connect to AppServer via OpenClient

Issue Number: OE00216870
     A way to add keep-alive settings to the connection

Have a way to add keep-alive settings "KeepAliveInterval, KeepAliveTime,
and TcpMaxDataRetransmission"  parameteres to the connection to avoid
timeout in a .NET client/server application.

Open Client .NET
Issue Number: OE00216895
     .NET Open Client Empty String Init Value Becomes DBNull

When passing back a temp-table from the AppServer to a .NET Open Client
where a CHAR field in the temp-table is defined with an initial value of
"" (empty string), we appear to see the data for the field on the .NET
side as String.Empty but upon creating new records in the temp-table, the
fields value becomes DBNull.  This is because the .DefaultValue property
for the field is wrongly set to DBNull.  It should be String.Empty.

Open Client Java
Issue Number: OE00171680
     Index info lost when retrieving ProDataSet with Java OpenClient

When exchanging a ProDataSet with the Java Open Client, indexe info is
ignored by the Java OpenClient.

Progress Developer Studio for OpenEdge
Issue Number: OE00203760
     HelpButtonClicked Event Subscription deleted when changing code

Modifying code in the PDS Editor after manually entering the method
associated with the HelpButtonClicked event wipes out the subscription to
the event.

Issue Number: OE00207103
     Error while creating Project in different location

Getting UI error while creating project in different location.

Issue Number: OE00210611
     New file wizard of Editor template should take any ABL file extn

New File Wizard created using Editor Template of Customization Editor in
Progress Developer Studio for OpenEdge only accepts the
extension .p

Issue Number: OE00212477
     Program with many include files references exhausts memory

A program that has a large number of references to the same include file
can cause the Progress Developer Studio to consume very large amounts of memory,
to the point where the tool becomes unstable.

Issue Number: OE00213685
     Procedures/ABL code components are not displayed in outline view

Procedures/ABL code components are not displayed in outline view if an
include file reference contains quotes within quotes even though the
nested quotes are for a preprocessor reference or another nested include

Issue Number: OE00215638
     Cannot open multiple files in the same instance of Progress Developer Studio

If right clicking on a file to open it in Progress Developer Studio for OpenEdge, this always
tries to start a new instance of the Progress Developer Studio.  If there is already an
instance running then it is not possible to open the file using the same
instance and workspace.  If you try this results in:

"Workspace in use or cannot be created, choose a different one."

This is an enhacement to include this functionality in the product.

Issue Number: OE00216297
     Automatically Check Syntax can trigger excess compiles

The Automatic syntax check goes into looping behavior when the Project AVM
takes more time to perform  syntax check. The moment the project AVM fails
to perform syntax check, another request for syntax check is done though
there is no change in file. this loop continues till syntax check is
performed correctly, project AVM is able to do syntax check in lesser

Issue Number: OE00216342
     PDSOE does not auto fill Serial No. field in Report Tech Issue

The "Customer Information" preference page in Progress Developer Studio
for OpenEdge does not auto fill the "Serial No." field.  Both the Product
and Version information is auto filled, but not the Serial No.

Issue Number: OE00217091
     PDS Unexpected compile-time error when using READ-ONLY property

Accessing a read-only property of a class that is used as a parameter to
the ENTRY function, such as:

entry(3, myvar,Delimiter:Level1)  = "A" .

raises error 13824:

Cannot update Level1 because it is a property that is read-only. (13824)

Issue Number: OE00217210
     Intellisense May Not Work with Some Include Files

When a class file contains an include file reference it is possible that
Intellisense will not show any of the class specific properties and

Issue Number: OE00217238
     PDS property dialog hangs on saving the form.

In Progress Developer Studio for OpenEdge, after accessing a property of a form using the
PropertyDialog (and pressing either OK or Cancel), when you subsequently
try to save the changes to the form, PDS hangs.

Issue Number: OE00217644
     Error 4348 running OE dev studio debugger with OE10.2B AVM

Running the OpenEdge developer studio Debugger with an associated
OpenEdge10.2B AVM results in error 4348 and the debugger is terminated.
Running the application from within OE11 with an associated 10.2B AVM
causes no problem, only debugging fails.

Issue Number: OE00217792
     Error 1008 when using Test Connection in PDS with MSSDSRV

create a Database Connection in Progress Developer Studio for OE to
MS SQL Server using the DataServer for MS SQL Server. on the edit dialog
of connection profile, clicking on "Test Connection" returns a error
dialog (error 1008). which means the logical name provided by the user is
not recognized by the MSS data server.

<program name> non-PROGRESS database <name> unknown. (1008)

on clicking "test connection" multiple times displays another error
dialog(error 1012).

Connection failed.
** Warning -- database sports2000~oe is already connected. (1012)

this suggest that sports2000~oe connection is already established and we
are trying to connect it again.

Issue Number: OE00219005
     .esboe files not being generated

When user select "Generate Sonic ESB Invocation Files" in Progress Developer Studio and
the Preprocessing button is not enabled, then the .esboe files will not
get generated and no errors will be given. but when Preprocessing is
enabled, .esboe files get generated properly.

Issue Number: OE00220157 missing after enabling Dynamics to OE project

Error marker is shown for file after enabling dynamics for an
OE project. Also observed that the file is not present in
$DLC\gui folder.

Issue Number: OE00220404
     Double-Click on Word in Progress Developer Studio Sometimes Doesn't Take

Double-Click on Word in Progress Developer Studio Sometimes Doesn't Take

Progress Developer Studio for OpenEdge DB Navigator
Issue Number: OE00203866
     Remote DS connection fails with error 560 from Progress Developer Studio

Progress Developer Studio for OpenEdge DB Navigator give error 560 when connecting the remote
dataserver for connecting to foreign Database (SQL, Oracle). This Error is
only shown in the case when user uses -Dsrv svub,1 in other parameters to
connect to Remote dataserver.

Progress Developer Studio for OpenEdge Editing
Issue Number: OE00163724
     Some events not cased in Progress Developer Studio editor

The auto-case on typing is not working for MOUSE events.These mouse event
keywords are not even color coded when we type them in editor which might
be the reason why they are not cased.This is because these events are not
part of the keyword list that PDS maintains.

these are the list of mouse events for which color coding and auto casing
do not work.


OpenEdge GUI for .NET
Issue Number: OE00198881
     WAIT-FOR event PAUSE n does not work with .Net

The WAIT-FOR <event> PAUSE <n> statement does not work correctly if there
is already a .NET WAIT-FOR executing (WAIT-FOR <.NET method>). The
WAIT-FOR PAUSE will not time out until an event such as a mouse event or
keyboard event occurs.

Issue Number: OE00200101
     MouseDoubleClick event on UltraTree node does not restore window

Setting an ABL window's WINDOW-STATE attribute to 3 (WINDOW-NORMAL) in a
MouseDoubleClick event trigger on an UltraTree node does not restore the
window; the KeyUp event does restore the window.

Issue Number: OE00201947
     Error when calling a static method in a CALC field in a browser

When a calculated field expression in a browser calls a static method, you
get this error:

In order to use this WAIT-FOR format (WAIT-FOR x:y), you must specify an
input-blocking method of a .NET object. (13968)

Replacing the static method with a (local) function and using the static
method in this function solves the problem.

Issue Number: OE00204235
     Executing WAIT-FOR Application:Run twice breaks menu shortcut ke

When WAIT-FOR System.Windows.Forms.Application:Run:() is executed two
times and the form contains a menu option with a shortcut key, this
shortcut breaks on the second run.

Issue Number: OE00206290
     updasmref.exe fails on 64-bit Windows

On Windows 7 64-bit, the updasmref.exe tool will fail to load an
assemblies.xml, and will raise the exception
"System.BadImageFormatException: An attempt was made to load a program
with an incorrect format. (Exception from HRESULT: 0x8007000B)"

From within Progress Developer Studio, this is observed when selecting "OpenEdge
-> Migration -> Update Assembly References".

Issue Number: OE00206328
     .NET WAIT-FOR fails to resolve chained properties and methods

At runtime a .NET wait-for will fail if it contains a chained reference,
and the chain includes properties or methods.
For example:
"WAIT-FOR classref:ChainsToDialog:showdialog()." fails if "ChainsToDialog"
is a class property.

Depending on what class types are included in the chain, one of the
following errors will occur:
- In order to use this WAIT-FOR format (WAIT-FOR x:y), you must specify an
input-blocking method of a .NET object.  (13968)
- System.ArgumentException: You can only call ShowDialog as part of a
Wait-For statement. (15574)

Issue Number: OE00209878
     UltraGrid crashes sometimes when repopulating DataSet

This problem is seen when you have an UltraGrid bound to a
ProBindingSource attached to a ProDataSet. If you set the
ProBindingSource:Handle to Unknown before you repopulate the DataSet's
query, the UltraGrid may crash.

Issue Number: OE00213382
     System.ObjectDisposedException closing form with UltraTimelineVi

Error "System.ObjectDisposedException: Cannot access a disposed object."
occurs when closing a form containing an UltraTimelineView control whose
CalendarInfo property references an UltraCalendarInfo control.

Issue Number: OE00216068
     Session crashes closing .NET form after ABL dialog is displayed

If an ABL dialog box is displayed while a .NET form is visible and the
form is closed programmatically while the dialog is still displayed, the
session may crash.

Issue Number: OE00216074
     System exception closing .NET window

You get System.InvalidOperationException: Operation is not valid due to
the current state of the object when closing a .NET calendar window in
customer's application that contains Infragistic controls.

Issue Number: OE00216180
     DataGrids displaying with missing data

Changing the WHERE-STRING on then re-opening a dataset query when it's
attached to a bindingSource whose data are displayed in multiple
UltraGrids causes anomalous results such as disappearing data and missing

Issue Number: OE00216326
     UPDATE statement during WAIT-FOR may cause application to freeze

An application which displays a form and executes WAIT-FOR
Application:Run() may become unresponsive if the application subsequently
displays an ABL window which executes the UPDATE statement.

Issue Number: OE00216397
     UseFullFieldNames breaks compatbility from 10.2B04 to 10.2B05

In 10.2B05 we introduced the UseFullFieldNames property for the

When an ABL form with a ProBindingSource is saved under 10.2B05, in the
generated InitializeComponent( ) method, there is code to explicitly set
this property.
This means the code can no longer be used with earlier 10.2B service pack
releases, as the property did not exist there.

Issue Number: OE00216506
     Crashes related to CREATE QUERY or DELETE OBJECT (query handle)

There are random crashes when creating or deleting a QUERY widget.

Issue Number: OE00216564
     Query error when UltraGrid attempts to push updates to tt

The following query error sometimes appears when an ultraGrid attempts to
push updates back into the temp-table:

"Warning: A buffer in query contains a different record than the current
query result list entry. (4108)"

Issue Number: OE00217049
     Error 13016 when passing .NET class to a procedure

Error 13016 is raised incorrectly when r-code is run that passes a .NET
class as a parameter to a procedure.  For example:

Source class 'System.Object, mscorlib, Version=, Culture=neutral,
PublicKeyToken=b77a5c561934e089' is not compatible with target class
'System.Object, mscorlib, Version=, Culture=neutral,
PublicKeyToken=b77a5c561934e089' for parameter 'poSender'. (13016)

Issue Number: OE00217294
     Progress.Windows.Form prop names don't follow .NET convention

The new disposeDialogOnClose and previousState properties of the
Progress.Windows.Form class should have their names start with a capitol
letter, to adhere to .NET coding standards.

Issue Number: OE00217383
     Vis. Des. can't open control w/ event that has non-.NET param

If a user control has (or inherits) an event defined with an ABL-style
signature, and that signature includes a parameter that is not a .NET type
or a hybrid, the following error occurs when opening the Control in the
Visual Designer:
The invoked member is not supported before the type is created.

Issue Number: OE00218232
     Assigning bindingsource:handle multiple times triggers errors

A probindingsource that has it's handle property reset to a query handle
doesn't get reset properly.  As a result it can try to create multiple
copies of a record, where only 1 should be created.

Issue Number: OE00218339
     OE11 batch clients do not accept -assemblies parameter

OpenEdge 11.0 batch clients generate error 1610 when attempting to use the
-assemblies parameter:

-assemblies is not supported by this executable. (1610)

Issue Number: OE00219027
     Record not available after REPOSITION-TO-ROWID if bound to PBS

When a ProDataSet containing an empty temp-table is bound to a
ProBindingSource, a new record is created in the temp-table, the binding
source is synced either by reopening the query on the temp-table buffer or
by executing Query:CREATE-RESULT-LIST-ENTRY and
BindingSource:RefreshAll(), and the query cursor is positioned to the new
record with Query:REPOSITION-TO-ROWID, the new record is unavailable.

Issue Number: OE00219233
     Focus lost in embedded ABL window after displaying modal dialog

If a dialog box or alert box is displayed while focus is in an ABL window
which is embedded in a .NET form, focus will not return to the embedded
window when the dialog box or alert box is dismissed. Focus may go to a
.NET control in the form or focus may appear to be lost.

OpenEdge Replication
Issue Number: OE00209937
     Repl Agent crashes when connecting to a listener port

Replication agent crashes when there is an unintended connection to one of
the listener ports.

Issue Number: OE00217979
     OpenEdge Replication not propagating schema change

OpenEdge Replication did not propagate online schema change made to source
database, resulting in 450 and 3191 errors.

OpenEdge Replication Agent
Issue Number: OE00204109
     Replication transtion fails with -252 and -263 errors on Windows

OE Replication transition might fail with -252 and -263 errors when
performing a recovery backup during a transition. This could happen when
using (trying to backup) a "large" database.  This is a problem only on

Progress Developer Studio for OpenEdge
Issue Number: OE00218513
     PDS - Error updating Eclipse in OE 11.0

When choosing to update the Eclipse platform the following error appears:

An error occurred while configuring the installed items
session context was:(profile=PlatformProfile,
operand=null --> [R]toolingorg.eclipse.platform.ide.ini.win32.win32.x86
An error occurred while processing the JVM argument.
Invalid format for byte argument: 384m .

This happens because of the space after 384m in the -Xmx384 parameter in

Issue Number: OE00219749
     proDebugConfig can't make ABL form debug ready

When using the proDebugConfig command when an OE11 ABL Form (.NET) has
focus, this results in:

Cannot make process <PID> ready for debugging
The process is busy and cannot be interrupted

Progress Explorer
Issue Number: OE00211679
     root auth fails from remote host when running dbman query on RH6

Remote management of database that is on Redhat 6 using root user fails
authentication.  Though the problem was reported on RH6 it  can occur on
any Unix platform where password is NOT encoded in Unix's DES algorithm.
(Note: For Linux the problem can occur if password is NOT encoded in DES
or MD5)

ERROR: Unable to connect to AdminServer.
User authentication failed for user: root (DBMan014)

Report Builder
Issue Number: OE00212473
     _prlist.p shows wrong list ofprinters on windows 2008 citrix

The Report Builder _prlist.p utility procedure may return more printers
than expected when the session is run on a Windows 2008 Citrix server. The
extra printers belong to other users running on the same server.

Issue Number: OE00218418
     starting report engine prore32.exe fails

report engine prore32.exe fails with snbd12dm.dll not found error

Issue Number: OE00208257
     Specific BETWEEN predicate causes internal error in SQL ENGINE

A specific NOT BETWEEN predicate in the WHERE clause causes a query to
fail with the error:

"Encountered internal error in SQL ENGINE at 2598 in
Z:/vobs_sql/sql/src/rds/opt_anl1.cxx. Contact Progress Technical Support"

Issue Number: OE00208258
     The SQL scalar ROUND function fails with some rounding factors

The SQL scalar function ROUND fails with error "Overflow error (7485)" if
its rounding factor is zero or absent and returns wrong values if the
absolute value of its negative rounding factor is greater than or equal to
the number of digits in the decimal part of the number.

Issue Number: OE00209662
     INSERT 31 digit in DECIMAL(31,0) field cause Overflow error (748

Trying to INSERT a 31 digit number into a DECIMAL(31,0) field generates
the error:

"[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver][OPENEDGE]Overflow error (7485)"

Issue Number: OE00211339
     VIEW columns created with COALESCE function are case sensitive

SQL VIEW columns created with the COALESCE function are case sensitive
causing queries that are not aware of this fact to return wrong result
sets.  The COALESCE function is supposed to be a shorthand for the CASE
statement, yet, the SQL VIEW columns created with the CASE statement are
NOT case sensitive

Issue Number: OE00212197
     SQL query over views and containing multiple UNIONs crashes

Queries with a large number (approaching 30) of SELECTs over views
combined using UNION ALL crash with an internal error.

Issue Number: OE00212964
     'with (NO-LOCK)' parameter of an SQL query is not functionning

When using the 'with (NO-LOCK)' parameter in an SQL select query a lot of
database record locking still takes place, and often give the following
error messages:
Lock table is full. (7870)

Issue Number: OE00216073
     _SQLSRV2 crashes executing a query with multiple outer joins

_SQLSRV2 crashes executing a query with multiple outer joins (more than 39
left outer joins) in OpenEdge 10.2B .
Query worked previously in 10.1C04.

Issue Number: OE00217904
     NO EXISTS predicate in a view causes wrong result set in join

When a Query joining a view with another view or another table is
executed, it may return wrong result set and and bad column order if the
view was created using multiple WHERE clause predicates one or more of
which uses th SQL "NO EXISTS" predicate.

Issue Number: OE00218078
     SQL query does not return data due to constant field comparison

A query against a join of two views fails to return proper result set when
a constanct field(s) is involved in the definition of one of the vews.

Issue Number: OE00219253
     Updating a date array with PRO_ELEMENT can corrupt its data

Updating an array with PRO_ELEMENT can corrupt its data.
When PRO_ELEMENT function is accessing single array element, and if that
array element is NULL, then PRO_ELEMENT is returning NULL instead of ?.
Because of this, single array element access via PRO_ELEMENT function can
result in all other values becoming NULL as part of an UPDATE statement.

Issue Number: OE00213010
     crash while inserting empty string into char arrayas

SQL engine crashes, if an empty string is provided as a value to a column
of type CHAR array, and a word index is defined on this column.

SQL JDBC Drivers
Issue Number: OE00215555
     Index ORDINAL_POSITION is 0 querying index information via JDBC

Index ORDINAL_POSITION is 0 querying multi-part index information using
JDBC drivers in 10.1A01 thru 10.2B05

SQL Server
Issue Number: OE00200269
     Error in SQL ENGINE at 406 in /vobs_sql/sql/src/rds/opt_jfn1.cxx

The error: " [DataDirect][OpenEdge JDBC Driver][OpenEdge] Encountered
internal error in SQL ENGINE at 406 in /vobs_sql/sql/src/rds/opt_jfn1.cxx.
" is generated while executing SQL queries containing UNION on right side
of JOIN and an index is selected to retrieve rows from the UNION.

Issue Number: OE00171816
     Caesar-Code in PUB._SYSSEQAUTH for prolang\ger\empty4.db

For database that has German character set when using sequences.
the  fields _Grantee , _Seq-Owner and _Seq-Name are  Caesar Code encoded

Issue Number: OE00198305
     UPDATE STATISTICS degrades query performance in 10.2B01

Certain queries' performance may degrade when the table, column and index
statistics are updated.

Issue Number: OE00208270
     Different results when using 2 aggregates in a select statement

When using more than one aggregate functions in a SELECT statement with
sub-query in EXISTS clause, the results are wrong

Issue Number: OE00211602
     IN predicate & CASE statement do no work properly in WHERE claus

SQL queries that use the IN predicate and the CASE statement in the WHERE
clause may fail to return the correct result set.  Some of these queries
that worked properly in 10.0B stopped returning the correct result in
later versions.

Issue Number: OE00213343
     Query performance drop after upgrade  from 10.1B03 to 10.2B05

Performance of certain(details given below) queries drops dramatically
after upgrade  from 10.1B03 to 10.2B05

A query containing at least three table join statement which meets the
following criteria takes lot of time to execute.
- Tables with multi-component indexes in a database.
- One of the table's conditions in WHERE clause must skip one component of
some multi-component index and have conditions on other components (like
a,b,c,d are columns of tab1; ABCD index spans across a,b,c,d. Where
conditions must be a = <another table's column> and b = <another table's
column> and d = <another table's column>. Note that c is missing.
- All the conditions in WHERE clause are transitively related.

Issue Number: OE00215481
     SQL query  returns Server Error 1 if {NO REORDER} not used

If the query plan has SEMIJOIN project, SQL Server returns Error 1 while
evaluating the cost for SEMIJOIN project node in SQL Optimization. If {NO
REORDER} is used in SQL query, query plan doesn't have SEMIJOIN node and
query does not return an error.

Issue Number: OE00217412
     More than 13 "IN" in WHERE statement causes huge performance dro

When using WHERE IN statements in a complex SQL query for very large
tables (millions of rows) , if 13 or more IN values are present the
performance of the query execution drops. The time of execution goes from
a couple of seconds (with less than 13 IN) to 10+ minutes (when adding 13
or more IN).

If the same query is modified and the WHERE IN statement is replaced by
WHERE OR then you can add more than 13 values and the query executes in a
few seconds.

This problem can occur when one (or more) of the tables has associated
indexes which contain some index key values with  many, many duplicate
values and other index key values with many fewer key values. In other
words, this problem is related to skewed key value distribution.

Issue Number: OE00218222
     UPDATE ALL COLUMN STATISTICS on big table fails

UPDATE ALL COLUMN STATISTICS for big table fails with :

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error -1 (see
dsmret.h) in
SQL from subsystem DSM SERVICES function dsmRecordGet called from
scan_cursor on .SRTT_Temp_2 for . Save log for Progress technical support.

This problem BEHAVIOR occurred when a character column in a database table
contained many values larger than 3000 characters, and some of those large
values could not be correctly handled by UPDATE ALL COLUMN STATISTICS.
This incorrectly prevented UPDATE STATISTICS from completing.

Issue Number: OE00134946
     Combo box screen value is incorrect on end-error of frame

If you open and close a combo-box's list in a character client without
making a selection the combo-box's screen-value will be reset to the first
item in the list.

Issue Number: OE00219158
     Attempting to realize dynamic browse on a frame crashes session

Attempting to realize a dynamic browse on a frame defined without the SIZE
phrase generates error (2108) and the session crashes.

UI Controls
Issue Number: OE00218988
     UltraTree + KeyPreview=true results in unhandled .NET exception

If a .NET child form and it's parent form both have the KeyPreview=TRUE
property set and the child form contains an UltraTree control, closing the
child form from ( THIS-OBJECT:Close(). )  within a KeyPress event handler
in the child form will result in a "System.NullReferenceException: Object
reference not set to an instance of an object." being raised.

Web Services Adapter
Issue Number: OE00219368
     WSDL SOAP 1.1 generated by WSA is not compliant with XML 1.0

When the WSDL file generated during deployment by the Web Service Adapter
is validated with Apache CXF error 
"Attribute 'required' is not allowed to appear in element 'soap:header'"
is displayed.

If the WSDL file generated by the Proxygen is validated  with Apache CXF
no errors are displayed.

Web Services Client
Issue Number: OE00196502
     WSDL analyzer crashes or creates incomplete documentation.

When running the WSDL analyzer bprowsdldoc against a specific wsdl
document it either crashes or no documentation for the operations is

Issue Number: OE00217318
     WebClient crashes using -q and program in an as-needed component

WebClient will crash when using -q in the application startup parameters
and having programs in an as-needed component that has not yet been

Issue Number: OE00194419
     Addition of WebSpeed Messenger removes entries for WSA

The Webspeed Messenger product was added to an existing installation of
WSA product.
The addition of the messenger product removed all entries related to WSA.