Search results

The correct answer is to update to a supported version of OpenEdge and to then use OE Auditing. You claim to be running 10.02B which, so far as I know, is not an actual release. Did you perhaps means 10.2B? (no extra "0"). OE Auditing does exist in that version, it was introduced with 10.1B...

You have added some code page conversions to one of those DLCs but not to the other. So do whatever you did to the one that has them to the one that does not. You might also want to compare $DLC/startup.pf in the two DLCs and see if there are relevant differences. This might be a good place to...

There is no such thing as "32 bit database", there are databases that were started with 32 bit executables and there are databases that are started with 64 bit executables. If your mpro startup parameters do NOT contain -S portNum then you are trying to connect via shared memory. In that case...

In that case your requirements for db admin and application admin are basically the same as "old PROD". I can't see why anything would change there. You might have to update your various scripts and config files to reflect new host names, IP addresses and ports and paths but that's not really a...

Databases don't have "bitness". The installed executables do. There is no conversion of databases between 32 bits and 64 bits. There is nothing to do. You access the database with either 32 bit or 64 bit executables. If you are making shared memory connections everything needs to run from the...

Are you asking what you need to do in a "fail over" situation to be able to replace an existing database on a PROD server with one of the TEST databases? Presumably in a situation where the PROD server has failed?

Maybe you could share some simple sample code that shows what you have so far and where you need these current buffers? I'm having difficultly understanding how it is that you are able to iterate & return them but somehow don't know what they are.

Perhaps you can share a description of the problem and your eventual solution?

Maybe. Or maybe he is testing to see if some series of operations can corrupt his configuration. I can’t tell. The steps do appear to be 90% similar to an easily found kbase for reinitializing the OEM password. But the title talks about “recovery” not initialization. So it is quite unclear (to...

And while we are at it... what version of OpenEdge are we talking about?

What is "it" and what did you expect it to do that would constitute "working"?

That is an interesting series of events. Is there a question somewhere in there?

Stefan is pointing out that "Eclipse Jetty" is used by OpenEdge Explorer. And you very likely are using that. So it is more a matter of needing to restrict access to that port because, otherwise, anyone can fire up OpenEdge Explorer and wreak havoc on your systems. (Instead of just a few...

What does "starting up a server" have to do with anything? That sounds like a new bit of information.

Using _progres, or not, doesn't matter. That's just me being annoyed at the "when all you have is a hammer everything is a nail" approach. You could make me even more annoyed if you tell me that the source file is a .w. (Which also doesn't affect the outcome.)

"What is happening is best examiined in the Task Manager..." "...the .exe is left as a background process and for some reason their (as I am now a contractor) stays connected and it appears there are now limits to the number of connections." So "the problem" is that each execution of the task...

You don't need to upgrade SX in order to upgrade OpenEdge anymore than you need to upgrade SX before applying a Windows update.

Are you also responsible for managing the server? They seem to want someone (you? or whoever manages the server or network) to setup some firewall rules to limit who can talk to services. That seems reasonable. Unless this server is public facing and needs to accept requests from everyone. If...

Why? It’s good for the soul. Aside from that… yes, the executables are clearly different; why carry around all of that excess baggage? Batch jobs don’t need support for mice and GUIs and all of that useless cruft.

Another observation... your startup command contains "-n 4 -Ma 4". Those are server startup parameters. They have no relevance to starting a client session.