dbTalk Databases Forums  

problm with btrieve

comp.databases.btrieve comp.databases.btrieve


Discuss problm with btrieve in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
nmm
 
Posts: n/a

Default problm with btrieve - 05-11-2009 , 03:24 AM






Hi,

we observe on a Win2003-Server R2 SP1, running PSQL 9.50.077.002
sometimes, that the btrieve close-command b_close (1) does not return,
i.e. the programm hangs in BTRCALL.DLL.
The application involved is running on the server (not on a client
from the network). The file to be closed has been opened without
problem (dsatus=0). Also get-operatons (milliseconds before the
close-command) on that file processed without problem.

The problm appear sporadic during an autumatic process, that runs
every night.

What can be the reason for this? There are no messages in pvsw.log.

May be there are something in logfiles in the directory MKDE\LOGS, but
these are bin files, and I do not know, how to make them readebale.

We will appreciative on any hints!

Regards
Mircea

Reply With Quote
  #2  
Old   
BtrieveBill
 
Posts: n/a

Default Re: problm with btrieve - 05-12-2009 , 12:21 PM






The MKDE\Logs folder contains the transaction logs, and these contain no
human-readable information.

I would first suggest that you patch to 9.71 update, which is available
from Pervasive's web site. If that doesn't help, then you may be
experiencing a memory leak on your application causing it to fail.
Recheck to make sure that you are not closing any files twice or
something bad like that. You can also monitor the application with a
network analyzer and see what is really happening behind the scenes, but
this is a bit more lengthy process...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive Training - July 2009 in Chicago ***


After that

nmm wrote:
Quote:
Hi,

we observe on a Win2003-Server R2 SP1, running PSQL 9.50.077.002
sometimes, that the btrieve close-command b_close (1) does not return,
i.e. the programm hangs in BTRCALL.DLL.
The application involved is running on the server (not on a client
from the network). The file to be closed has been opened without
problem (dsatus=0). Also get-operatons (milliseconds before the
close-command) on that file processed without problem.

The problm appear sporadic during an autumatic process, that runs
every night.

What can be the reason for this? There are no messages in pvsw.log.

May be there are something in logfiles in the directory MKDE\LOGS, but
these are bin files, and I do not know, how to make them readebale.

We will appreciative on any hints!

Regards
Mircea

Reply With Quote
  #3  
Old   
nmm
 
Posts: n/a

Default Re: problm with btrieve - 05-14-2009 , 10:28 AM



Thank you! I think, that memory leaks and doubble closing are not the
reason: the program runs on other locations without this problm (since
about 10 years in summa). But the other sites are running PSQL 8.x.

We will try, wether the update to 9.71 will help...



BtrieveBill schrieb:
Quote:
The MKDE\Logs folder contains the transaction logs, and these contain no
human-readable information.

I would first suggest that you patch to 9.71 update, which is available
from Pervasive's web site. If that doesn't help, then you may be
experiencing a memory leak on your application causing it to fail.
Recheck to make sure that you are not closing any files twice or
something bad like that. You can also monitor the application with a
network analyzer and see what is really happening behind the scenes, but
this is a bit more lengthy process...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive Training - July 2009 in Chicago ***


After that

nmm wrote:
Hi,

we observe on a Win2003-Server R2 SP1, running PSQL 9.50.077.002
sometimes, that the btrieve close-command b_close (1) does not return,
i.e. the programm hangs in BTRCALL.DLL.
The application involved is running on the server (not on a client
from the network). The file to be closed has been opened without
problem (dsatus=0). Also get-operatons (milliseconds before the
close-command) on that file processed without problem.

The problm appear sporadic during an autumatic process, that runs
every night.

What can be the reason for this? There are no messages in pvsw.log.

May be there are something in logfiles in the directory MKDE\LOGS, but
these are bin files, and I do not know, how to make them readebale.

We will appreciative on any hints!

Regards
Mircea

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.