Error fixMicrosoft Dynamics 365 Business CentralCompanies / users / licensing

Business Central Could Not Open the Company: Causes and Fixes

Error
business central could not open the company

Also searched as

  • business central cannot open company
  • business central company not found
  • business central user cannot access company
  • business central company does not exist

Short answer

When Business Central cannot open a company, the cause is almost always one of: the user lacks access or a license, the user record is disabled, the company name in the URL or the user's default company no longer exists, or the environment or server is in a bad state. Check the user, the company list and the URL in that order.

Applies to: Business Central online and on-premises. Exact message wording varies by version and client, so match the cause, not the text.

Work through the usual causes

  1. 1Check whether it is one user or everyone. If everyone, check environment state in the admin center (online) or the server instance and SQL connection (on-premises).
  2. 2Open the Users page as an administrator. Confirm the user exists, State is Enabled, and a license is assigned in the Microsoft 365 admin center (online).
  3. 3Check permission sets for the user. A user without any permission set, or lacking access to basic system tables, can fail to load a company. Assign a baseline set such as D365 BASIC plus role sets.
  4. 4Open the Companies page as an admin and confirm the company still exists with that exact name. A renamed or deleted company breaks bookmarked links.
  5. 5Remove the company parameter from the URL, or use the company picker. A stale company= value (check URL encoding for spaces and commas) is a frequent cause.
  6. 6Reset the user's default company in User Personalization if it points to a company that was removed.
  7. 7On-premises, confirm the server instance is running, the user is mapped to the right authentication type, and look in the Windows event log for the underlying error.
  8. 8If a company was just copied, renamed or restored, wait for the operation to finish and try again, then check for a failed state in the admin center.

User, license and permissions

Online, a user needs a Business Central license assigned in the Microsoft 365 admin center and must appear in Business Central Users with State Enabled. Users are created automatically on first sign-in only if they have a license and the tenant is configured that way, otherwise an administrator creates them. A missing or expired license produces a sign-in or open-company failure that looks like a company problem.

Permissions come from permission sets, groups and, online, license-based default sets. If the permission sets were changed recently, or an extension removed access to a base table, the user may fail to load. Compare with a working user who has the same role and check effective permissions rather than guessing.

Company missing, renamed or in the wrong state

The Companies page lists what exists in the environment. Company names can include spaces and punctuation, and bookmarked URLs carry the name, so after a rename every bookmark with the old company= value fails. Deleting a company that someone still has as default has the same effect.

Environment operations such as copy, restore or update can leave a company unavailable until they finish. If an environment shows a failed or suspended state in the admin center, the fix is at environment level, with support from Microsoft, not at user level.

https://businesscentral.dynamics.com/<tenant>/<environment>?company=<URL-encoded company name>

# Example encoding for a name with spaces and a comma
CRONUS%20USA%2C%20Inc.

On-premises: server, authentication and data

On-premises check the Business Central Server instance, the web server instance and SQL connectivity first. Then check the credential type: Windows, NavUserPassword or AAD, and whether the user exists in the User table for that tenant. Multi-tenant installations also need the tenant ID in the URL.

If many users are affected right after maintenance, look for a failed upgrade, an extension that did not synchronize, or a database restored without its tenant mounted. The service event log normally names the real error behind the generic open-company failure.

Try it here, free

Business Central License Cost Calculator

Open full tool

Estimate Business Central monthly and annual subscription cost from your user mix and your own price per user, with a chart of cost growth.

Common pitfalls

  • !Debugging the company when the real cause is a disabled user or missing license.
  • !Bookmarking URLs with a company name and then renaming the company.
  • !Forgetting to URL-encode spaces and commas in a manual company parameter.
  • !Deleting or renaming a company that users have as their default company.
  • !Granting SUPER to make the error go away instead of finding the missing baseline permission.
  • !Ignoring environment state in the admin center when several users fail together.

How an ERP-grounded AI assistant handles this

Access triage is a lookup: user state, license, permission sets, company list, environment state. A private assistant with read access to those administrative records can walk through the checklist for a named user and report what differs from a working colleague. Granting or changing access remains a deliberate admin action.

See ERPray

Frequently asked questions

Why can one user open the company but another cannot?

The difference is almost always the user record: a disabled state, a missing license, missing permission sets, or a default company that no longer exists. Compare the failing user with a working user on the Users page and in User Personalization.

Does a missing license cause could not open the company?

It can. Online users must have a Business Central license assigned in the Microsoft 365 admin center. Without one, sign-in or company load can fail even if the Business Central user record exists and is enabled.

I renamed the company and now my links fail, why?

The URL carries the company name in the company parameter. After a rename the old value no longer matches. Open the environment without the parameter, pick the company, and update bookmarks and any integration that builds the URL.

What should I check on-premises?

Check that the server instance and SQL Server are running, that the user exists with the correct authentication type, that the tenant is mounted, and read the Windows event log for the underlying error behind the generic message.

Related

Error fix

Business Central Error Messages: What They Mean and How Errors Are Handled

Most Business Central errors come from a few AL patterns: TestField and FieldError for missing or invalid field values, Error for rule violations, and permission or locking messages from the platform. Developers can customize them with Error and ErrorInfo, collect many errors at once, or catch them with TryFunction. If the whole service is unreachable, check service health and environment state first.

Error fix

Fixing "You do not have the following permissions on TableData (table): (permission)" in Business Central AL

This runtime error means the current user's assigned permission sets do not grant the required Insert, Modify, Delete, Read, or Execute right on that specific table. It is most common right after installing or updating a custom AL extension, because Business Central checks object-level permissions even for tables an extension owns.

How-to

Upgrade to Business Central 25: How to Update SaaS and On-Premises

Business Central version 25 is the 2024 release wave 2. For SaaS you schedule or accept the update from the Business Central admin center after testing in a sandbox. On-premises you install the new server, convert the database, then synchronize and upgrade each extension. The real work is making every extension compile and upgrade cleanly on the new version first.

Error fix

Business Central: "Another user has modified the record after you retrieved it"

Business Central uses optimistic concurrency. Every record carries a row version, and a write is rejected if the stored version no longer matches what you read. For users, refresh the page and redo the edit. For developers, read and modify in the same short transaction, use LockTable or the right read isolation, and send an If-Match ETag from API clients.

Error fix

Fixing "Cannot create a record in (table). The record already exists" in D365 F&SCM data entity imports

This is the standard kernel duplicate-key exception, thrown when the Data Management Framework tries to insert a staging row into a target table whose unique or alternate key already matches an existing record. It almost always means the entity's insert-vs-update logic did not recognize the target row as an update, not that you have a true accidental duplicate in your source file.

Error fix

Fixing "There are currently no batch servers available for processing" in D365 F&SCM

This message means the batch framework cannot find any AOS instance flagged as a batch server and available for the batch group the job is assigned to. The fix is almost always in server configuration (System administration > Servers) or batch group assignment, not in the batch job itself.

AI for ERP

AI for Dynamics 365 Business Central, on-premises or SaaS, beyond Copilot

AI for Business Central beyond Copilot: grounded question answering over BC's data via OData and APIs, for on-premises and SaaS tenants alike.

Stuck on Microsoft Dynamics 365 Business Central?

Talk to engineers who work inside Microsoft Dynamics 365 Business Central every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Comparisons

Software

TermsDynamics 365 Business CentralOData (Open Data Protocol)