Can’t connect to the server after the latest patch

Data Abstract
1

Hey,
Since the last patch, I’ve been getting a “connection failed” error every time I try to log in. I’ve checked my internet connection, and everything else seems fine. Has anyone else experienced this, or do you have any tips for fixing it?

Appreciate the help!

2

Hi,

Can you specify your platform (Delphi, .NET, etc), edition (full or trial) and version of Data Abstract, pls?

You might have firewall issue, i.e. firewall doesn’t allow to connect to remote server.

Can you connect locally to Relativity server? You might test any sample.

3

I am also experiencing problems with the latest patch (.1611) and Delphi 12.2

DAMemDataTable.Open hangs on lDataAdapter.Fill in the method LoadFromRemoteSource in uDADataTable

Got back to .1607, problem(s) solved.

4

Hi,

Can you create a simple testcase that reproduces this issue, pls?

I don’t see any changes related to RDA.Fill between .1607 and .1611

5

Well, that’s a bit of a problem… Lack of time is holding me back.

Strange though that all of the “weird stuff” is vanished when .1611 is uninstalled and .1607 back in business.
Even my server-application didn’t stop properly. Remained resident in memory. This is also solved going back to .1607

6

Hi,

Hmm, I can’t reproduce any issue with DA Server sample (Delphi) and Dynamic Where sample (desktop) (Delphi) …

Grid on client-side was filled with data correctly and DAServer was closed w/o any issue …

7

Never mind… my mistake, sorry for that

1 Like
8

For posterity – what was the issue, if you can share?

9

I had just installed the latest version of RODA.
I hadn’t noticed that I had created a deadlock situation in a (derived) BusinessProcessorRules.
After a few tries, I was convinced it was related to the latest version of DA. So I installed the previous version - and of course rebooted my PC - and the deadlock was gone (logically).

That convinced me even more that it was to do with the latest version… Of course, after retesting, I had the same situation that led me to the deadlock.

So, again, sorry for the inconvenience.

1 Like
10

No worries at all, this what we’re here for! thanks for the explanation, maybe it can help others in the future if a similar situation arises.

—marc