Issues fixed in OpenEdge 13.1

AppBuilder trims procedure code

Incremental Dump writes Add Index statement for a new active index into the Offline_Section for phased load.

When importing schema from SQL Server DataServer, when a varchar(max) array field is encountered, it throws the below error 10885 that causes crashes when attempting to compile code referencing the field in question.

Cannot load (import) Audit policy event definitions programmatically

When using the Delta df to MS SQL Server Conversion tool in OpenEdge 12.8.11 with the Include Defaults option enabled, the generated SQL script omits DEFAULT constraints for INT64 fields.

Admin Server crashes randomly with “The error was triggered by the auth.dll module, which caused the JVM to terminate unexpectedly with the following exception: EXCEPTION_ACCESS_VIOLATION (0xc0000005).”

The ABL session crashes with error (4208) during REPOSITION-BACKWARDS(n) when using Oracle DataServer in C/S mode.

Oracle DataServer may return incorrect post-update CLOB content when applications access CLOB fields from the OLD BUFFER inside an ABL WRITE trigger.

An ABL WRITE trigger does not fire when a CLOB field is modified using the COPY-LOB statement with MSS DataServer.

MS SQL dataserver does not refresh the buffer within the same session when using the RECID function and the OE database is migrated with the “Try primary for RowId” option.

MSS DataServer may return incorrect post-update CLOB content when applications access CLOB fields from the OLD BUFFER inside an ABL WRITE trigger.

Using QUERY-TUNING (NO-JOIN-BY-SQLDB) crashes OpenEdge 12.8.8 prowin client when using OpenEdge DataServer for MSS SQL Server

Outdated 11.7 executable bundled in the 12.8 install's 117_dbutil directory

Online backup on the repl target crashed with “No return pbktbl in bmRemoveQAreaDbkey”

When aiarchiver setdir is run with -aiarcdircreate option, it creates the directory specified by  but returns error.

rfutil  -C aiarchiver setdir  -aiarcdircreate

An error occurred while trying to create one of the directories in . (13645)

This is now fixed so that it returns a success message:

The after-image management daemon has been notified about the new archive directory. (13208)

Threaded binary dump does not respond to control-c, it has been fixed so that a threaded binary dump will now respond to control-c.

When OpenEdge Replication is configured to use a service name (defined in /etc/services) in the replication properties file, the command:

dsrutil  -C validate

fails with the following error:

Unable to contact database '' on : for agent ''. (19461)

Changing TXE commit lock skip limit in ‘Adjust TXE Options’ menu of PROMON does not reflect in _Dbparams VST.

Deselecting the recommended component 'OpenEdge Explorer' during a custom OpenEdge 12.2.16 installation still installs and starts OpenEdge Explorer.

The OpenEdge 12.8.8 Client Networking 32-bit .msi installer installs the prox.dll in the wrong place.  After the installation the prox.dll is located in: “C:\Program Files (x86)\Common Files\Progress Software\11” But not the expected: “C:\Program Files (x86)\Common Files\Progress Software\12”

Visual C++ x64 Redistributable not updated by openedge update install.

OpenEdge installer is asking to install RDBMS license despite OE RDBMS Adv Enterprise license being present

Client-Networking 32-bit MSI install fails to access mscomctl.ocx

WARNING: ESAM Installation failed

--------------------------------------

The ESAM installation has failed. For more details, contact the administrator to review either the ESAM_Install_mm_dd_yyyy_hh_mm_ss.log or the OpenEdge_External_Security_Administration_Manager_Install_mm_dd_yyyy_hh_mm_ss.log. Both files are accessible at the following location: C:\Windows\System32\openedge.d\audit

However, when you click “OK”, the installation continues after the warning.

When a silent install is attempted, and the OE installer is for a machine type incompatible with the machine type of the machine on which the response.ini was generated, the messages returned do not indicate that the discrepancy exists.

When only PASOE license is installed, during installation installer asks for the internationalization settings, but then in the DLC/startup.pf the settings are not set.

OpenEdge Update Installer Does Not Update %DLC%\pdbfiles to Match Updated Binaries

Session may crash during PAUSE statement when running an ABL application with .NET windows if the procedure-complete event of an async request got processed prior to the PAUSE statement.

Client session may crash if you disconnect and reconnect to a PASOE or WebServices server while asynchronous requests are still pending and an asynchronous request has no event procedure defined.

READ-JSON fails to update the nested foreign key field of a ProDataSet child table if the child table values appear before the parent key value in the JSON input string, and there are no parent-fields-before or parent-fields-after for the data-relation between the parent and child.

If a VAR statement is encountered in the procedure’s Main block after a sub-compile block (PROCEDURE, FUNCTION, ON trigger, etc.) or DEFINE FRAME statement, the AVM issues error 20006: ‘The VAR statement must precede any executable statement within block contexts where it is allowed’ .

Quotes around command arguments used with OS-COMMAND statement are stripped when executed by PASOE Web Transport

Progress.Util.ResourceManager is unable to locate .resx files if they are located in a directory containing ASCII extended characters in the name of the directory.

Progress.Lang.Stop exceptions are not raised when using class property SET accessors combined with a single ASSIGN statement.

PROCESS EVENTS can hang if making asynchronous PASOE requests with -maxConnections parameter, and the number of outstanding asynchronous requests exceeds the -maxConnections value.

Error 683 when running a session compile of a program with a shared frame using -defuntrans startup parameter.

Interactive _progres can continue executing ABL code despite a fatal error message if pending frames needs to be flushed out to the current output device.

Incorrect behavior when using SESSION:NUMERIC-SEPARATOR on a Windows client started with -useOsLocale and a Windows locale configured to use a non-ASCII character (e.g. NBSP, a non-breaking space) as the digit grouping symbol.

Nested constructor calls with string literals will not appear in STRING-XREF output.

Invalid -0 result from ABL AGGREGATE statement when no records satisfy the query.

Quotes around command arguments used with OS-COMMAND statement are stripped when executed by a PASOE agent

Chained use of Safe Navigation Operator (?:) throws error 10068 when used on .NET objects.

Breakpoints in a procedure or class file aren’t honored if the file is recompiled during a debugging session. This issue also prevents the debugger from setting breakpoints in OEUnit tests.

The AVM may crash when a widget which has a pending event trigger is deleted before the trigger is executed.

When using PROLIB -[LibraryName] -pf [FileListName.lst] to build a library, file names are truncated at 132 bytes.

When using .NET OpenClient, if a PASOE request uses DO ON STOP in multiple locations, then a STOP condition shows in the log as being raised in the DO ON STOP block and not in the actual location where the stop was raised if in a nested call.

A client session can crash if a FRAME with SIDE-LABELS has fields with long labels.

A crash occurs when compiling a program that performs a BUFFER-COPY from one TEMP-TABLE defined LIKE a database table to another TEMP-TABLE defined LIKE the same database table.

This produces the following C stack in the generated protrace file (attached):

smBCmpWhen

smbufcpy

smstmt

smsem

cr_compile

crpsrch

crrun_entry

rninterpret

crrun_rcsv

rncmpile

A memory leak may occur if you set a property with an implementation via a chained expression where the property resides in the object instance that was returned via one of the expressions in the chain expression.

Values that begin with a dash were incorrectly rejected when used in a connect string, such as -SOAPEndpointPassword ‘-secret’;, resulting in error “You have not supplied a parameter for argument... (1403)”

Using the QUOTER() function with a low -s value (e.g. 50) can return error : Not enough space to add quotes to item. (10083)

A memory violation error can happen during the loading of the .df when trying to manage Progress.Lang.LockConflict.

Abbreviated widget properties generate a compile error with the require-full-keywords compiler option instead of warning

Assigning a LONGCHAR variable value to a buffer-field column-label can display garbled text.

Using ADD-INTERVAL to add 0 years to a date changes year when year is negative

Using a custom format (e.g. “29999”) in an editable browse cell can return wrong SCREEN-VALUE and INPUT-VALUE.

Accessing the root object directly for a ProDataGraph java open client may throw a NullPointerException.

Indeterminate arrays with constant initial values are initialized at runtime, when the array definition is encountered.  ABL that accesses a variable before the DEFINE VARIABLE statement will see the variable with an unknown EXTENT, ? .  For example, RUN proc  before DEFINE VARIABLE, where  proc appears after the definition and accesses the indeterminate array.

AGGREGATE statement with COUNT operation can sometimes read records even if there is no record selection needed.

The PASOE SOAP transport may crash during XML serialization when a SOAP operation returns a dataset response.

The displayed value of a disabled fill-in isn’t updated when the screen-value is changed to an empty string.

Application crashes occur when INNER-LINES reference outdated coordinates. This issue may be noticed during a combo-box dropdown action.

The Procedure Editor may display non-ASCII characters incorrectly when -cpinternal is set to a code page other than UTF-8.

The GUI client may crash when multi-byte characters are pasted in a fill-in whose format includes fill characters, such as “xxxx-xxxx-xxxx”.

The bprowsdldoc and CONNECT methods are not accepted when the UsingPolicy element (a component of the WS-Policy WSDL extension) is included within the WSDL.

The Windows client can crash when creating or assigning popup-menus.

The READ-JSON method on a TEMP-TABLE triggers a client crash reading an empty JSON array while inferring schema from the JSON string.

The AVM may crash when the loading of a large number of records is interrupted by pressing Ctrl-C.

The RANDOM() function generates a repeated sequence of values in a Kubernetes/Docker container, even when -rand 2 is used

OEM/OEE Agent Metrics show date/time values with an incorrect UTC offset.

A crash (Fatal Signal 11) could occur during ABL session shutdown when a trigger or procedure using a BUFFER parameter was cleaned up after the procedure that owned that buffer had been destroyed.

PASOE agent crashes when SOAP request to a 3rd party provider fails due to SSL errors

Using the ‘-connectionLifetime’ parameter to consume web services results in error 11773.

Progress Developer Studio for OpenEdge (PDSOE) crashes during startup and generates hs_err_pid logs when the required .NET runtime is not installed.

ABL batch clients occasionally crash after running proGetStack (SIGUSR1) on the PID of the ABL batch client.

Fathom tomcat process consuming high CPU.

OEE not indicating actual database status.

OpenEdge management is giving CPU and memory usage alerts for usage above 100%

In OpenEdge Memory Profiler (OEMP), deleting a large recording could cause excessive database Before-Image (BI) file growth and disk space exhaustion because child records were deleted in large, unbatched transactions. The deletion process has been updated to batch record deletions into smaller transaction scopes, preventing unexpected BI growth.

Client connection to PASOE fails after 60 seconds with TLS 1.3 Protocol.

If a SQL client dies or becomes unresponsive during connection while performing SSL negotiation with OpenEdge database, it might result in OpenEdge SQL Server process, (_sqlsrv2) to hang.

STOPPED local sessions never evicted when the connection are terminated via idleSessionTimeout leading to OOM

In PASOE, setting statusEnabled within a webapp-specific section of openedge.properties is ignored, causing only the global [AppServer] setting to take effect.

Health Scanner default returns a failed state out of the box

Error “The network path was not found” occurs when creating a pasoe instance or deploying webapps to an existing pasoe instance at the root of the drive. For example, using pasman/tcman.bat to create or deploy to C:/oepas1 fails with this error.

A delay could occur during specific TLSv1.3 SSL retry scenarios in ABL client communication. This fix removes the pause and relies on the existing retry logic to handle the condition correctly, eliminating the delay while maintaining reliable network communication.

Error reported in PASOE for an erroneous HTTP request doesn’t provide clear information

Error 'sem_timedwait() error: -1 errno: 4' shuts down the admin thread, terminating the agent

Cannot clear PASOE instance log files: check for locked files." when starting a pasoe instance using pasoestart or the OEM webinterface

Client-Principal attributes that contain special characters are not displayed properly.

Attempting to pass a dataset back from a PAS OE instance to a user authenticated by MS AD, belonging to many membership groups causes an ACCESS VIOLATION crash.

If the location of the Tomcat catalina PID file is changed, then the TCMAN PASOESTART or PASMAN PASOESTART command will fail.

Failed Oauth2 authentication not shown in authn/authz logfile

PASOE instance fails to start when using adding in the Spring Anonymous filter in Spring configuration files.

No service found error when changing the relative URI of a REST service

When invoking oemanager.sh to check instance status, there is a new line item in the output with "OESECURITY: UNKNOWN"

When creating a new instance, the instances.unix / instances.windows files are copied from {CATALINA_HOME}/conf > {CATALINA_BASE}/conf. While the  $CATALINA_BASE/conf instances files  are not used, the content is not consistent across instance directories and create confusion

When certain illegal/malformed requests were sent to a Progress Application Server for OpenEdge (PASOE) production instance, the returned Tomcat error page included the underlying Tomcat server version. This has been corrected so production PASOE instances no longer include the Tomcat version in these error pages by default.

Using the OE Manager REST API oemanager/applications//sessions?sessionID=&terminateOpt=2, the agent is terminating session immediately instead of waiting for the current request to complete.

Using binaryUploadMaxSize in openedge.properties is a no-op.  This property (when fetched using get-config() function) always returns ?.

Unable to deploy a WAR file due to an error coming from the web application deployment tailoring

There's a risk of name collision when running the tcman clean -A on Windows because the archive folder name format as defined in the %DLC%/oepas1/bin/tcmanager.ps1 doesn't guarantee uniqueness.tcmanager.ps1 reads:  $_subdir="$(get-date -f MM-dd-yyyy-ss)"

The “Get OEABL WebApp Metrics” operation of the PASOE REST API always returns HTTP 500 error.

The tcman / pasman plist command can output invalid child processes.

The PASOE Session Manager process (java) will crash when it receives signal 15 (SIGTERM).

The PASOE Agent runs out of ABL Sessions before reaching maxAblSessionsPerAgent.

The OpenEdge tailoring scripts may fail if there are Apache Ant libraries located in %USERPROFILE%\.ant\lib .

The ${psc.as.https.connectiontimeout} variable is missing from the HTTPS acceptor section within the server.xml file.

Terminating hung PASOE agent crashed database

Running “tcman.bat clean -A” online causes error about agent log being in use.

SOAP requests are not updating the pasoe Application Metrics 'Max Concurrent Clients:' counter and the related 'PAS Application Concurrent Connected Clients' chart when using OpenEdge 12.2.17 or 12.8.8Under OpenEdge 11.7.22 the pasoe Application Metrics 'Max Concurrent Clients:' counter is being updated when doing SOAP requests

PASOE API doesn't need a valid Application Name to stop Agent or ABL Session

OEMANAGER REST API calls will hang forever if an Agent is in a hung state.

PASOE 12.8.6 instance running on linux becomes randomly unresponsive and NoAvailableConnection exception messages are shown in [ablapp].[date].log

PASOE ABL Sessions crash with fatal signal 11 when making calls to another PASOE instance via SSL.

PASOE ABL Sessions randomly crash when calling a HTTPS REST service with the ABL HTTP client.

PASOE agent fails to start if agent startup parameter has the -pf parameter and the .pf file contains a -param that contains value starting with dash (-).

PASOE agent may crash when handling a .NET exception with a NO-ERROR.

Removal of the psc.as.msg.timeout property in catalina.properties and its relevant Message Timeout field in OEM.

PASOE instance fails silently after enabling JMX ports through the -Dcom.sun.management.jmxremote.port and -Dcom.sun.management.jmxremote.rmi.port JVM parameters

When waiting for a record lock in a PASOE Application using a shared memory connection to the database, the STOP-AFTER time-out and Administrative STOP operations are ignored until the lock wait is satisfied.

PASOE logs does not record the reason/origin for ABL session termination

PASOE sometimes fails to reliably start

PASOE startup warning in catalina log file caused by incorrect way of configuring default value of psc.as.https.protocol in the file conf\catalina.properties

PASSOE does not return details when a MsgFormatException is thrown, losing details on why the exception happened.

READEME files does not explicitly specify psc.as.logging.maxhistory in the logging-tomcat.properties and logging-pasoe.properties  preserves psc.as.logging.maxhistory plus 1 file including active file.

4GLTrace logging adds additional 4GLTrace logging line with truncated data if the line is long.

When creating an ABL WebApp project in Progress Developer Studio for OpenEdge (PDSOE), schema validation errors could appear in the Problems view for files such as oeablSecurity, referencing an unreachable spring-security.xsd schema document. These were validation warnings only and did not affect publishing or running web services; they have been resolved so they no longer appear.

The AppBuilder perspective of the Developer Studio doesn’t generate  trigger code for ABL menu widgets.

In PDSOE, compiling source files with non-UTF-8 characters in project startup AVM using -cpinternal UTF-8 causes runtime errors, stops the build, and requires restarting the AVM.

Resource View in PDSOE does not display correctly

New class creation fails when the target package name contains a hyphen (-)

Run Configuration: Relative paths cause error on Profiler/Performance tabs (Temporary files directory) when working directory is set to “C:\”.

Sustained memory growth for OpenEdge SQL Server process,  _sqlsrv2 under heavy workload triggering JAVA based UDF queries.

OpenEdge SQL server crashes when “-SQLStmtCache” is set to greater than or equal to 819.

When Group by and Where clause contains similar columns then Group by is optimized to use stream aggregation by reusing the selected index for query filter. If there is NULL check in Where clause on a column then incorrect results might be returned due improper copy of the index related information.