Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Pervasive.SQL Topics / August 2008

Tip: Looking for answers? Try searching our database.

E_FAIL status error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ackerliz@gmail.com - 29 Jul 2008 16:31 GMT
Our VB application is generating this error:

Data Provider or other service returned an E_FAIL status error

when we attempt to retrieve data from our HISTORY file on certain
records in our PSQL database.

We are running Pervasive SQL 9.5 on a Linux RedHat server. On the
local workstation PCC, in some instances (we have indentified about 15
employee records which are affected by this error) we have been able
to retrieve the records from the file (called HISTORY), delete them,
and then recreate them. When we do that, we are then no longer able to
bring the new records up in PCC - it just sits there querying for
ages, and we have to CTRL+ALT+DEL PCC. The GUI then generates that
error when we click to enter the HISTORY screen.

The application encountered I/O error. Btrieve error 2

The current positioning is invalide. Btrieve error 8

These are errors when querying in PCC to find the records. We have
looked these errors up but have not yet found a way to resolve the
issue. In the table that is causing us grief, there is a unique index
which is comprised of 3 primary keys in the table...we believe that
somehow, we have managed to create duplicate records that shouldn't
have happened, which has resulted in corrupted records. We believe
that we need to delete these dups (that we cannot see) but have not
quite figured out how to do that.

Can anyone offer some suggestions or guidance?

Thanks!

Liz
BtrieveBill - 29 Jul 2008 20:04 GMT
The Status 2 indicates that the database file has been damaged
(literally, "I/O Error").  This means that you should stop using the
file and repair it as soon as possible, to prevent further data loss.

You can find infomration about basic file recovery from our web site at
www.goldstarsoftware.com/press.asp in the paper on Btrieve File
Maintenance.  This should get you started.

If this is not sufficient, or if you are losing more records than you
can afford to lose, then our data recovery capability may also be
helpful to you.  Click the big red "File Recovery" button on the website
mentioned above for more details.
    Goldstar Software Inc.
    Pervasive-based Products, Training & Services
    Bill Bach
    BillBach@goldstarsoftware.com
    http://www.goldstarsoftware.com
    *** Chicago: Pervasive Service & Support Class - August 2008 ***

> Our VB application is generating this error:
>
[quoted text clipped - 30 lines]
>
> Liz
ackerliz@gmail.com - 06 Aug 2008 03:50 GMT
Thanks, Bill...I used your document and we were able to export the
data minus the corrupt records and then import it into a new table,
rename the old table and then rename the new table....all seems to be
back to normal...the process that crashed because of the corrupt data
has run properly and we are so very relieved!!! Kudos to my very
determined analyst!!

Appreciate your input!!

Liz

> The Status 2 indicates that the database file has been damaged
> (literally, "I/O Error").  This means that you should stop using the
[quoted text clipped - 13 lines]
>        http://www.goldstarsoftware.com
>         *** Chicago: Pervasive Service & Support Class - August 2008 ***
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.