![]() If the nothing was returned, run the following command: Set-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName "FeatureSwitchOverrides" -KeyValue "EnableLegacyIterationCount" Replace $ServerInstanceName with the Business Central Server instance name.ĭepending on what was returned in step 2, run one of the following commands to enable the EnableLegacyIterationCount feature switch: Run the following command to determine which feature switches are enabled: Get-NAVServerConfiguration -ServerInstance $ServerInstanceName -KeyName "FeatureSwitchOverrides" Run the Business Central Administration Shell as an administrator.įor more information, see Start Business Central Administration Shell. To workaround this issue, activate the EnableLegacyIterationCount feature switch by completing these steps. Your user name or password is incorrect, or you do not have a valid account in Dynamics 365 Business Central. In event viewer, you'll see the following error: The specified user name or password is not correct, or you do not have a valid user account in Dynamics 365 Business Central When users try to sign in to Business Central, they'll get an error, similar to the following message: Passwords aren't considered valid anymore. When you upgrade to version 18 from an earlier major version, authentication that's based on NavUserPassword credential type no longer works for existing users. NavUserPassword authentication doesn't work after upgrade to version 18 Also, rewrite the custom application code that's stores the non-temporary records in these base application tables to use other tables. ![]() Workaroundīefore you upgrade, either move the records to new tables or delete the records from the tables. So if there are records in these tables, or the application includes custom code that stores non-temporary records to these tables, you'll have to make some changes before you can run the upgrade. In this case, you'll get an error stating that the table cannot be deleted from the database because it contains data, for example:Ĭannot delete the Document Entry table from the database because it contains data. If a table isn't empty, you can't synchronize the new version of the base application. With this change, these tables must be empty to complete the upgrade. Depending on how you're using these tables, this change may affect the upgrade from version 17 or earlier to a later version. Starting in version 18, the following base application tables are now temporary tables, as specified by the TableType property. Tables changed to temporary may prevent synchronizing new base application versionĪpplies to: Upgrade from version 17.X or earlier to any later version Problem Set 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. In the event viewer, you'll see the following exception: System.PlatformNotSupportedException: Operation is not supported on this platform.Īt System.Func`2.BeginInvoke(T arg, AsyncCallback callback, Object object)Īt .ConnectionEstablisher.TestSpnSettings(ConnectFailedEventArgs connectFailedArgs) If the Business Central Web Server is configured for Windows authentication, users may not be able to sign in. Users can't sign in to the web client after upgrade to 19.0 NET Core Runtime from the VM, then run setup.exe again. Uninstall Windows Server Hosting and Microsoft. NET Core Runtime on the VM but they're already installed, causing a conflict. ![]() ![]() It happens because setup is trying to install Windows Server Hosting and Microsoft. This error will typically occur on a VM where the Business Central Web Server hasn't been installed before. When you try to install the Business Central Web Server components using setup.exe on a Azure VM running Windows Server, the following error occurs:įatal error during installation Possible cause Web server components fatal error during installation on Azure virtual machine (VM) If you're aware of issues that aren't in this article, or you'd like more help, see Resources for Help and Support. Instead, it addresses some common issues that you might experience or might consider when upgrading to a version. The article doesn't include a complete list of known issues.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |