Author | Topic: error | |
---|---|---|
Edgar Borger | error on Thu, 08 Aug 2019 14:57:29 -0300 after migrating from DBF to postgresql via Boris, SQLExpress, I am getting this errors, any clue ? server is Win 2012 R12 Alaska xbase 1.90.335 thanks, Edgar FATAL ERROR LOG Error within the error handling! SYS Thread-ID: 2304 Module: EXE Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 Call Stack of Thread 1 (984): MAIN(581) Call Stack of GUI Thread (1184): Call Stack of Thread 3 (2020): @MXPRINTSCREEN@I@EXECUTE(122) Call Stack of Thread 4 (2056): Call Stack of Thread 5 (1940): @DC_GETLIST@I@EVENTLOOP(3743) @DC_GETLIST@I@READGUI(3488) DC_READGUI(85) TELEM(227) Call Stack of Thread 6 (2304): @SQLSELECT@I@FETCHROW(2930) @SQLSELECT@I@__FETCHNEXT(2355) @SQLSELECT@I@SKIP(2547) @SQLDATASET@I@FETCHDATA(385) @SQLDATASET@I@EXECUTE(60) LESQL(326) Call Stack of Thread 7 (1968): File: c:\dll\vendasql.EXE TimeStamp: 20190808 14:50 End of FATAL ERROR LOG. Edgar Borger Softsupply Informatica Ltda. Rua Alagoas, 48 Sao Paulo, SP 01242-000 Tel : (5511) 3159-1997 Email : softsupply@terra.com.br | |
Matej Jurac | Re: error on Fri, 09 Aug 2019 08:29:47 +0200 It would be helpful if you pasted source for us to see as there are many reasons for that. Is there anything in sqlerror.log too? Edgar Borger <eborger@terra.com.br> wrote in message news:15d9f0c3$628adec6$157ea@news.alaska-software.com... >after migrating from DBF to postgresql via Boris, SQLExpress, I am getting this errors, any clue ? > >server is Win 2012 R12 >Alaska xbase 1.90.335 > >thanks, >Edgar > > >FATAL ERROR LOG >Error within the error handling! >SYS Thread-ID: 2304 >Module: EXE >Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 >Call Stack of Thread 1 (984): >MAIN(581) >Call Stack of GUI Thread (1184): >Call Stack of Thread 3 (2020): >@MXPRINTSCREEN@I@EXECUTE(122) >Call Stack of Thread 4 (2056): >Call Stack of Thread 5 (1940): >@DC_GETLIST@I@EVENTLOOP(3743) >@DC_GETLIST@I@READGUI(3488) >DC_READGUI(85) >TELEM(227) >Call Stack of Thread 6 (2304): >@SQLSELECT@I@FETCHROW(2930) >@SQLSELECT@I@__FETCHNEXT(2355) >@SQLSELECT@I@SKIP(2547) >@SQLDATASET@I@FETCHDATA(385) >@SQLDATASET@I@EXECUTE(60) >LESQL(326) >Call Stack of Thread 7 (1968): >File: c:\dll\vendasql.EXE >TimeStamp: 20190808 14:50 >End of FATAL ERROR LOG. | |
Edgar Borger | Re: error on Fri, 09 Aug 2019 12:22:08 -0300 Hi Matec, it's to big post.... basicaly I am reading a table into memory, select "about 10 fields" from table order by field1 the error code says memory full, could that be the case ? the table has about 25.000 rows..... Em 09/08/2019 03:29, Matej Jurac escreveu: > It would be helpful if you pasted source for us to see as there are many reasons for that. > > Is there anything in sqlerror.log too? > > > > Edgar Borger <eborger@terra.com.br> wrote in message news:15d9f0c3$628adec6$157ea@news.alaska-software.com... >> after migrating from DBF to postgresql via Boris, SQLExpress, I am getting this errors, any clue ? >> >> server is Win 2012 R12 >> Alaska xbase 1.90.335 >> >> thanks, >> Edgar >> >> >> FATAL ERROR LOG >> Error within the error handling! >> SYS Thread-ID: 2304 >> Module: EXE >> Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 >> Call Stack of Thread 1 (984): >> MAIN(581) >> Call Stack of GUI Thread (1184): >> Call Stack of Thread 3 (2020): >> @MXPRINTSCREEN@I@EXECUTE(122) >> Call Stack of Thread 4 (2056): >> Call Stack of Thread 5 (1940): >> @DC_GETLIST@I@EVENTLOOP(3743) >> @DC_GETLIST@I@READGUI(3488) >> DC_READGUI(85) >> TELEM(227) >> Call Stack of Thread 6 (2304): >> @SQLSELECT@I@FETCHROW(2930) >> @SQLSELECT@I@__FETCHNEXT(2355) >> @SQLSELECT@I@SKIP(2547) >> @SQLDATASET@I@FETCHDATA(385) >> @SQLDATASET@I@EXECUTE(60) >> LESQL(326) >> Call Stack of Thread 7 (1968): >> File: c:\dll\vendasql.EXE >> TimeStamp: 20190808 14:50 >> End of FATAL ERROR LOG. Edgar Borger Softsupply Informatica Ltda. Rua Alagoas, 48 Sao Paulo, SP 01242-000 Tel : (5511) 3159-1997 Email : softsupply@terra.com.br | |
Jim Lee | Re: error on Sat, 10 Aug 2019 06:16:36 +0200 > Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 EH 1006 two many memory-objects: there are not enough handles XPP 15 XPP_ERR_MEMORY_FULL Not enough memory or swapping space available --- > basicaly I am reading a table into memory, select "about 10 fields" from > table order by field1 > the error code says memory full, could that be the case ? the table has > about 25.000 rows..... Question 32 Bit oder 64 Bit OS ? i don't think 25000 Row is to much but it seems your run too much Apps on 32 Bit OS ? --- there are some "4 GB Game Patch" for 32 Bit Games unter 64 Bit OS they use a "large address aware" Flag that is set by 4 GB Patch. those Patch seem also to run with 32 Bit Apps ... --- you can load SQL Row "dynamic" into Listview using LVS_OWNERDATA / LVN_GETDISPINFO. have a look at Pablo Website www.xbwin.com or Newsgroup news.xbwin.com --- Diese E-Mail wurde von AVG auf Viren geprüft. http://www.avg.com | |
Matej Jurac | Re: error on Mon, 12 Aug 2019 09:19:04 +0200 @Edgar In todays term 25k row table, unless it contains BLOBs of images,pdfs is but a small one and should not be problematic memory consumption wise. But could be "@MXPRINTSCREEN@I@EXECUTE(122)" the real culprit on allocating too much memory for whatever it is doing ? If memory is full as indicated by error codes, close web browsers (as they are memory hogs) or retry on another workstation. Extract only sql handling code and try it in separate exe. If it works fine, you have somewhere else a memory leak. Sorry, but lack of insight what you are doing means you are on your own. No info on which odbc driver release you are doing, how is code around Select done, whethere SqlDataSet or SqlSelect is used, etc. Jim Lee wrote in message news:44239f10$19f581a2$1a85c@news.alaska-software.com... >> Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 > >EH >1006 two many memory-objects: there are not enough > handles > >XPP > 15 XPP_ERR_MEMORY_FULL Not enough memory or swapping space > available >--- > >> basicaly I am reading a table into memory, select "about 10 fields" from >> table order by field1 >> the error code says memory full, could that be the case ? the table has >> about 25.000 rows..... > >Question 32 Bit oder 64 Bit OS ? > >i don't think 25000 Row is to much but it seems your run too much Apps on 32 >Bit OS ? > >--- > >there are some "4 GB Game Patch" for 32 Bit Games unter 64 Bit OS >they use a "large address aware" Flag that is set by 4 GB Patch. > >those Patch seem also to run with 32 Bit Apps ... > >--- > >you can load SQL Row "dynamic" into Listview using LVS_OWNERDATA / >LVN_GETDISPINFO. >have a look at Pablo Website www.xbwin.com or Newsgroup news.xbwin.com > > > > > >--- >Diese E-Mail wurde von AVG auf Viren geprüft. >http://www.avg.com | |
Jim Lee | Re: error on Mon, 12 Aug 2019 22:49:45 +0200 as i can say Edgar is using Thread for each Connection. 32 Bit App can only use 2 GB RAM but OS take more that 1.3 GB RAM so only 600-700 MB can be used. the Problem is to "free RAM" which is done by CG so it can fail when have used much RAM before. --- Diese E-Mail wurde von AVG auf Viren geprüft. http://www.avg.com | |
Edgar Borger | Re: error on Tue, 13 Aug 2019 14:49:09 -0300 Thanks all, I am reviewing my code to reduce memory usage. Em 08/08/2019 14:57, Edgar Borger escreveu: > after migrating from DBF to postgresql via Boris, SQLExpress, I am getting this errors, any clue ? > > server is Win 2012 R12 > Alaska xbase 1.90.335 > > thanks, > Edgar > > > FATAL ERROR LOG > Error within the error handling! > SYS Thread-ID: 2304 > Module: EXE > Error Codes: EH: 1006 Sub: 0(0) OS: 0 XPP: 15 > Call Stack of Thread 1 (984): > MAIN(581) > Call Stack of GUI Thread (1184): > Call Stack of Thread 3 (2020): > @MXPRINTSCREEN@I@EXECUTE(122) > Call Stack of Thread 4 (2056): > Call Stack of Thread 5 (1940): > @DC_GETLIST@I@EVENTLOOP(3743) > @DC_GETLIST@I@READGUI(3488) > DC_READGUI(85) > TELEM(227) > Call Stack of Thread 6 (2304): > @SQLSELECT@I@FETCHROW(2930) > @SQLSELECT@I@__FETCHNEXT(2355) > @SQLSELECT@I@SKIP(2547) > @SQLDATASET@I@FETCHDATA(385) > @SQLDATASET@I@EXECUTE(60) > LESQL(326) > Call Stack of Thread 7 (1968): > File: c:\dll\vendasql.EXE > TimeStamp: 20190808 14:50 > End of FATAL ERROR LOG. > > > Edgar Borger Softsupply Informatica Ltda. Rua Alagoas, 48 Sao Paulo, SP 01242-000 Tel : (5511) 3159-1997 Email : softsupply@terra.com.br |