Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #4599 > unrolled thread

differnces 2.7 to 2.8

Started byOskar Atkinson <Oskar@atk-it.com>
First post2013-01-17 09:59 -0700
Last post2013-01-22 08:25 -0700
Articles 3 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  differnces  2.7 to 2.8  Oskar Atkinson <Oskar@atk-it.com> - 2013-01-17 09:59 -0700
    Re: differnces  2.7 to 2.8 D.J.W. van Kooten <public@ic2remove.this.com> - 2013-01-18 21:00 +0100
      Re: differnces  2.7 to 2.8 Oskar Atkinson <Oskar@atk-it.com> - 2013-01-22 08:25 -0700

#4599 — differnces 2.7 to 2.8

FromOskar Atkinson <Oskar@atk-it.com>
Date2013-01-17 09:59 -0700
Subjectdiffernces 2.7 to 2.8
Message-ID<1ebgf8hoatomi3u71dircclfafdegouk4e@4ax.com>
Howdy,

we have moved a large app from 2.7 ( 2773 ) to 2.8 (  SP4 2838 ) and now are experiencing random strange errors

like  indexord() sometimes crashes ( Table is open, closed table  is giving an different error )

     Severity ERROR
     GenCode 27 -> 
     SubSystem -> AXDBFCDX
     SubCode 5023
     FuncSym -> ORDERINFO FuncPtr 0x00000000
     VO-Description -> Error 5018:  The handle given was not recognized by Advantage


or in the super init call of an inherited dbserver

Error description :
     Severity ERROR
     FuncSym -> INIT FuncPtr 0x00000000
     MethodSelf -> W_23883

Calling Stack :
     00:     14 - _FUNCTIONS - GETCALLINGSTACK
     03:      2 - CLASS=dbGeneralDBServer - DBGENERALDBSERVER:INIT
     04:     40 - CLASS=DLSServer - DLSSERVER:INIT


anyone experiened such, any ideas

Thanks
Oskar

[toc] | [next] | [standalone]


#4611

FromD.J.W. van Kooten <public@ic2remove.this.com>
Date2013-01-18 21:00 +0100
Message-ID<j7ajf8hjoem0o3poe3429m8o4tbem4f6n9@4ax.com>
In reply to#4599
On Thu, 17 Jan 2013 09:59:11 -0700, Oskar Atkinson <Oskar@atk-it.com>
wrote:

Hello Oskar,

>     VO-Description -> Error 5018:  The handle given was not recognized by Advantage

Two notes: first make sure that all your FTP memo fields are 64 bit.
You can quickly arrange that with dbMax if you have that (export,
chosoe 64 bit). With 32 bit ftp, your VO program will quit without
error, and although we know it, it usually takes some time to
recognize it if we are bringing a new user to ADS with 32 bit memo
files... But now about your question:

I am not sure I've seen this error as well, but in the Advantage NG I
found the below reply from Peter Funk which solved the 5018 problem
for the person who posted the question. If it doesn't for you, I can
look further into our docs.

Dick
====

Hello David,
I was able to see the 5018 error today.  It is caused by the
KUNDEN.ADT table 
failing to open.  In fact, all the tables the application tries to
open fail 
to do so.  On my PC they are failing to open due to a collation
sequence 
mismatch.  This is no real surprise to me since I'm probably using a
different 
language setting than you.  Once I reindexed all the indexes with my
language, 
the application works fine.

If you open the tables in ARC, do you get a 5175
(AE_INDEX_COLLATION_MISMATCH) 
error?  If so, you need to reindex the tables so the indexes are built
with 
the correct language.  If you don't get the 5175 error, you might be
using 
ARC with the correct language, but the VO application is not.  The
language 
setting is set by ads_cfg.exe for remote server and set in
adslocal.cfg for 
local server.  Please check to make sure both these settings have the
same 
language.  If you're using local server with both ARC and the VO
application, 
look for multiple copies of adslocal.cfg as they might have different
settings 
in each one.

Now the reason this was so hard to track down is due to bad error
handling. 
 When the tables are opened in the Init method of the dbShellServer
class, 
there is no check to make sure the table actually opened.  Once I
tracked 
down the table open call there, I added some code to check if the
table actually 
opened:

SUPER:init (cFile, lShare, lReadOnly, cDriver)
IF !SELF:Used
   // do some error handling and bail out
ELSE
   // carry on as normal
ENDIF

Another indication that the table failed to open is the NetErr()
global flag. 
 It is set whenever a table fails to open.  You might want to check it
in 
addition to the DBServer:Used flag.

Finally, the 5018 error comes about after the table open fails but the
application 
continues on.  It tries to do some things with indexes and attempts to
get 
the current record number.  Since the table handle in the RDD is zero,
these 
calls fail with the 5018.

I hope this explains what is going wrong and gives you enough
information 
to solve the problem.  If it doesn't, let me know and we can look at
it a 
bit more.

Regards,
Peter Funk
Advantage R&D

[toc] | [prev] | [next] | [standalone]


#4631

FromOskar Atkinson <Oskar@atk-it.com>
Date2013-01-22 08:25 -0700
Message-ID<rcbtf8p3tbaad92uol4eetmq96d96g8ih4@4ax.com>
In reply to#4611
Hi Dick,

would be nice if it be that easy ..

However, the crash happens within the VO SDK . Pretty much the call to myDbServer:super:init( .. ) fails. So I cannot catch the error, espically as the sequence stmt in 2838  does not work in a
subclassed dbserver
And not all the time, just every now and then.
Also, running the same code in VO 2.7 ( 2773) and ADS 9 works without any problems with a couple thousand of installations in the field.
So, IMHO it is eiter VO 2.8 or ADS 10 creating the issue.

Right now I am going back to older 2.8 versions and see ... :-(

Oskar



On Fri, 18 Jan 2013 21:00:10 +0100, D.J.W. van Kooten <public@ic2remove.this.com> wrote:

>On Thu, 17 Jan 2013 09:59:11 -0700, Oskar Atkinson <Oskar@atk-it.com>
>wrote:
>
>Hello Oskar,
>
>>     VO-Description -> Error 5018:  The handle given was not recognized by Advantage
>
>Two notes: first make sure that all your FTP memo fields are 64 bit.
>You can quickly arrange that with dbMax if you have that (export,
>chosoe 64 bit). With 32 bit ftp, your VO program will quit without
>error, and although we know it, it usually takes some time to
>recognize it if we are bringing a new user to ADS with 32 bit memo
>files... But now about your question:
>
>I am not sure I've seen this error as well, but in the Advantage NG I
>found the below reply from Peter Funk which solved the 5018 problem
>for the person who posted the question. If it doesn't for you, I can
>look further into our docs.
>
>Dick
>====
>
>Hello David,
>I was able to see the 5018 error today.  It is caused by the
>KUNDEN.ADT table 
>failing to open.  In fact, all the tables the application tries to
>open fail 
>to do so.  On my PC they are failing to open due to a collation
>sequence 
>mismatch.  This is no real surprise to me since I'm probably using a
>different 
>language setting than you.  Once I reindexed all the indexes with my
>language, 
>the application works fine.
>
>If you open the tables in ARC, do you get a 5175
>(AE_INDEX_COLLATION_MISMATCH) 
>error?  If so, you need to reindex the tables so the indexes are built
>with 
>the correct language.  If you don't get the 5175 error, you might be
>using 
>ARC with the correct language, but the VO application is not.  The
>language 
>setting is set by ads_cfg.exe for remote server and set in
>adslocal.cfg for 
>local server.  Please check to make sure both these settings have the
>same 
>language.  If you're using local server with both ARC and the VO
>application, 
>look for multiple copies of adslocal.cfg as they might have different
>settings 
>in each one.
>
>Now the reason this was so hard to track down is due to bad error
>handling. 
> When the tables are opened in the Init method of the dbShellServer
>class, 
>there is no check to make sure the table actually opened.  Once I
>tracked 
>down the table open call there, I added some code to check if the
>table actually 
>opened:
>
>SUPER:init (cFile, lShare, lReadOnly, cDriver)
>IF !SELF:Used
>   // do some error handling and bail out
>ELSE
>   // carry on as normal
>ENDIF
>
>Another indication that the table failed to open is the NetErr()
>global flag. 
> It is set whenever a table fails to open.  You might want to check it
>in 
>addition to the DBServer:Used flag.
>
>Finally, the 5018 error comes about after the table open fails but the
>application 
>continues on.  It tries to do some things with indexes and attempts to
>get 
>the current record number.  Since the table handle in the RDD is zero,
>these 
>calls fail with the 5018.
>
>I hope this explains what is going wrong and gives you enough
>information 
>to solve the problem.  If it doesn't, let me know and we can look at
>it a 
>bit more.
>
>Regards,
>Peter Funk
>Advantage R&D

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web