Seven Bentley SELECT Server Headaches (and What Each One Teaches You)
Every IT team that has managed Bentley SELECT Server has a few war stories. The laptop that wouldn't activate in a site office in the middle of nowhere. The server nobody remembered installing. The invoice that made the finance director go quiet.
These stories are useful. Each one points to a habit worth building, whether you're still running SELECTserver for legacy versions or you've already moved to Bentley's Subscription Entitlement Service (SES).
So grab a coffee. Here are seven of the most common headaches, and what they teach.
1. "It says it's not activated, but it was fine yesterday"
The classic. A user opens a Bentley application and it complains about activation.
Nine times out of ten, the cause is boring. The machine's License Management Tool is pointing at the wrong server name. Maybe someone reimaged the PC with an old setup. Maybe the in-house server moved and nobody updated the pointer. Maybe a laptop has been offline for weeks.
The lesson: Keep a short, written record of your license setup. Server name, whether it's deployed or Bentley-hosted, and how new machines should be configured. It sounds obvious. Most firms don't have it until after the third time this happens.
2. The mystery server under someone's desk
Older firms sometimes discover a SELECTserver installed years ago by a person who has long since left. It's still running. It's still reporting usage. Nobody knows the admin password.
This isn't rare. SELECTserver has been around a long time and stayed backward compatible all the way to MicroStation/J, which came out in 1998. That kind of longevity means installs outlive the people who set them up.
The lesson: Inventory your licensing infrastructure the same way you'd inventory servers or network gear. If it's critical to how your firm gets billed, someone current should own it.
3. "Why is our bill higher this quarter?"
This one hurts the most.
SELECTserver was built on Trust Licensing. It logged usage instead of blocking people, so your team could go over the number of licenses you owned without anyone noticing at the time. Bentley's pooled billing looks at peaks, so a few busy days can shape the whole quarter.
The frustrating part is that most firms only find out after the invoice arrives.
The lesson: Don't wait for Bentley to tell you how much you used. Track it yourself, as close to real time as you can. SES helps with this through near real-time monitoring and alerts. For a fuller picture across all your engineering software, a dedicated platform like OpenLM can show Bentley usage next to your Autodesk, Esri, and other license data, so peaks don't come as a surprise.
4. The licenses that went on holiday
SELECTserver let users check out licenses for offline work. Very handy for site engineers. Less handy when those licenses stay checked out long after the trip ends.
I heard about one firm where a license had been checked out for most of a year. The laptop holding it had been sent for repair and quietly replaced. The license was technically still out there, attached to a machine sitting in a storeroom.
The lesson: Review checked-out licenses on a regular schedule. Monthly is plenty for most firms. Keep check-out periods sensible, and make returning a license part of the process when laptops are swapped or retired.
5. Old and new versions fighting for attention
During a move to SES, some users run both an older SELECTserver-licensed version and a newer SES-enabled version. Bentley says these can coexist on the same machine, which is helpful. But it can also lead to double counting when someone opens both to compare files.
One firm noticed its peak usage rising in the middle of a migration even though nobody new had joined. It turned out to be this exact behavior.
The lesson: During any migration, watch usage more closely than usual. A tool that pulls data from both systems into one view makes overlaps easy to spot. OpenLM supports Bentley along with dozens of other license managers, which makes it a natural fit for firms juggling more than one licensing setup at once.
6. Contractors who never quite left
Engineering firms bring in contractors all the time. They get a machine, the software, and access. Then the project ends and they leave.
What often doesn't leave is the software install, or under SES, the account access. That machine gets reassigned, someone opens Bentley software occasionally, and it adds to usage. Or an old account keeps access it shouldn't have.
The lesson: Add licensing to your offboarding checklist. Uninstall what isn't needed. Remove account access. Write it down once, then follow it every time.
7. Guessing at renewal time
Renewal comes around. Someone asks, "How many licenses do we need next year?" And the honest answer is, "Uh, the same as last year, plus a few?"
That's how firms end up overbuying. Or underbuying and paying overages.
The lesson: Bring real data to renewal conversations. You want at least six months of usage history per product, with peaks, averages, and some sense of how much was idle time. With that in hand, you can make a confident case to keep, cut, or add licenses. It also gives you a stronger footing when you talk to your Bentley account manager.
The common thread
Read back through these seven and you'll notice something. Almost none of them are really technical failures. They're visibility failures.
SELECTserver did what it was designed to do. It kept people working and recorded what they used. The trouble came when nobody inside the firm was looking at those records until it was too late.
SES improves that picture a lot for Bentley products. Combine it with a broader license management tool like OpenLM and you get something better still: one place to see what your engineers actually use, across every vendor, before anyone gets a surprise invoice.
A few quick wins to try this month
Write down your Bentley license server setup in one short document.
Check for licenses that have been checked out longer than 30 days.
Pull last quarter's peak usage for your top three Bentley products.
Add licensing steps to your contractor offboarding list.
None of these take long. All of them make the next headache a little smaller.