dbTalk Databases Forums  

Known issue w/ Pervasive 8.6 Workgroup Engine?

comp.databases.btrieve comp.databases.btrieve


Discuss Known issue w/ Pervasive 8.6 Workgroup Engine? in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Alan S. Olson
 
Posts: n/a

Default Known issue w/ Pervasive 8.6 Workgroup Engine? - 02-16-2005 , 07:28 PM






Hello All -

Whenever i go to reboot my computer after using any applications that use
Pervasive, i am forced to manually shut down teh Pervasive Workgroup engine.
There seems to be an issue with clients not properly being removed even if
those clients/sessions have no files open. If i go into the Monitor
utility, the username is still listed, even if they have no files open.
Obviously this causes problems when Windows tells the engine it needs to
reboot. The workgroup engine then complains and will not let Windows
shutdown and/or reboot.

Is this a known issue with 8.6? Does anyone else experience this?

Thanks,

Alan Olson



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

Default Re: Known issue w/ Pervasive 8.6 Workgroup Engine? - 02-17-2005 , 08:21 AM






The session must be explicitly closed by the application.
When the first file is opened a session is opened and stays open until
the application issues a Stop(25) or Reset(28).

ODBC is a little more explicit about session opens and closes so they
are normally correct, however if the session is not closed it will
stay out there also.

While not reported in the monitor, the monitor session will also keep
the engine from stopping. It is possible the application has a
similar kind of connection, DTI. Like all of the others it must be
closed by the application.

Leonard

On Thu, 17 Feb 2005 01:28:29 GMT, "Alan S. Olson"
<aolson (AT) bizwi (DOT) rr.com> wrote:

Quote:
Hello All -

Whenever i go to reboot my computer after using any applications that use
Pervasive, i am forced to manually shut down teh Pervasive Workgroup engine.
There seems to be an issue with clients not properly being removed even if
those clients/sessions have no files open. If i go into the Monitor
utility, the username is still listed, even if they have no files open.
Obviously this causes problems when Windows tells the engine it needs to
reboot. The workgroup engine then complains and will not let Windows
shutdown and/or reboot.

Is this a known issue with 8.6? Does anyone else experience this?

Thanks,

Alan Olson



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.