Search results

Seconded. Do not use -i, ever. I wouldn't even mess around with -r if I were you. You need to know what you're doing and understand the consequences of your actions to be using such things in production. I have seen this many times in the past. Someone decides to delete a large number of...

Welcome! If you have an issue, I suggest you create a new thread, and do so in the appropriate forum (Development).

Look at https://www.progress.com/oedk .

Some more detail is required about the problems you are trying to solve. What does "segment it" mean to you? It sounds like a solution that you envision to some problem. If so, what is that problem? The same goes for "more easy to use"? Easier than what? What usability problems are you...

In your second post it seems like you just ignored what I said. Why would you insist on not specifying -Mpb for a secondary broker when I just told you that you should always specify it, and that the fact that you didn't specify it is contributing to your problem? I already outlined detailed...

You haven't specified your OpenEdge release. This is important to know when discussing broker parameters. Three major points: Some broker parameters interact with each other. All of their values need to make sense together. Currently, they don't. These include -n, -Mn, and all values of...

Yes, it's from CyberScience. Unless someone here happens to have some expertise and can chime in, the best bet is to follow up with CyberScience tech support.

Attachment?

The problem is not with the database. The issue is on the client side. By default, an OpenEdge client can connect to up to five databases concurrently. This is a soft limit, it can be increased by specifying a higher value with the -h client startup parameter. E.g.: mpro -db db1 -db db2 -db...

I don't understand what you are doing. This batch file command runs a primary database broker for a database called calldata. You reported that you had a problem with your compile client, that it throws an error that it cannot connect to all of the databases it is attempting to connect to...

Credit where it's due: that's @TomBascom's message based on his research and consulting; I'm just spreading the word. Agreed on virtualization. It can provide real benefits but it isn't free (computationally) or risk-free. It adds another layer of abstraction and complexity, and can have...

I don't know your business, or the rate at which your data changes, or how much you can afford to lose. But you should. It sounds like you are modernizing to some extent. If I were you, I would start by modernizing the business continuity plan. Figure out your RPO and RTO and put in place...

You can try running Process Monitor during the installation. If there is a silent failure, e.g. accessing a registry entry or file, creating a service, spawning a process, you should see it there.

When last I checked (admittedly several years ago) there were several different development product licenses. They have different costs and features. The list varies by OpenEdge release. E.g.: 4GL Development System Basic compiler license. OpenEdge Studio GUI Procedure Editor interface...

When an ABL or SQL client connects to a database via TCP, it needs to make two connections: First, to the login broker on its service port (the value of -S for the broker). Once connected, the broker sends the client the port number of the server it should connect to. The client disconnects...

Hi Andy, Progress does support running multiple OpenEdge installations side-by-side on Windows, including 32-bit and 64-bit of the same release, since (I think) 11.5. I have multiple releases installed on my machine, including 12.8. So having the releases you mentioned already installed...

Are you aware of the install changes that Progress made as of 12.8.4? Previously, you could install OpenEdge from scratch in one of two ways: install then update install the FCS release (e.g. 12.8.0) install the latest update over top of that (e.g. 12.8.3) install directly from the update...

How to install a Progress OpenEdge Service Pack | update Progress Customer Community If it didn't, there wouldn't be any point in updating. Yes. You test an OpenEdge update the same way you test any other change before deploying it to production: on your test server, with production-like...

From ProKB:

I originally wrote: This should have read: A value of -Ma 1 means that each server will only allow one client connection. Sorry for the error. I have corrected it above.