If you’ve ever clicked on an email in Outlook and watched the ndMail prediction screen come back with “The server could not display your filing locations” instead of your usual list of workspaces, you’re not alone. This ndMail prediction screen error is one of the ones I get asked about most, and it almost always shows up at the worst possible moment — when you’re trying to file something and move on.
Here’s what it means and what to do about it.
The Good News: Nothing Is Lost
Your email is fine. It’s still sitting in your mailbox exactly where it was.
Nothing got filed to the wrong place, nothing got deleted, and no half-saved copy is floating around in NetDocuments. The prediction screen is a suggestion box, not the filing engine. When it fails, all you lose is the shortcut.
What the ndMail Prediction Screen Error Actually Means
Every time you click on an email, ndMail sends a small request up to NetDocuments: here’s the sender, the recipients, and the subject line — where does this one probably belong? NetDocuments looks at your recent filing history, works out the most likely Workspaces, and sends a short list back down. That whole round trip happens in the second or two between you clicking the email and the prediction screen drawing itself.
When that round trip doesn’t finish, ndMail has nothing to put in the list. So it tells you the server couldn’t display your filing locations.
The honest answer as to why it didn’t finish is: usually nothing. It’s random. A request times out, a connection hiccups, your session token picks that moment to refresh, Outlook is busy doing six other things. Click a different email and the prediction screen is fine again.
NetDocuments Says This One Is on the Server
You don’t have to take my word for it. NetDocuments’ own documentation on this message is unusually direct:
This notification appears when the issue happens on the server or on getting the predictions call.
That’s the whole explanation. The failure is on the other end of the request — either the server itself or the predictions call that goes to it. It is not your Outlook profile, it is not something you clicked, and it is not your firm’s cabinet setup.
Their stated resolution is equally short: restore your connection and try again. If it keeps happening, escalate it with a trace log and the time the error occurred.
That’s not a satisfying answer, but it’s the accurate one.
When You Should Actually Worry
There’s a real difference between an occasional annoyance and an actual problem, and it’s worth knowing which one you have before you spend any time on it:
- A few times a week, on random emails – Normal. Annoying, but normal. Click past it.
- On every email, all day, for you alone – Try the two steps below.
- On every email, for everyone in the firm – That’s not your computer. Tell your IT team or your consultant, and include the time it started.
The Fix: Work Through These in Order
Step 1: Click a Different Email, Then Click Back
The fastest fix and the one that works most of the time. Click any other message in your inbox, wait a second, then click back on the original. ndMail re-runs the prediction, and the second attempt usually succeeds.
Step 2: Close Outlook and Reopen It
If clicking around doesn’t clear it, close Outlook completely — all the way out, not just the window — and open it again. This forces ndMail to re-establish its connection to NetDocuments from scratch.
You Can Still Save the Email with ndSave
Don’t sit and wait for the prediction screen to come back. The prediction screen being down doesn’t stop you from filing the email — it only stops NetDocuments from guessing where it goes.
Use ndSave and pick the Workspace yourself, exactly the way you would for an email ndMail guessed wrong on. The email saves normally, it lands in the same place, and nobody downstream can tell the difference.
Prediction is a convenience. It is not the only way in.
Still Seeing It?
If the ndMail prediction screen error is following your firm around every day rather than showing up once in a while, that’s usually a sign something in the ndMail configuration or the network path needs a real look. We can go through your setup and tell you which one it is — usually in a single call.
Schedule a free consultation at go.oncehub.com/optconsult.
I’ve guided over 550 law firms across the United States and Canada through NetDocuments implementations since 2010, specializing in firms with 10 to 150 users.