# Business Central Could Not Open the Company: Causes and Fixes > Source: https://netray.co/erp-help/business-central-could-not-open-the-company-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System dynamics ## Erp Microsoft Dynamics 365 Business Central ## Module Companies / users / licensing ## Query business central could not open the company ## Alternate Queries - business central cannot open company - business central company not found - business central user cannot access company - business central company does not exist ## Applies To Business Central online and on-premises. Exact message wording varies by version and client, so match the cause, not the text. ## Steps ### Work through the usual causes **Items:** - Check 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). - Open 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). - Check 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. - Open the Companies page as an admin and confirm the company still exists with that exact name. A renamed or deleted company breaks bookmarked links. - Remove 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. - Reset the user's default company in User Personalization if it points to a company that was removed. - On-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. - If 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. ## Sections ### User, license and permissions **Body:** 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 **Body:** 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. **Code:** https://businesscentral.dynamics.com//?company= # Example encoding for a name with spaces and a comma CRONUS%20USA%2C%20Inc. ### On-premises: server, authentication and data **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Why can one user open the company but another cannot? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms business central could not open the company, business central cannot open company, business central company not found, business central user permissions company, business central license user state, business central company parameter url, business central default company, business central user personalization --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json