I have just started seeing "The RSE communications daemon could not be started." whenever I edit SQL statements. Maybe a coincidence, but this seemed to start happening right about the same time I applied the new fix pack. I check the port it says it cannot access, and the only app using the port is RDi. It is always in the low 4300s... Usually a system restart will make it work for a while. Disabling SQL syntax checking also seems to bypass this error.
Anyone else seeing this?
Possibly related, I am still seeing unexpected hard closures of RDi, usually as compile results are coming back to the Event Viewer (but I do not think it is only at this time). No java error, just RDi disappears. I have done totally clean reinstalls of everything except Windows itself, but this still happens intermittently. Wondering if the crashing RDi might be keeping the daemon active somewhere, locking the port.
If there is anything I can do to help isolate this, please let me know.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
