Problems connecting to ODB with OmnisSQL

[Michael Houlberg]

An update on my situation:

I have a logon window, so I’m not dealing with the kind of problem you are having Reg.

Not only would the branch computers not see ODB and not be able to log in, but the ODB host computer could not quit without a Force-Quit.  Branch computers would get errors showing odb://0.0.0.0 in them as if ODB wasn’t running even though I could confirm ODB was running on the host computer.

I removed the LaunchDeamon.  That seemed to be the cause of my problems.  After removing it, I rebooted, then started up ODB manually from Terminal.  At that point everyone could connect again as normal.  One thing that happened was the first time I started ODB, I got a message asking me to approve ODB receiving connections.  That was probably the problem when running as a service.  Anyway the client had been happy in the past when I included the odbconfig.lbs and I see there is a newer version on the Omnis website, so we are back to using that.  Also I see that it defaults to using 100 for a timeout.  Also I can quit the application on the host computer again.

Michael Houlberg
Houlberg Development, LLC

> On Mar 1, 2022, at 12:26 AM, Jef Leys | Desim <jef.leys at desim.be> wrote:
> 
> Hi
> 
> I solved this issue by increasing the socket timeout in the ODB connections config to 100.
> 
> Jef Leys
> 
>> Op 1 mrt. 2022, om 02:59 heeft Reg Paling <reg.paling at lokanet.com> het volgende geschreven:
>> 
>> Hi all,
>> 
>> Michael Houlberg mentioned in another thread:
>>> Also, we’re having problems getting the other computers, other than the ODB host, to connect with the OmnisSQL DAM. Has anyone else seen problems here?
>> 
>> I am starting another thread because I am hoping that this issue might see a bit of discussion in its own right...
>> 
>> Yes Michael, I am having difficult-to-diagnose problems.  In my case, these problems occur when the workstation is configured to skip the logon window and just automatically open the datafile with saved credentials.  If I turn the Logon window back on, then the small delay or interruption thus created seems to avoid the problem.
>> 
>> I have put some sleep() commands into the logic and they seem to (maybe) reduce the frequency of the issue but they don't totally remove it.
>> 
>> Sometimes I will get a "table not found" error from OmnisSQL, sometimes it hangs in other ways.
>> 
>> On affected computers it happens 10% or 20% of the time and the rest of the time it starts up without a problem.
>> 
>> I am not sure it is due to ODB v1.77 - I think it is more a Studio 10.2 thing.
>> 
>> I have wrapped the logon in a repeat loop to try the connection again if it fails, but I can't always diagnose the failure.
>> 
>> Does anyone know exactly what this is?
>> 
>> Thanks,
>> Reg
>> 
>> _____________________________________________________________
>> Manage your list subscriptions at https://lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 
> 
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com