Introduction
If you've ever seen an "Error Reading File" message or dealt with unexplained data corruption inside Pivoten, there's a good chance your server environment was quietly working against you — and you had no idea.
Over the years, we've worked with many of you to troubleshoot these issues, applying settings and workarounds to keep things stable. But after years of monitoring, testing, and supporting clients across a wide range of server environments, we've made a definitive decision: Pivoten no longer supports SMB2 or higher server environments.
This isn't a decision we made lightly. It's one we made to protect your data.
What Is SMB2 and Why Does It Matter?
SMB (Server Message Block) is the protocol Windows uses to handle file sharing across a network. When Microsoft introduced SMB2, they made a significant change to how data gets written to your server.
Instead of writing data to disk immediately, Windows began holding writes in a cache and committing them to disk later — a process called opportunistic locking or write caching. For most modern applications, this is invisible and harmless.
For Pivoten, it's a problem.
Pivoten is built around keeping your data accurate and reliable, which means it depends on writes happening immediately and in the correct sequence. When Windows intercepts that process through SMB2 caching, it can lead to corrupted indexes, out-of-sync records, and the frustrating errors some of you have experienced firsthand.
The workarounds we've recommended over the years — adjusted cache settings, registry tweaks, network configuration changes — have helped, but they are not a permanent or guaranteed fix. The root cause has always been the same.
Our New Support Stance
Effective immediately, Pivoten does not support installations running on SMB2 or higher server environments.
We know this is a meaningful change for some of you. But continuing to support these environments means continuing to expose your data to risk — and that's not something we're willing to do.
If you are not running Pivoten on a shared network server, this change does not affect you. You can continue using Pivoten exactly as you always have.
If you are running a shared server environment with SMB2 or higher, it's time to talk.
The Better Path: Pivoten Cloud
The cleanest, most reliable way to run Pivoten has always been our hosted cloud environment — and now it's the recommended path for every client running in a networked server setup.
Here's why Pivoten Cloud works where local SMB environments struggle:
- No SMB caching. Data writes happen the way Pivoten expects — immediately and in sequence.
- No server maintenance. No Windows updates are quietly changing behavior behind the scenes.
- Access from anywhere. Work from the office, home, or the field without VPN headaches.
- Your data is protected. Built-in backups and redundancy keep your records safe.
- Always current. You're always running the latest version of Pivoten without lifting a finger.
For clients who have dealt with recurring data errors, the move to the cloud is often the moment everything just... works.
What Should You Do Next?
If you're unsure whether your current setup uses SMB2 or higher, your IT administrator can check your server's SMB configuration. If you're running SMB2, SMB3, or aren't sure, now is the right time to make the move.
Our support team is ready to walk you through the transition. It's simpler than you might expect, and we'll be with you every step of the way.
👉 Contact our support team today to get started with Pivoten Cloud.
Your data deserves a setup that works with Pivoten — not against it.
Comments