Status 2I/O error
Usually a damaged data file, a failing disk, or a network drop in the middle of a write. The data is often recoverable, but repeated retries on the live file can make things worse.
Legacy systems · Remote, nationwide
Your old Btrieve app still runs the business. Let's keep it that way.
We keep Pervasive SQL, Btrieve, Actian Zen and VB6 software running on modern Windows, and we get your data out cleanly when it's time to move on. Remote help for businesses anywhere in the U.S.
01 — Sound familiar?
The software works. The people who understood it are gone.
Plenty of businesses still run on software built 20 or 30 years ago. It usually does its job just fine, until something changes underneath it.
/01
The vendor disappeared.
They retired, sold the company, or stopped answering the phone, and nobody else knows how the system works.
/02
The server is on borrowed time.
The machine it lives on is old, and everyone is afraid to touch it in case the whole thing stops working.
/03
Windows needs an upgrade.
IT wants to move to a current version of Windows, and nobody can say whether the app will survive the move.
/04
Your data is locked in.
You need it in Excel, SQL Server or a new system, and the database files won't open in anything modern.
/05
Errors keep coming back.
Users hit license limits or status codes, and restarting the server is the only fix anyone knows.
02 — Common errors
Pervasive and Btrieve errors we fix all the time.
If one of these status codes keeps coming up, it's usually a sign of something specific underneath. Here's what each one typically points to.
Status 12File not found
The application is looking for its data in a path that no longer exists. This commonly happens after a server move, a changed drive mapping, or a new workstation setup.
Status 20Record manager inactive
The database engine isn't running, or the workstation can't reach it. It often shows up after Windows updates, engine reinstalls, or on newly set up computers.
Status 30Not a MicroKernel file
The file's header is damaged, or the file isn't what the application expects. It sounds fatal, but these files can often be repaired or their records recovered.
Status 84 / 85Record or file is locked
Another user or a stuck process is holding a lock. When it keeps happening, the cause is often a crashed workstation, a stale connection, or a network setting.
Status 94Permission error
Windows share or folder permissions are blocking access to the data. This is very common after a server upgrade, a domain change, or a new user account.
Status 161User count license limit reached
The engine thinks too many users are connected. Common causes are stale sessions, a license that didn't move with the server, or an expired license key.
Status 3012 / 3014Engine not accessible or not found
The workstation's client configuration doesn't match where the engine actually lives. These codes show up constantly after moving the database to a new server.
Seeing a different status code? Send it to us along with what the software is and when the error appears.
03 — What we do
Keep it running, get the data out, or plan the move.
Most clients need one of these three things. Some need all three, in that order.
Keep it running
Stabilize the system you have today, so the business stops holding its breath every time the server reboots.
- Move to current Windows Server
- Virtualize old hardware
- Fix engine & license errors
- Backups you can restore
Get your data out
Pull records out of Btrieve and Pervasive files into formats your new tools can actually read.
- Export to CSV, Excel or SQL
- Rebuild missing record layouts
- Clean & map for new systems
- Verified record counts
Plan the move
When it's time to replace the old system, avoid a risky weekend cutover that takes the business down with it.
- Document what the system does
- Run old & new side by side
- VB6 changes during transition
- Ongoing on-call support
04 — Who you'll work with
Not something we learned for a sales page.
I'm Dmitry, and I run ID Communications. For about 15 years I've been responsible for VB6 applications and Pervasive/Btrieve databases that businesses rely on every day.
I maintain the code, support the businesses that use it, and manage the servers it runs on. I've carried these systems through Windows Server upgrades and onto virtualized infrastructure. This isn't a technology I learned for a sales page. I've kept it running in production, with real businesses depending on it.
Experience15 years supporting Pervasive/Btrieve and VB6 systems in production
HowSecure remote sessions, no travel costs
WhoThe person you talk to is the person doing the work
05 — How it works
No open-ended hourly bills.
You'll know the scope and the price before any real work begins.
Step 01
Tell us what you're running
Use the form below. The software name, what it does for you, and what's going wrong is plenty to start.
Step 02
Fixed-price assessment
We connect remotely, review the system, and tell you in plain terms where things stand and what the options are.
Step 03
Written quote
You get a clear scope and a fixed price for the work. You decide if and when to go ahead.
Step 04
Work and handoff
We do the work and leave you documentation, so you're never stuck in the same spot again.
06 — FAQ
What people usually ask first.
Do you need to be local?
No. Nearly all of this work happens over a secure remote session. We're based in Georgia and work with businesses anywhere in the U.S.
Do I need the original source code?
Not to get your data out. In most cases the database files are enough, even when the data dictionary files are missing. Source code only matters if the application itself needs to change.
Which versions do you work with?
Older Btrieve engines, Pervasive SQL (Pervasive.SQL and PSQL v8 through v13) and current Actian Zen, plus Visual Basic 6 applications, on Windows Server 2008 through 2025, physical or virtual.
What does it cost?
Every job starts with a fixed-price assessment. After that you get a fixed quote for the work itself, so there are no surprises.
Can you be our on-call person for the old system?
Yes. Some clients prefer a monthly support arrangement, so there's always someone to call when the old system acts up.
Do you handle the rest of our IT too?
We can. ID Communications also does IT consulting, networking, hosting and websites. Plenty of legacy projects turn up other things worth fixing along the way.
07 — Let's talk
Tell us about your system. We'll tell you where it stands.
A few sentences is plenty. The software name, roughly how old it is, and what's going wrong. You'll hear back from a real person, not a ticket queue.
Based inSavannah, Georgia
ServingBusinesses across the U.S., remotely
Reply timeUsually within one business day