I used the OpenSSL manual.
As to which ciphers are actually used when you allow two, I'm not sure if this shows up with logging-level 5.
Maybe this will show in Fiddler.
TLS 1.3 will not work with 11.7.
I think you have two typos in your remaining ciphers:
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES128-GCM-SHA256
11.7.17 uses OpenSSL 1.1.1q - not sure about 11.7.18 -> proenv
sslc version
You will need to force the Progress client to use these ciphers, the...
You are encoding an unlimited bit length string to a limited bit length space. Why are you surprised? This is a property of all hashes - see Hash collision - Wikipedia - the 16 character length of _password does not help in reducing the chance of hash collision.
It would have been easier if Java 8: Does OpenEdge Support Java8 Runtime for OE11.6? had had a link to How to change the Java version for an OpenEdge installation on Windows.
I've seen this oddity repeated a few times in the knowledge base - it is not true.
Someone seems to have thought that since the format for the _user._password field is x(16), you can only enter a 16 character password. The plain text password is not stored in _password, the encoded password is...
You are aware that OpenEdge 11.7.4 was the first release of 11 for which Windows 2019 server was certified?
You are aware that OpenEdge 11.3 was retired in 2016?
what is in your WebSpeed agent log? I think you will also get an unable to run if for example your code was compiled against a...
From the docs:
I'm not sure about this balancing act, but if you add an additional > to the left of your decimal point, it creates extra space to show the < on the right.
I'm not seeing any outer-join in your code, so I'm not sure what you are trying to do. With a query you can tell if something is ambiguous when first-of does not equal last-of:
DEFINE TEMP-TABLE foo NO-UNDO
FIELD pk AS INTEGER
FIELD t AS CHARACTER
FIELD fk AS INTEGER
// should...
You seem to be trying to connect using JDBC, based on this community post it would seem you need to use an ODBC client to have a chance of talking with the SQL processes.
The error is your reward for using ancient software. When a parameter is not recognized, Progress tries to help you and use the parts it does recognize. -S is known -ServerType is not, so you are given a "helpful" message about -e, the first letter of the unrecognized parameter.
I am guessing...
based on SendKeys Class (System.Windows.Forms) it seems to be:
System.Windows.Forms.SendKeys:Send('^v')
As to the initial could not locate method error - if you use the PDSOE class browser (CTRL+F12) and go to class System.Windows.Forms.RichTextBox and then select method ProcessCmdKey - it...
Your Java stack trace starts with:
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.progress.osmetrics.OSMetricsImpl.jniInitLibrary(Ljava/lang/String;)Z+0
j com.progress.osmetrics.OSMetricsImpl.initLibrary()Z+10
So maybe Admin Server Does not Start and Create...
10.2B is not certified on Windows 11.
10.2B ships with Java 1.5 (1.5.0_11-b03). Java 5 was released in 2004.
Java 8, which 11.7 uses seems to be supported on Windows 11.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.