Recent content by Clueless

Thank you so much again!

Oh, one other thing - will it help to use the -Mm parameter on the database startup to increase the packet size? or does that have any effect at all on appserver connections?

Wow! Thanks for the quick response! One other consideration: What if the Windows Progress version does not match - ie. the Windows Progress is 11.6 or 11.5 whereas the Linux Progress version is 11.7? There are a number of these database moves and I'm not 100% all of them have Progress 11.7...

I have a working 11.7 openedge database on a Windows server. There is an appserver on the Windows server that connects to the Windows database that is working perfectly. For "mostly political reasons", I am tasked with moving the Windows database from the Windows server to a Linux server. So...

This is an old post, but just in case anyone else ever runs into the problem... The solution was to add the following line to the ubroker.properties file. Specifically, the appserver that was connected to needed this "Keep Alive" to avoid Communication Errors"...

Thanks for your response Rob. I have tried the PC client from the office and from home and get the same results. I have changed the office default gateway from a SonicWall firewall to a plain Linksys NAT router that has no advanced capabilities. Basically the same intermittent errors. I get...

Cringer, I posted this in the Developer's Forum also, because I thought it could be solved by that Forum group as well as this one. I am just desperate to get an answer to this and I know that I cannot be the only person who has ever seen this problem... Thanks.

I have a C# program using an open client connection directly to a CentOs 6.5 Linux OpenEdge 10.2B patch 8 appserver -> database (does not use the nameserver & operating mode is state-free). All works well when on a LAN. But when the Linux server was moved from a LAN to out-of-state data...

I have a C# program using an open client connection directly to a CentOs 6.5 Linux OpenEdge 10.2B patch 8 appserver -> database (does not use the nameserver). All works well when on a LAN. But when the Linux server was moved from a LAN to out-of-state data center, then started getting...

Found answer: replication port can be used by 4GL and SQL clients. So no need for separate brokers... This, of course, is the opposite of how the source database is configured = with separate 4GL and SQL brokers for performance and administration (in case the SQL broker/server hangs, then it...

Dumb question: I am trying to configure OE Replication Plus on a Windows 2012 server, but I am baffled at how to configure this using the OpenEdge Explorer. I can get things working by using the proenv commandline, but cannot figure out how to do this with OpenEdge Explorer: proserve...