{"title":"Some known issues in Business Central on-premises","url":"https://jonas-paprotka.de/docs/dev-itpro/upgrade/known-issues/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/known-issues, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/known-issues","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Provides an overview of the known issues that can affect Business Central installation or upgrade.","date":"2025-09-19","meta":{"topic":"troubleshooting-known-issue"},"outline":[{"level":1,"title":"Some known issues in Business Central on-premises","slug":"some-known-issues-in-business-central-on-premises","at":0,"chars":47331},{"level":2,"title":"Business Central admin shell modules fail in PowerShell 7 remote sessions","slug":"business-central-admin-shell-modules-fail-in-powershell-7-remote-sessions","at":551,"chars":1584},{"level":3,"title":"Problem","slug":"problem","at":720,"chars":1093},{"level":3,"title":"Workaround","slug":"workaround","at":1813,"chars":322},{"level":2,"title":"Evaluation company creation fails in some country/region versions","slug":"evaluation-company-creation-fails-in-some-countryregion-versions","at":2135,"chars":854},{"level":3,"title":"Problem","slug":"problem-1","at":2230,"chars":374},{"level":3,"title":"Workaround","slug":"workaround-1","at":2604,"chars":385},{"level":2,"title":"Web server components installation fails because of missing .NET Core Hosting Bundle","slug":"web-server-components-installation-fails-because-of-missing-net-core-hosting-bundle","at":2989,"chars":1763},{"level":3,"title":"Problem","slug":"problem-2","at":3077,"chars":1003},{"level":3,"title":"Possible cause","slug":"possible-cause","at":4080,"chars":357},{"level":3,"title":"Workaround","slug":"workaround-2","at":4437,"chars":315},{"level":2,"title":"Renamed tables and fields in subscription billing extension cause synch errors on upgrade","slug":"renamed-tables-and-fields-in-subscription-billing-extension-cause-synch-errors-on-upgrade","at":4752,"chars":13721},{"level":3,"title":"Problem","slug":"problem-3","at":4877,"chars":624},{"level":3,"title":"Workaround","slug":"workaround-3","at":5501,"chars":504},{"level":3,"title":"Renamed tables and fields","slug":"renamed-tables-and-fields","at":6005,"chars":9442},{"level":4,"title":"Table 8051 \"Service Contract Setup\" -> \"Subscription Contract Setup\"","slug":"table-8051-service-contract-setup---subscription-contract-setup","at":6120,"chars":327},{"level":4,"title":"Table 8004 \"Contract Price Update Line\" -> \"Sub. Contr. Price Update Line\"","slug":"table-8004-contract-price-update-line---sub-contr-price-update-line","at":6447,"chars":550},{"level":4,"title":"Table 8001 \"Contract Renewal Line\" -> \"Sub. Contract Renewal Line\"","slug":"table-8001-contract-renewal-line---sub-contract-renewal-line","at":6997,"chars":890},{"level":4,"title":"Table 8002 \"Planned Service Commitment\" -> \"Planned Subscription Line\"","slug":"table-8002-planned-service-commitment---planned-subscription-line","at":7887,"chars":479},{"level":4,"title":"Table 8019 \"Contract Analysis Entry\" -> \"Sub. Contr. Analysis Entry\"","slug":"table-8019-contract-analysis-entry---sub-contr-analysis-entry","at":8366,"chars":715},{"level":4,"title":"Table 8062 \"Customer Contract Line\" -> \"Cust. Sub. Contract Line\"","slug":"table-8062-customer-contract-line---cust-sub-contract-line","at":9081,"chars":510},{"level":4,"title":"Table 8065 \"Vendor Contract Line\" -> \"Vend. Sub. Contract Line\"","slug":"table-8065-vendor-contract-line---vend-sub-contract-line","at":9591,"chars":508},{"level":4,"title":"Table 8066 \"Customer Contract Deferral\" -> \"Cust. Sub. Contract Deferral\"","slug":"table-8066-customer-contract-deferral---cust-sub-contract-deferral","at":10099,"chars":379},{"level":4,"title":"Table 8072 \"Vendor Contract Deferral\" -> \"Vend. Sub. Contract Deferral\"","slug":"table-8072-vendor-contract-deferral---vend-sub-contract-deferral","at":10478,"chars":377},{"level":4,"title":"Table 8010 \"Imported Customer Contract\" -> \"Imported Cust. Sub. Contract\"","slug":"table-8010-imported-customer-contract---imported-cust-sub-contract","at":10855,"chars":208},{"level":4,"title":"Table 8008 \"Imported Service Object\" -> \"Imported Subscription Header\"","slug":"table-8008-imported-service-object---imported-subscription-header","at":11063,"chars":221},{"level":4,"title":"Table 8009 \"Imported Service Commitment\" -> \"Imported Subscription Line\"","slug":"table-8009-imported-service-commitment---imported-subscription-line","at":11284,"chars":709},{"level":4,"title":"Table 8007 \"Overdue Service Commitments\" -> \"Overdue Subscription Line\"","slug":"table-8007-overdue-service-commitments---overdue-subscription-line","at":11993,"chars":572},{"level":4,"title":"Table 8068 \"Sales Service Commitment\" -> \"Sales Subscription Line\"","slug":"table-8068-sales-service-commitment---sales-subscription-line","at":12565,"chars":406},{"level":4,"title":"Table 8069 \"Sales Service Comm. Archive\" -> \"Sales Sub. Line Archive\"","slug":"table-8069-sales-service-comm-archive---sales-sub-line-archive","at":12971,"chars":261},{"level":4,"title":"Table 8057 \"Service Object\" -> \"Subscription Header\"","slug":"table-8057-service-object---subscription-header","at":13232,"chars":256},{"level":4,"title":"Table 8059 \"Service Commitment\" -> \"Subscription Line\"","slug":"table-8059-service-commitment---subscription-line","at":13488,"chars":661},{"level":4,"title":"Table 8073: Service Commitment Archive -> Subscription Line Archive","slug":"table-8073-service-commitment-archive---subscription-line-archive","at":14149,"chars":690},{"level":4,"title":"Table \"Service Comm. Package Line\" -> \"Subscription Package Line\"","slug":"table-service-comm-package-line---subscription-package-line","at":14839,"chars":212},{"level":4,"title":"Table 8016 \"Usage Data Subscription\" -> \"Usage Data Supp. Subscription\"","slug":"table-8016-usage-data-subscription---usage-data-supp-subscription","at":15051,"chars":396},{"level":3,"title":"Only fields renamed","slug":"only-fields-renamed","at":15447,"chars":3026},{"level":4,"title":"Table 8070 \"Subscription Billing Cue\"","slug":"table-8070-subscription-billing-cue","at":15471,"chars":475},{"level":4,"title":"Table 8061 \"Billing Line\"","slug":"table-8061-billing-line","at":15946,"chars":580},{"level":4,"title":"Table 8064 \"Billing Line Archive\"","slug":"table-8064-billing-line-archive","at":16526,"chars":588},{"level":4,"title":"Table 8003 \"Price Update Template\"","slug":"table-8003-price-update-template","at":17114,"chars":229},{"level":4,"title":"Table 8017 \"Generic Import Settings\"","slug":"table-8017-generic-import-settings","at":17343,"chars":140},{"level":4,"title":"Table 8006 \"Usage Data Billing\"","slug":"table-8006-usage-data-billing","at":17483,"chars":401},{"level":4,"title":"Table 8018 \"Usage Data Generic Import\"","slug":"table-8018-usage-data-generic-import","at":17884,"chars":134},{"level":4,"title":"Only tables renamed","slug":"only-tables-renamed","at":18018,"chars":455},{"level":2,"title":"Removed tables and fields in the E-Document Core extension cause synchronization errors on upgrade","slug":"removed-tables-and-fields-in-the-e-document-core-extension-cause-synchronization-errors-on-upgrade","at":18473,"chars":790},{"level":3,"title":"Problem","slug":"problem-4","at":18594,"chars":241},{"level":3,"title":"Workaround","slug":"workaround-4","at":18835,"chars":428},{"level":2,"title":"Number series creation doesn't work in Business Central 25.2 on-premises","slug":"number-series-creation-doesnt-work-in-business-central-252-on-premises","at":19263,"chars":359},{"level":3,"title":"Problem","slug":"problem-5","at":19358,"chars":223},{"level":3,"title":"Workaround","slug":"workaround-5","at":19581,"chars":41},{"level":2,"title":"Different installation path in 25.2","slug":"different-installation-path-in-252","at":19622,"chars":483},{"level":2,"title":"Installation fails because PowerShell 7 is already installed","slug":"installation-fails-because-powershell-7-is-already-installed","at":20105,"chars":27226},{"level":3,"title":"Problem","slug":"problem-6","at":20220,"chars":499},{"level":3,"title":"Possible cause","slug":"possible-cause-1","at":20719,"chars":26612}],"text":"# Some known issues in Business Central on-premises\nThis article describes some known issues in Business Central versions. These issues can affect installation, upgrade, and various operations of Business Central on-premises.\n> NOTE\n> The article doesn't include a complete list of known issues. Instead, it addresses some common issues that you might experience or might consider when upgrading to a version. If you're aware of issues that aren't in this article, or you'd like more help, consult Resources for Help and Support<../help-and-support>.\n## Business Central admin shell modules fail in PowerShell 7 remote sessions\n> Applies to: Business Central v28.0 on‑premises and container-based environments on Docker\n### Problem\nPowerShell 7 has a known issue where Business Central Administration Shell modules fail to load in remote PowerShell sessions. This issue affects both on‑premises deployments and container-based environments.\n On‑premises deployments\n  You get an error when you try to import the .Business Central Administration Shell modules in a remote session. Because the module fails to load, dependent cmdlets can't be invoked.\n Container-based environments\n  You get errors when running BCContainerHelper management functions such as `Restart-BcContainer`, `Get-BcContainerAppInfo`, and `Publish-BcContainerApp`. These functions rely on Business Central admin modules, which BCContainerHelper invokes through a remote PowerShell session to the container.\nDepending on your environment, you might get errors similar to the following:\n`Import-Module: Could not load file or assembly '<name , version, culture, public key token>'. Uncaught exception during type initialization.`\n`The term '<cmdlet name>' is not recognized as a name of a cmdlet, function, script file, or executable program.`\n### Workaround\nUse Windows PowerShell 5.1 when running Business Central Administration Shell and BCContainerHelper modules in remote sessions. See Business Central admin shell<../administration/administration-shell> and Running a container-based development environment<../developer/devenv-running-container-development>.\n## Evaluation company creation fails in some country/region versions\n> Applies to: 27.3 online\n### Problem\nWhen you create an evaluation company in the following countries/regions: AU, CA, DE, DK, ES, FR, GB, IT, NZ, US, the process fails with an error in the Setup Status column, and an error similar to the following is logged on the Job Queue Entries page:\n```\nDocument Record ID must have a value in E-Document: Document Entry No=7. It cannot be zero or empty.\n```\n### Workaround\nBefore creating a new evaluation company in any of the affected countries/regions, set the work date to January 1, 2026. You can do this from the My Settings page by updating the Work Date field. See Set work date</ui-change-basic-settings#work-date>.\nIf the company creation has already failed, delete the failed company, set the work date as described, and try again.\n## Web server components installation fails because of missing .NET Core Hosting Bundle\n### Problem\nWhen you install the Web Server components on a machine that already includes the .NET 6.0 SDK or Core Runtime, you get the following error:\nWeb Server Components Fatal error during installation\nThe installation log, accessible via a link in the error dialog box, includes entries such as:\n```\nRegistrySearch: Id = 'IISASPNETInstalled', searching for registry key value.\n                Id = 'IISASPNETInstalled', Registry value not found. Key = 'SOFTWARE\\Microsoft\\InetStp\\Components', Value = 'ASPNET'\n\nRegistrySearch: Id = 'IISNETFXInstalled', searching for registry key value.\n                Id = 'IISNETFXInstalled', Registry value not found. Key = 'SOFTWARE\\Microsoft\\InetStp\\Components', Value = 'NetFxExtensibility'\n\nRegistrySearch: Id = 'WebComponentsPrerequisitesInstalled', searching for registry key value.\n                Id = 'WebComponentsPrerequisitesInstalled', Registry key not found. Key = 'SOFTWARE\\Microsoft\\Microsoft Dynamics NAV\\260\\Web Components Prerequisites'\n```\n### Possible cause\nIf the .NET 6.0 SDK or Core Runtime is installed before the IIS (Internet Information Services) feature is enabled on Windows. The system doesn't register the components needed to host ASP.NET Core applications in IIS correctly. See Troubleshoot and debug ASP.NET Core projects<https://learn.microsoft.com/aspnet/core/test/troubleshoot>.\n### Workaround\n1. Uninstall Business Central.\n1. Download and install the ASP.NET Core 6.0 Runtime (v6.0.36) - Windows Hosting Bundle from Download .NET 6.0<https://dotnet.microsoft.com/en-us/download/dotnet/6.0/> or select this link<https://go.microsoft.com/fwlink/?linkid=2336162>.\n1. Reinstall Business Central.\n## Renamed tables and fields in subscription billing extension cause synch errors on upgrade\n> Applies to: Upgrade from 25.X\n### Problem\nSeveral tables and fields are #renamed-tables-and-fields in the subscription billing extension for version 26. These changes prevent you from syncing the extension to the tenant database when upgrading to version 26.0 or later. When you try to sync the extension, you get errors like the following:\n`Table 8001 Contract Renewal Line :: The table 'Contract Renewal Line' cannot be located. Removing tables is not allowed unless they are temporary or are being moved by migration to another app.`\n`Table 8003 Price Update Template :: The field 'Contract Filter' cannot be located. Removing fields is not allowed.`\n### Workaround\nIf no custom application code depends on the renamed tables and fields, force sync the extension using the `-Mode ForceSync` parameter:\n```powershell\nSync-NAVApp -ServerInstance $NewBcServerInstance -Name \"Subscription Billing\" -version $NewVersion -Mode ForceSync\n```\nForce sync might cause data loss if custom code depends on the renamed tables and fields in the extension. To prevent data loss, refactor the custom code to match the extension's latest database schema before upgrading.\n### Renamed tables and fields\nThis section lists the new names for tables and fields. (ff) indicates a flow field.\n#### Table 8051 \"Service Contract Setup\" -> \"Subscription Contract Setup\"\nField no.|Original field name|New field name\n2|Customer Contract Nos.|Cust. Sub. Contract Nos.\n3|Vendor Contract Nos.|Vend. Sub. Contract Nos.\n4|Service Object Nos.|Subscription Header No.\n6|Serv. Start Date for Inv. Pick|Sub. Line Start Date Inv. Pick\n#### Table 8004 \"Contract Price Update Line\" -> \"Sub. Contr. Price Update Line\"\nField no.|Original field name|New field name\n2|Service Object No.|Subscription Header No.\n3|Service Commitment Entry No.|Subscription Line Entry No.\n7|Contract No.|Subscription Contract No.\n8|Contract Description|Sub. Contract Description\n9|Service Object Description|Subscription Description\n10|Service Commitment Description|Subscription Line Description\n13|Additional Service Amount|Additional Amount\n14|Old Service Amount|Old Amount\n15|New Service Amount|New Amount\n#### Table 8001 \"Contract Renewal Line\" -> \"Sub. Contract Renewal Line\"\nField no.|Original field name|New field name\n1|Service Object No.|Subscription Header No.\n2|Service Commitment Entry No.|Subscription Line Entry No.\n10|Linked to Ser. Comm. Entry No.|Linked to Sub. Line Entry No.\n11|Linked to Contract No.|Linked to Sub. Contract No.\n12|Linked to Contract Line No.|Linked to Sub. Contr. Line No.\n13|Contract No.|Subscription Contract No.\n14|Contract Line No.|Subscription Contract Line No.\n(ff) 101|Service Object Description|Subscription Description\n(ff) 102|Service Commitment Description|Subscription Line Description\n(ff) 103|Service Start Date|Subscription Line Start Date\n(ff) 104|Service End Date|Subscription Line End Date\n(ff) 106|Service Amount|Amount\n(ff) 108|Planned Serv. Comm. exists|Planned Sub. Line exists\n201|Agreed Serv. Comm. Start Date|Agreed Sub. Line Start Date\n#### Table 8002 \"Planned Service Commitment\" -> \"Planned Subscription Line\"\nField no.|Original field name|New field name\n1|Service Object No.|Subscription Header No.\n3|Package Code|Subscription Package Code\n6|Service Start Date|Subscription Line Start Date\n7|Service End Date|Subscription Line End Date\n14|Service Amount|Amount\n19|Contract No.|Subscription Contract No.\n26|Service Object Customer No.|Subscription Customer No.\n27|Contract Line No.|Subscription Contract Line No.\n#### Table 8019 \"Contract Analysis Entry\" -> \"Sub. Contr. Analysis Entry\"\nField no.|Original field name|New field name\n2|Service Object No.|Subscription Header No.\n3|Package Code|Subscription Package Code\n6|Service Start Date|Subscription Line Start Date\n7|Service End Date|Subscription Line End Date\n14|Service Amount|Amount\n19|Contract No.|Subscription Contract No.\n27|Contract Line No.|Subscription Contract Line No.\n33|Service Amount (LCY)|Amount (LCY)\n39|Quantity Decimal|Quantity\n1005|Service Commitment Entry No.|Subscription Line Entry No.\n8007|Service Object Source Type|Sub. Header Source Type\n8008|Service Object Source No.|Sub. Header Source No.\n8010|Service Object Description|Subscription Description\n#### Table 8062 \"Customer Contract Line\" -> \"Cust. Sub. Contract Line\"\nField no.|Original field name|New field name\n1|Contract No.|Subscription Contract No.\n100|Service Object No.|Subscription Header No.\n101|Service Commitment Entry No.|Subscription Line Entry No.\n102|Service Object Description|Subscription Description\n106|Service Commitment Description|Subscription Line Description\n(ff) 109|Service Obj. Quantity Decimal|Service Object Quantity\n(ff) 200|Planned Serv. Comm. exists|Planned Sub. Line exists\n#### Table 8065 \"Vendor Contract Line\" -> \"Vend. Sub. Contract Line\"\nField no.|Original field name|New field name\n1|Contract No.|Subscription Contract No.\n100|Service Object No.|Subscription Header No.\n101|Service Commitment Entry No.|Subscription Line Entry No.\n102|Service Object Description|Subscription Description\n106|Service Commitment Description|Subscription Line Description\n(ff) 109|Service Obj. Quantity Decimal|Service Object Quantity\n(ff) 200|Planned Serv. Comm. exists|Planned Sub. Line exists\n#### Table 8066 \"Customer Contract Deferral\" -> \"Cust. Sub. Contract Deferral\"\nField no.|Original field name|New field name\n2|Contract No.|Subscription Contract No.\n5|Contract Type|Subscription Contract Type\n22|Contract Line No.|Subscription Contract Line No.\n23|Service Object Description|Subscription Description\n24|Service Commitment Description|Subscription Line Description\n#### Table 8072 \"Vendor Contract Deferral\" -> \"Vend. Sub. Contract Deferral\"\nField no.|Original field name|New field name\n2|Contract No.|Subscription Contract No.\n5|Contract Type|Subscription Contract Type\n22|Contract Line No.|Subscription Contract Line No.\n23|Service Object Description|Subscription Description\n24|Service Commitment Description|Subscription Line Description\n#### Table 8010 \"Imported Customer Contract\" -> \"Imported Cust. Sub. Contract\"\nField no.|Original field name|New field name\n2|Contract No.|Subscription Contract No.\n7|Contract Type|Subscription Contract Type\n#### Table 8008 \"Imported Service Object\" -> \"Imported Subscription Header\"\nField no.|Original field name|New field name\n2|Service Object No.|Subscription Header No.\n100|Service Object created|Subscription Header created\n#### Table 8009 \"Imported Service Commitment\" -> \"Imported Subscription Line\"\nField no.|Original field name|New field name\n2|Service Object No.|Subscription Header No.\n3|Service Commitment Entry No.|Subscription Line Entry No.\n5|Contract No.|Subscription Contract No.\n6|Contract Line No.|Subscription Contract Line No.\n7|Contract Line Type|Sub. Contract Line Type\n8|Package Code|Subscription Package Code\n11|Service Start Date|Subscription Line Start Date\n12|Service End Date|Subscription Line End Date\n19|Service Amount|Amount\n28|Service Amount (LCY)|Amount (LCY)\n(ff) 37|Quantity Decimal|Quantity\n100|Service Commitment created|Subscription Line created\n104|Contract Line created|Sub. Contract Line created\n#### Table 8007 \"Overdue Service Commitments\" -> \"Overdue Subscription Line\"\nField no.|Original field name|New field name\n4|Contract No.|Subscription Contract No.\n5|Contract Description|Sub. Contract Description\n6|Service Commitment Description|Subscription Line Description\n10|Service Amount|Amount\n12|Contract Type|Subscription Contract Type\n14|Service Start Date|Subscription Line Start Date\n15|Service End Date|Subscription Line End Date\n16|Service Object No.|Subscription Header No.\n17|Service Object Description|Subscription Description\n19|Quantity Decimal|Quantity\n#### Table 8068 \"Sales Service Commitment\" -> \"Sales Subscription Line\"\nField no.|Original field name|New field name\n20|Service Amount|Amount\n21|Service Comm. Start Formula|Sub. Line Start Formula\n22|Agreed Serv. Comm. Start Date|Agreed Sub. Line Start Date\n31|Package Code|Subscription Package Code\n50|Service Object No.|Subscription Header No.\n51|Service Commitment Entry No.|Subscription Line Entry No.\n#### Table 8069 \"Sales Service Comm. Archive\" -> \"Sales Sub. Line Archive\"\nField no.|Original field name|New field name\n20|Service Amount|Amount\n21|Service Comm. Start Formula|Sub. Line Start Formula\n22|Agreed Serv. Comm. Start Date|Agreed Sub. Line Start Date\n#### Table 8057 \"Service Object\" -> \"Subscription Header\"\nField no.|Original field name|New field name\n28|Quantity Decimal|Quantity\n(ff) 95|Archived Service Commitments|Archived Sub. Lines exist\n(ff) 200|Planned Serv. Comm. exists|Planned Sub. Lines exist\n#### Table 8059 \"Service Commitment\" -> \"Subscription Line\"\nField no.|Original field name|New field name\n1|Service Object No.|Subscription Header No.\n3|Package Code|Subscription Package Code\n6|Service Start Date|Subscription Line Start Date\n7|Service End Date|Subscription Line End Date\n14|Service Amount|Amount\n19|Contract No.|Subscription Contract No.\n(ff) 26|Service Object Customer No.|Sub. Header Customer No.\n27|Contract Line No.|Subscription Contract Line No.\n33|Service Amount (LCY)|Amount (LCY)\n(ff) 39|Quantity Decimal|Quantity\n(ff) 200|Planned Serv. Comm. exists|Planned Sub. Line exists\n(ff) 8010|Service Object Description|Subscription Description\n#### Table 8073: Service Commitment Archive -> Subscription Line Archive\nField no.|Original field name|New field name\n2|Service Object No.|Subscription Header No.\n5|Package Code|Subscription Package Code\n8|Service Start Date|Subscription Line Start Date\n9|Service End Date|Subscription Line End Date\n16|Service Amount|Amount\n21|Contract No.|Subscription Contract No.\n(ff) 28|Service Object Customer No.|Sub. Header Customer No.\n29|Contract Line No.|Subscription Contract Line No.\n35|Service Amount (LCY)|Amount (LCY)\n41|Serial No. (Service Object)|Serial No. (Sub. Header)\n42|Quantity Decimal (Service Ob.)|Quantity (Sub. Header)\n96|Variant Code (Service Object)|Variant Code (Sub. Header)\n#### Table \"Service Comm. Package Line\" -> \"Subscription Package Line\"\nField no.|Original field name|New field name\n1|Package Code|Subscription Package Code\n12|Service Comm. Start Formula|Sub. Line Start Formula\n#### Table 8016 \"Usage Data Subscription\" -> \"Usage Data Supp. Subscription\"\nField no.|Original field name|New field name\n6|Service Object No.|Subscription Header No.\n7|Service Commitment Entry No.|Subscription Line Entry No.\n21|Connect to Service Object No.|Connect to Sub. Header No.\n22|Connect to SO Method|Connect to Sub. Header Method\n23|Connect to SO at Date|Connect to Sub. Header at Date\n### Only fields renamed\n#### Table 8070 \"Subscription Billing Cue\"\nField no.|Original field name|New field name\n(ff) 2|Customer Contract Invoices|Cust. Sub. Contr. Invoices\n(ff) 3|Customer Contract Credit Memos|Cust. Sub. Contr. Credit Memos\n(ff) 4|Vendor Contract Invoices|Vend. Sub. Contr. Invoices\n(ff) 5|Vendor Contract Credit Memos|Vend. Contr. Credit Memos\n(ff) 6|Serv. Comm. wo Cust. Contract|Sub. L. wo Cust. Sub. Contract\n(ff) 7|Serv. Comm. wo Vend. Contract|Sub. L. wo Vend. Sub. Contract\n#### Table 8061 \"Billing Line\"\nField no.|Original field name|New field name\n20|Contract No.|Subscription Contract No.\n21|Contract Line No.|Subscription Contract Line No.\n30|Service Object No.|Subscription Header No.\n31|Service Commitment Entry No.|Subscription Line Entry No.\n(ff) 32|Service Object Description|Subscription Description\n33|Service Commitment Description|Subscription Line Description\n34|Service Start Date|Subscription Line Start Date\n35|Service End Date|Subscription Line End Date\n39|Service Obj. Quantity Decimal|Service Object Quantity\n52|Service Amount|Amount\n#### Table 8064 \"Billing Line Archive\"\nField no.|Original field name|New field name\n20|Contract No.|Subscription Contract No.\n21|Contract Line No.|Subscription Contract Line No.\n30|Service Object No.|Subscription Header No.\n31|Service Commitment Entry No.|Subscription Line Entry No.\n(ff) 32|Service Object Description|Subscription Description\n33|Service Commitment Description|Subscription Line Description\n34|Service Start Date|Subscription Line Start Date\n35|Service End Date|Subscription Line End Date\n39|Service Obj. Quantity Decimal|Service Object Quantity\n52|Service Amount|Amount\n#### Table 8003 \"Price Update Template\"\nField no.|Original field name|New field name\n4|Contract Filter|Subscription Contract Filter\n5|Service Commitment Filter|Subscription Line Filter\n6|Service Object Filter|Subscription Filter\n#### Table 8017 \"Generic Import Settings\"\nField no.|Original field name|New field name\n4|Create Subscriptions|Create Supplier Subscriptions\n#### Table 8006 \"Usage Data Billing\"\nField no.|Original field name|New field name\n5|Contract No.|Subscription Contract No.\n6|Contract Line No.|Subscription Contract Line No.\n7|Service Object No.|Subscription Header No.\n(ff) 8|Service Object Description|Subscription Description\n9|Service Commitment Entry No.|Subscription Line Entry No.\n10|Service Commitment Description|Subscription Line Description\n#### Table 8018 \"Usage Data Generic Import\"\nField no.|Original field name|New field name\n6|Service Object No.|Subscription Header No.\n#### Only tables renamed\nOriginal table name|New table name\nContract Type|Subscription Contract Type\nCustomer Contract|Customer Subscription Contract\nVendor Contract|Vendor Subscription Contract\nItem Serv. Commitment Package|Item Subscription Package\nItem Templ. Serv. Comm. Pack.|Item Templ. Sub. Package\nService Commitment Template|Sub. Package Line Template\nService Commitment Package|Subscription Package\nUsage Data Customer|Usage Data Supp. Customer\n## Removed tables and fields in the E-Document Core extension cause synchronization errors on upgrade\n> Applies to: 26.2\n### Problem\nSeveral tables and fields are removed in the E-Document Core extension in version 26.2. The removed tables and fields prevent you from synchronizing the extension to the tenant database when you upgrade to version 26.2 or later.\n### Workaround\nThese tables and fields were never publicly released and were used internally for development in private preview, so no code path has a dependency on them. To resolve the issue, use the ForceSync parameter to remove the deleted columns in the database schema, as the following example shows.\n```al\nSync-NAVApp -ServerInstance $NewBcServerInstance -Name \"E-Document Core\" -version $NewVersion -Mode ForceSync\n\n```\n## Number series creation doesn't work in Business Central 25.2 on-premises\n> Applies to: 25.2\n### Problem\nIf you try to create a number series, you get the following error:\n`The filter on Series Code was altered by an event subscriber. This is a programming error. Please contact your partner to resolve this issue.`\n### Workaround\nUpgrade to 25.3 or later.\n## Different installation path in 25.2\n> Applies to: 25.2\n25.2 includes internal database schema changes with the following consequences:\n New platform version 25.2 instead of 25.0.\n Different installation path than 25.0 and 25.1. Instead of using folder '250', components are installed in folder '252', for example: `C:\\Program Files\\Microsoft Dynamics 365 Business Central\\252`.\nFuture updates like 25.3 and 25.4 will also use platform number '25.2' and installation folder '252'.\n## Installation fails because PowerShell 7 is already installed\n> Applies to: Installation of version 24.0 or 24.1\n### Problem\nWhen you try to install the Business Central Server using the setup.exe program of version 24.1, the installation fails with the following error:\n```\nMicrosoft Dynamics 365 Business Central Build NNNNN\nError Report\n\nSetup Components\nThe component was rolled back.\n\nPowerShell 7\nPowerShell 7 for the commandlets\nFatal error during installation.\n```\nIn the installation log or Windows Event Viewer, you get an error message similar to `A newer version of PowerShell is already installed`.\n### Possible cause\nWindows PowerShell 7.4.2 or later is already installed on the Business Central Server machine. The Business Central setup.exe will automatically install PowerShell 7.4.2, but it should only do so if the machine doesn't have PowerShell installed or it has a version earlier than 7.4.2. In version 24.1, instead of skipping the PowerShell installation when it should, the setup.exe tries to install PowerShell but fails.\n> TIP\n> To find out what PowerShell version is running on your machine, open PowerShell and enter the following prompt:\n```powershell\n> PWSH.exe\n> ```\n\n### Workaround\n\nUninstall PowerShell 7 from the Business Central Server machine, then run setup.exe again.\n\n[Learn how to uninstall an app or program in Windows.](https://support.microsoft.com/en-us/windows/uninstall-or-remove-apps-and-programs-in-windows-4b55f974-2cc6-2d2b-d092-5905080eaf98)\n\n## Error importing control add-in files from the client\n\n> Applies to: Upgrade to version 23.3\n\n### Problem\n\nWhen you try to import a control add-in file client from the **Control Add-ins** page in the client by using the **Control Add-in Resource** > **Import**, you get the following error:\n\n```\nCan't open file`\n[URL] can't open files in this folder because it contains system files`\n```\n\n`[URL]` is the URL of your Business Central web client, for example, `http://localhost:8080`.\n\n### Workaround\n\nYou have two options to work around this issue:\n\n- Use the Set-NAVAddin cmdlet of the Business Central Administration Shell as described in [Upgrade control add-ins](/dev-itpro/upgrade/upgrading-cumulative-update-v23#controladdins).\n- If you want to use the Business Central web client, then copy the files to another folder on your PC, like Documents or Downloads, and try again.\n\n## Removed table fields in the Czech (CZ) base application cause sync errors\n\n> Applies to: Upgrade to version 23\n\n### Problem\n\nAs part of the delocalization process of the Czech (CZ) version of Business Central, Microsoft moved Czech-specific functionality into separate applications. As a result, the following fields have been removed and the primary keys modified in the Czech (CZ) base application, version 23:\n\n|Table|Field|\n|-|-|\n|1251 \"Text-to-Account Mapping\"|11700 \"Text-to-Account Mapping (Code[10])|\n|1252 \"Bank Pmt. Appl. Rule\"|11700 \"Bank Pmt. Appl. Rule Code\" (Code[10])|\n\nThese changes can lead to the following errors when you try to synchronize the base application with the tenant during upgrade:\n\n```ps\nSync-NAVApp : Table 1251 Text-to-Account Mapping :: The field 'Text-to-Account Mapping Code' cannot be located. Removing fields is not allowed.\nTable 1251 Text-to-Account Mapping :: Changing fields for the key 'Key1' is not allowed. Previous list: 'Text-to-Account Mapping Code', 'Line No.', new List: 'Line No.'.\nTable 1252 Bank Pmt. Appl. Rule :: The field 'Bank Pmt. Appl. Rule Code' cannot be located. Removing fields is not allowed.\nTable 1252 Bank Pmt. Appl. Rule :: Changing fields for the key 'Key1' is not allowed. Previous list: 'Bank Pmt. Appl. Rule Code', 'Match Confidence', 'Priority', new List: 'Match Confidence', 'Priority'.\n```\n### Workaround\nIf you're upgrading from version 22, use the Sync-NavApp cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.apps.management/sync-navapp> to synchronize the base application in the ForceSync mode during upgrade, for example:\n```ps\nSyncNavApp -ServiceInstance <BC 23 server instance> -Name \"Base Application\" -Version <23 version number> -Mode ForceSync\n```\nIf you're upgrading from version 21 or earlier, the workaround is slightly different. First, ensure that no duplicate records will exist in either table 1251 \"Text to Account Mapping\" or table 1252 \"Bank Payment Application Rule\" after upgrade. To do this, complete one of the following tasks before you upgrade to version 23:\n Manually delete any duplicate records in either of the tables, or\n Upgrade to the latest version 22 that's compatible<upgrade-v14-v15-compatibility> with the version 23 you're upgrading to. With version 22, the necessary data modifications to handle duplicate records are included as part of the upgrade procedures.\nOnce you completed either of these tasks, upgrade to version 23 as usual. Don't forget to synchronize the base application using the ForceSync mode with the Sync-NavApp cmdlet.\n## Web server components fatal error during installation on Azure virtual machine (VM)\n> Applies to: Version 20 and 21\n### Problem\nWhen you try to install the Business Central Web Server components using setup.exe on an Azure VM running Windows Server, the following error occurs:\nWeb Server Components\nFatal error during installation\n### Possible cause\nThis error typically occurs on a VM where the Business Central Web Server hasn't been installed before. It happens because setup is trying to install Windows Server Hosting and Microsoft .NET Core Runtime on the VM but they're already installed, causing a conflict.\n### Workaround\nUninstall Windows Server Hosting and Microsoft .NET Core Runtime from the VM, then run setup.exe again.\n## Users can't sign in to the web client after upgrade to 19.0\n> Applies to: Upgrade to 19.0\n### Problem\nIf the Business Central Web Server is configured for Windows authentication, users might not be able to sign in. In the event viewer, you see the following exception:\n```\nSystem.PlatformNotSupportedException: Operation is not supported on this platform.\n   at System.Func`2.BeginInvoke(T arg, AsyncCallback callback, Object object)\n   at Microsoft.Dynamics.Nav.Client.ConnectionEstablisher.TestSpnSettings(ConnectFailedEventArgs connectFailedArgs)\n```\n### Workaround\nSet the UnknownSpnHint setting in the navsettings.json file of Business Central Web Server by following the guidelines at in Configuring Business Central Web Server instance<../administration/configure-web-server#spn>.\n## Tables changed to temporary might prevent synchronizing new base application version\n> Applies to: Upgrade from version 17.X or earlier to any later version\n### Problem\nStarting in version 18, the following base application tables are now temporary tables, as specified by the ../developer/properties/devenv-tabletype-property. Depending on how you're using these tables, this change may affect the upgrade from version 17 or earlier to a later version.\nTable|File\nTable 49 \"Invoice Post. Buffer\"|InvoicePostBuffer.Table.al\nTable 265 \"Document Entry\"|DocumentEntry.Table.al\nTable 269 \"G/L Account Net Change\"|GLAccountNetChange.Table.al\nTable 338 \"Entry Summary\"|EntrySummary.Table.al\nTable 491 \"Parallel Session Entry\"|ParallelSessionEntry.Table.al\nTable 1670 \"Option Lookup Buffer\"|OptionLookupBuffer.Table.al\nTable 1754 \"Field Content Buffer\"|FieldContentBuffer.Table.al\nTable 6305 \"Power BI Chart Buffer\"|PowerBIChartBuffer.Table.al\nTable 6302 \"Power BI Report Buffer\"|PowerBIReportBuffer.Table.al\nTable 7330 \"Bin Content Buffer\"|BinContentBuffer.Table.al\n### Impact\nWith this change, these tables must be empty to complete the upgrade. If a table isn't empty, you can't synchronize the new version of the base application. In this case, you get an error stating that the table can't be deleted from the database because it contains data, for example:\n`Cannot delete the Document Entry table from the database because it contains data.`\nSo if there are records in these tables, or the application includes custom code that stores nontemporary records to these tables, you have to make some changes before you can run the upgrade.\n### Workaround\nBefore you upgrade, either move the records to new tables or delete the records from the tables. Also, rewrite the custom application code that's stores the nontemporary records in these base application tables to use other tables.\n## NavUserPassword authentication doesn't work after upgrade to version 18\n> Applies to: Upgrade to 18.0-18.2\n### Problem\nWhen you upgrade to version 18 from an earlier major version, authentication that's based on NavUserPassword credential type no longer works for existing users. Passwords aren't considered valid anymore.\n### Impact\nWhen users try to sign in to Business Central, they get an error, similar to the following message:\n`The specified user name or password is not correct, or you do not have a valid user account in Dynamics 365 Business Central`\nIn event viewer, you see the following error:\n`Your user name <name> or password is incorrect, or you do not have a valid account in Dynamics 365 Business Central.`\n### Workaround\nTo work around this issue, activate the EnableLegacyIterationCount feature switch by completing these steps.\n1. Run the Business Central Administration Shell as an administrator.\n See Run Business Central Administration Shell<../administration/administration-shell>.\n2. Run the following command to determine which feature switches are enabled:\n ```powershell\n Get-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName \"FeatureSwitchOverrides\"\n ```\n Replace`$ServerInstanceName` with the Business Central Server instance name.\n3. Depending on what was returned in step 2, run one of the following commands to enable the EnableLegacyIterationCount feature switch:\n  If the nothing was returned, run the following command:\n   ```powershell\n   Set-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName \"FeatureSwitchOverrides\" -KeyValue \"EnableLegacyIterationCount\"\n   ```\n  If one or more entries were returned, run the following command:\n   ```powershell\n   Set-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName \"FeatureSwitchOverrides\" -KeyValue ((Get-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName \"FeatureSwitchOverrides\") + (\",EnableLegacyIterationCount\"))\n   ```\n4. Restart the server.\n ```powershell\n Restart-NAVServerInstance -ServerInstance $ServerInstanceName\n ```\n### Notes\n Activating the EnableLegacyIterationCount feature switch is only required if you have existing users that are set up with passwords for the NavUserPassword authentication. So if you want to set up NavUserPassword from scratch after upgrade, you don't need to enable the EnableLegacyIterationCount feature switch for it to work.\n When the EnableLegacyIterationCount feature switch is enabled, you can create new users with passwords and assign or change passwords of existing users.\n You can activate and deactivate the EnableLegacyIterationCount feature switch for the deployment at any time, but be aware of the following behavior:\n   Passwords that were assigned to users when the EnableLegacyIterationCount feature switch was activated, won't work when the EnableLegacyIterationCount feature switch is deactivated.\n   Passwords that were assigned to users when the EnableLegacyIterationCount feature switch was deactivated, won't work when the EnableLegacyIterationCount feature switch is activated.\n    In these cases, as an administrator, you'll have to assign new passwords to the affected users.\n This feature switch is activated per server instance, so it pertains to all tenants in a multitenant deployment.\n## NavUserPassword authentication performance after upgrade to version 18\n> Applies to: Upgrade to 18.X\n### Problem\nWhen you upgrade to version 18 from an earlier major version, authentication that's based on the NavUserPassword credential type takes longer than it did in previous versions. This reason is that the password algorithm has been updated in version 18. The extra time it takes per authentication isn't noticeable to a normal user. But in a solution that has a heavy authentication load, for example from multiple and repeated web service calls, the extra time might be significant.\n### Workaround\nOne solution is to activate the EnableLegacyIterationCount feature switch, as described in the previous issue<#legacy>. This feature switch sets the server instance to use the same authentication algorithm used in version 17. Another solution is to change the authentication method to either OAuth or Web service access key. With these authentication methods, the password isn't stored in Business Central in a hashed format.\n## Data upgrades fail because of missing $system fields in the Permission and Permission Set tables\n> Applies to: Upgrade to 18.0-18.1\n### Problem\nWhen you upgrade to version 18 from an earlier major version, and the Business Central Server instance is configured to use permission sets from data<upgrade-permissions#continue-using-the-permission-sets-defined-as-data>, the data upgrade fails because some system fields aren't added to Permission and Permission Set tables.\n### Impact\nWhen you run the Start-NAVDataUpgrade or Start-NAVAppDataUpgrade against the base application, the cmdlet fails. You'll get an error message that the following columns in the Permission Set table are missing or invalid:\n `$systemCreatedAt`\n `$systemCreatedBy`\n `$systemModifiedAt`\n `$systemModifiedBy`\n### Workaround\nUpgrade to version 18.2<https://support.microsoft.com/help/5004062> or later.\n## Package Microsoft .NET Core Windows Server Hosting failed with error\n> Applies to: All versions up to and including version 18.0.\n### Problem\nWhen you install Business Central on premises, installation may fail with the error `Package Microsoft .NET Core Windows Server Hosting failed with error`, or with error code 1638, when the installer attempts to install prerequisite components.\nThis problem occurs when a version of Windows Server Hosting newer than version 2.1.14 is installed on the server, because Business Central installer attempts to install version 2.1.14.\nThe issue only occurs when the currently installed version is a newer minor version, not a newer major version of Windows Server Hosting.\n### Impact\nInstallation will fail and will be rolled back.\n### Workaround\nThe issue can be resolved in different ways:\n Manually install Windows Server Hosting version 3 or later before you install Business Central components.\n Uninstall Windows Server Hosting from your server before you install Business Central\n Use the installer from Business Central version 18.1 or later. In these versions, Business Central installer skips installing Windows Server Hosting components if it determines that newer Windows Server Hosting components are already installed.\n## Primary key mismatch between converted tables in local 14 versions and Microsoft Base Application\n> Applies to: Upgrade from 14.18-14.X to 15.12-15.X, 16.7-16.X, or 17.1-17.X\n### Problem\nIn some local versions, new table objects were added as part of a minor update. In version 14, which is still C/AL based, the primary keys of these tables are unnamed. When you convert the tables from CAL to AL using the txt2AL tool, primary keys are given the name Key1. In version 15, 16, and 17, which is fully AL-based, these tables have been moved to Microsoft base application extension, and the primary keys have the name PK. This difference can cause problems when you upgrade to use the Microsoft Base Application because it introduces breaking changes.\nThe affected local versions and tables include:\nLocal 14 version|Tables\nCH|<ul><li>QRBill Buffer</li><li>QRBill Billing Detail</li><li>QRBill Billing Info</li><li>QRBill Layout QRBill</li><li>QRBill Setup</li><li>VAT Reg. No. Srv. Template</li><li>VAT Registration Log Details</li></ul>\nNA|<ul><li>VAT Reg. No. Srv. Template</li><li>VAT Registration Log Details</li></ul>\n> NOTE\n> You don't experience this problem with table objects in other Microsoft extensions because the primary keys are named KEY1.\n### Impact\nIf you don't resolve this conflict, you'll experience problems when upgrading a customized version 14 (C/AL) application to the Microsoft Base Application.\nFor example, consider the following articles:\n Upgrading Customized C/AL Application to Microsoft Base Application Version 16<upgrade-to-microsoft-base-app>\n Upgrading Customized C/AL Application to Microsoft Base Application Version 17<upgrade-to-microsoft-base-app-v17>\nDuring this upgrade process, you'll create two versions of an extension referred to as the table migration extension. This extension is used for transferring ownership of existing tables in the database to other extensions. The first version contains table objects. The second version contains a migration.json file instead of the table objects. When you try synchronize the second version of the table migration extension (Task 13.5<upgrade-to-microsoft-base-app#syncfinal> or Task 12.6<upgrade-to-microsoft-base-app-v17#syncfinal>), you'll get the following errors for each affected table:\n`Table <table name> :: The previous primary key 'Key1' cannot be located. Changing the primary key is not allowed.`\n`Table <table name> :: Introducing a new key 'PK' as the primary key is not allowed. Please make the key 'Key1' the primary key again.`\n### Workaround\nTo avoid these errors, after converting the version 14 tables to AL, rename instances of the primary key `Key1 ` to PK in the affected table objects before building your extensions.\n If you're following the upgrade articles listed above, do this change as part of Task 2. If you've already published the first table migration extension with the wrong key names, restore the databases and go through the upgrade again, starting from Task 2.\n Also make these changes if you're only doing a technical upgrade. This way, you won't run into problems later if eventually uptake the Microsoft Base Application.\nFor each affected table object, do the following steps:\n1. Open the \\.al file.\n2. Locate the primary key definition. For example:\n ```al\n keys\n {\n     key(Key1; \"Primary key\")\n     {\n         Clustered = true;\n     }\n }\n ```\n3. Change the name from Key1 to PK. For example:\n ```al\n keys\n {\n     key(PK; \"Primary key\")\n     {\n         Clustered = true;\n     }\n }\n ```\n## Enum type fields not transferred as part of schema migration between extensions\n> Applies to: Upgrade to 15.3-15.11 and 16.0-16.4\n### Problem\nThe table migration feature fails to transfer data from a table object to a table extension object that introduces an enumeration.\n> NOTE\n> The table migration feature was introduced in version 15.3. See Migrating Tables and Fields Between Extensions<../developer/devenv-migrate-table-fields>.\n### Impact\nYou'll experience this issue in the following scenarios:\n Upgrading a customized version 14 solution to version 15 or 16\n Migrating data from one extension to another.\nThe issue occurs when synchronizing extensions. You get an error similar to one of the following messages:\n`Sync-NAVApp : The metadata object Enum <ID> was not found.`\n`Message App Sync Exception -- Microsoft.Dynamics.Nav.Types.NavMetadataNotFoundException: The metadata object Enum <ID> was not found.`\n### Workaround\n If you're upgrading from version 14, use 15.12 (or later) or 16.5 (or later) as the target version.\n If you're migrating data between extensions, upgrade your solution to 15.12 (or later) or 16.5 (or later).\n## $systemModifiedAt fields in tables not populated during upgrade\n> Applies to: Upgrade from 14.0-14.X to 17.X\n### Problem\nBusiness Central version 17 introduced data audit<../developer/devenv-table-system-fields#audit> fields on tables. When you upgrade from version 15 or 16, the $systemModifiedAt field is populated with values from field 5120 ModifiedOn in table 5151 Integration Record. However, this mapping doesn't work in a version 14-to-17 upgrade.\n### Impact\nWhen upgrading from version 14 to version 17, the $systemModifiedAt field will be blank.\n### Workaround\nUpgrade to version 15 or 16 before upgrading to version 17.\n## Wrong .NET assemblies for external connected services\n> Applies to: Upgrade to 16.5\n### Problem\nVersion 16.5 includes the wrong .NET 4.5 assemblies for connecting to external services that use OAuth, like Common Data Service.\n### Impact\nIn the Business Central client, you can set up external service connections from the Service Connections page. When you try to set up a connection, it fails because Business Central can't obtain an access token for connecting to the service.\nIn the client, you get an error similar to the following message:\n`Failed to acquire authorization token for <service>.`\nIn the event log, you see an error similar to the following message:\n`Could not load file or assembly 'Microsoft.Identity.Client, Version=4.14.0, Culture=neutral, PublicToken=0a613f4dd989e8e' or one of its dependencies. The located assembly's manifest location does not match the assembly reference.`\n### Workaround\nThere are two workarounds for this issue:\n1. Upgrade to 16.6 or later.\n2. Install the required assemblies:\n 1. Go to https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0<https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0>.\n 2. Under Info, select Download package.\n 3. Extract the contents of the nupkg file to a folder.\n  There are different ways to extract the content of nupkg file. An easy way is to change the file extension from \\.nupkg to \\.zip. Then, extract the files like you would do with any .zip file.\n 4. Copy the files in the \\lib\\net45 folder to the Service folder of the Business Central Server installation. Replace the existing files when prompted.\n  The default folder is C:\\Program Files\\Microsoft Dynamics 365 Business Central\\160\\Service.\n 5. Restart the Business Central Server instance.\n## Help Server for India preview missing files\n> Applies to: Upgrade to 17.X\n### Problem\nThe installation media (DVD) is missing required HTML files for the Help Server.\n### Impact\nThe Help Server installation fails.\n### Workaround\nInstall Help Server without the HTML files for local functionality, then pick up the content from GitHub instead.\n## Business Central Server Administration tool doesn't work for multitenant server instances\n> Applies to: Upgrade to 17.0-17.1\nIf a Business Central Server instance is configured as a multitenant instance, you can't manage the tenants by using the Business Central Server Administration tool.\n### Impact\nWhen you try to use the Tenant node in the Business Central Server Administration tool, you get a message: The MMC has detected an error in the snap-in and will unload it. This message is followed by:\n`FX:{ba484c42-ed9a-0170-925f-23e64e686fd0}`\n`Value cannot be null.`\n`Parameter name: objectToValidate at Microsoft.ManagementConsole.BaseCollection.OnValidate(Object objectToValidate, Boolean testForDuplicate) at System.Collections.CollectionBase.System.Collections.IList.Add(Object value)    at CallSite.Target(Closure , CallSite , NodeSubItemDisplayNameCollection , Object )    at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid2[T0,T1](CallSite site, T0 arg0, T1 arg1)    at Microsoft.Dynamics.Nav.ManagementUI.NavTenantsListView.RefreshWithNodeStateChangedCheck(IList1 tenants, ResultNodeCollection currentResultNodes)    at Microsoft.Dynamics.Nav.ManagementUI.NavTenantsListView.RefreshCore()    at Microsoft.Dynamics.Nav.ManagementUI.NavTenantsListView.OnInitialize(AsyncStatus status)    at Microsoft.ManagementConsole.View.ProcessRequest(Request request)    at Microsoft.ManagementConsole.ViewMessageClient.ProcessRequest(Request request)    at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)    at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)    at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()    at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)`\n### Workaround\nUse the Business Central Administration Shell. This error is fixed in later updates.\n## Sync-NAVApp error: Parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong\n> Applies to: Upgrade from 14.X\n### Problem\nYou get the following error when running Sync-NAVApp cmdlet on the base application:\n```powershell\nSync-NAVApp : The following SQL error was unexpected:\n\nEither the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.\n\nEither the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.\n\nCaution: Changing any part of an object name could break scripts and stored procedures.\n```\n### Workaround\nThis occurs when a key fails to get renamed. To fix the problem, identify the key that fails to get renamed, for example, by using the event log or SQL profiler. Then, disable the key by using Dynamics NAV Development Environment.\n## Business Central Server instance fails to start after changing a port number directly in the CustomSettings.config file\n> Applies to: Upgrade to 21.x\n### Problem\nYou get errors in the Event Log similar to the following errors when trying to start the Business Central Server instance after changing a port number directly in its CustomSettings.config file:\n Message (HttpSysException): Failed to start service with CLR type Microsoft.Dynamics.Nav.Service.AspNetCore.AspNetCoreApiHost, API type ClientApi and address http://gc1662:8085/BC210/client.\n Failed to start service with CLR type Microsoft.Dynamics.Nav.Service.AspNetCore.AspNetCoreApiHost, API type ClientApi and address\n The service MicrosoftDynamicsNavServer$BC210 failed to start. This could be caused by a configuration error. Detailed error information: Microsoft.AspNetCore.Server.HttpSys.HttpSysException (0x80004005): Access is denied\n Type: Microsoft.AspNetCore.Server.HttpSys.HttpSysException; Message: Access is denied\n### Impact\nAfter upgrading to version 21.x, you notice that the Business Central Server Administration tool is no longer available, because it has been removed in version 21.x. If you then try to update certain port numbers (for example, ClientServicesPort ) directly in the server instance's CustomSettings.config file, you may get the errors described above when you try to start the server instance.\n### Workaround\nAvoid updating the CustomSetting.config file directly. Instead, use the Business Central Administration Shell with the Set-NAVServerConfiguration cmdlet<https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/set-navserverconfiguration>. This will automatically grant the required Namespace Reservation permissions for the relevant port.\nAlternatively, you could grant the required Namespace Reservation permissions manually for the relevant port by running the appropriate NETSH command in an administrator command prompt on the Business Central Server machine, for example:\n```\nnetsh http add urlacl url=http://+:<PORT NUMBER>/<BC SERVICE NAME>/ user=\"<BC SERVICE ACCOUNT>\"\n```\n## Related information\nupgrading-to-business-central"}