Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread Dataset load response error messages
Sun, Jun 7 2015 4:05 AMPermanent Link

Uli Becker

Hi,

with EWB2 I get always the same error message if there is a problem
loading a dataset:

"Dataset load response error (Cannot connect to server)"

 Am I overlooking something to get a more detailed error message?

Thanks Uli
Sun, Jun 7 2015 11:29 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 6/7/2015 4:05 AM, Uli Becker wrote:
> with EWB2 I get always the same error message if there is a problem
> loading a dataset:
>
> "Dataset load response error (Cannot connect to server)"
>
>   Am I overlooking something to get a more detailed error message?

This is currently triggered for unsuccessful http prequest (meaning
StatusCode <> 200). Framework tries to retrieve http request
ResponseContent and if either that is blank or statucode is 0  then this
is the default message you end up with.

There are few issues at play :
- for a legit "unable to connect" (say bad server address/ip) one does
not really have more info available
- the other problem is that browsers do hide some of the low level error
stuff also (for example CORS related errors) so you do need to still
drop into the browser debug tools to get more detail and see what
exactly might be a problem.

I hope this is something Tim can eventually do more about but lot of it
is dependent on the browser.

Raul
Mon, Jun 8 2015 4:30 AMPermanent Link

Uli Becker

Raul,

> This is currently triggered for unsuccessful http prequest (meaning
> StatusCode <> 200). Framework tries to retrieve http request
> ResponseContent and if either that is blank or statucode is 0  then this
> is the default message you end up with.

OK, I found it here:

TempErrorMsg:=Request.ResponseContent.Text;
if (TempErrorMsg='') or (Request.StatusCode=HTTP_NONE) then
   TempErrorMsg:=Translate('ERR_DATA_CONNECT');

The question is maybe, why there is no detailed Error message in the
Request.ResponseContent.Text. I'm not sure, if that was different in
EWB1 or early versions of EWB2.

Thanks Uli
Mon, Jun 8 2015 11:04 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 6/8/2015 4:30 AM, Uli Becker wrote:
> The question is maybe, why there is no detailed Error message in the
> Request.ResponseContent.Text. I'm not sure, if that was different in
> EWB1 or early versions of EWB2.

This is all based on the XMLHttpRequest in javascript and for some type
of errors where one cannot get a connection there is simply no way to
know so there is nothing to display.

(following is based on direct use of XMLHttpRequest but same in EWB2).

For example connecting to an invalid URL (say http://www.ewb1.com)
results in status = 0 from javascript side and nothing in responseText.
Chrome internally does show "ERR_NAME_RESOLUTION_FAILED" but that is not
surfaced and you can only see if it is you have developer tools console
open..

Similarly connecting to a valid site that does not allow cross origin
scripting results is same. So connecting to "http://www.google.com")
results in status = 0 from javascript and nothing in responseText.

Again in Chrome you will see "XMLHttpRequest cannot load
http://www.google.com/. No 'Access-Control-Allow-Origin' header is
present on the requested resource" - however none of this is javascript
accessible again.

Hence you only get useful status and text if your connection succeeds
and your server actually responds with something (i.e. 2xx, 3xx, 4xx or
5xx series status codes).

Have not looked at EWB1 but it has same limitations so it could not
really display anything more either.

Raul
Tue, Jun 9 2015 3:42 AMPermanent Link

Uli Becker

Raul,

> This is all based on the XMLHttpRequest in javascript and for some type
> of errors where one cannot get a connection there is simply no way to
> know so there is nothing to display.

True, but that's not what I mean. I am referring to database errors. Let
me look for a sample and post it here.

Thanks Uli
Tue, Jun 9 2015 8:29 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 6/9/2015 3:42 AM, Uli Becker wrote:
> True, but that's not what I mean. I am referring to database errors. Let
> me look for a sample and post it here.

Uli,

Sounds good.

However "Dataset load response error (Cannot connect to server)" is what
OP listed and the 2 scenarios above are that result in that message.
There is no other data available in those cases.

Some examples for errors outside those would be useful to see - as well
as what you would expect to see as an error.

There is a side issue that only HTTP response 200 is considered success
so that's something Tim will need to fix but to get that the connection
would have to succeed and more info would be available just due to that.

Raul
Tue, Jun 9 2015 3:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Raul,

<< There is a side issue that only HTTP response 200 is considered success
>>

That was fixed in build 12 - it now considers any status code that starts
with '2' as a success.

Tim Young
Elevate Software
www.elevatesoft.com
Image