|
|
Dynamics 365 Business Central
|
|
|
Your Business Central failed to update
|
|
|
|
Business Central failed to be updated. The reason for the failure is because one or more of the installed extensions failed to update successfully. Review the error information below and complete the recommended actions to resolve the issue and reschedule the update.
|
|
|
| Your service identifier (Tenant): |
| Environment: Production |
| Version before update: 14.5.35970.0 |
| Version after update: 15.0.36560.0 |
| Scheduled date: 11/5/2019 (UTC) |
| Errors: |
| Extension 'Job Planning Fuctionality' version 1.0.1.6 by 'ELN' failed to compile.Extension compilation failederror AL0999: Internal error: System.InvalidCastException: Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceChangeAddActionSymbol' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ActionSymbol'. at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ChangeObjectMembersHelpers.ValidateSectionsAreaChangesWithNestedGroups[T](T changeSymbol, ActionSymbol anchor, ActionSymbol targetSymbol, DiagnosticBag diagnostics) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\ChangeObjectMembersHelpers.cs:line 532 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ChangeObjectMembersHelpers.VerifyActionAddChange(PageTypeKind pageTypeKind, ChangeAddSymbol addSymbol, DiagnosticBag diagnostics) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\ChangeObjectMembersHelpers.cs:line 328 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ChangeObjectMembersHelpers.CheckForAddAcrossAreas(PageTypeKind pageTypeKind, ImmutableArray`1 addSymbols, DiagnosticBag diagnostics) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\ChangeObjectMembersHelpers.cs:line 89 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.PageExtensionObjectMembers.CheckMembers(DiagnosticBag diagnostics) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\PageExtensionObjectMembers.cs:line 142 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ObjectMembers`1.ForceCompleteMembers(SourceLocation locationOpt, CancellationToken cancellationToken, Predicate`1 excludeFromNameUniqueness) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\ObjectMembers.cs:line 811 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ObjectMembers`1.ForceComplete(SourceLocation locationOpt, CancellationToken cancellationToken, Predicate`1 excludeFromNameUniqueness) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Members\ObjectMembers.cs:line 771 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourcePageExtensionTypeSymbol.ForceComplete(SourceLocation locationOpt, CancellationToken cancellationToken) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourcePageExtensionTypeSymbol.cs:line 55 at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceModuleSymbol.ForceComplete(SourceLocation locationOpt, CancellationToken cancellationToken) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceModuleSymbol.cs:line 125 at Microsoft.Dynamics.Nav.CodeAnalysis.Compilation.GetSourceDeclarationDiagnostics(SyntaxTree syntaxTree, Nullable`1 filterSpanWithinTree, Func`4 locationFilterOpt, CancellationToken cancellationToken) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\Compilation.cs:line 983 at Microsoft.Dynamics.Nav.CodeAnalysis.Compilation.GetDiagnostics(CompilationStage stage, Boolean includeEarlierStages, CancellationToken cancellationToken) in F:\a\784\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\Compilation.cs:line 648 |
|
|
|
|
Recommended actions:
|
|
Depending on the error and your permissions to manage extensions, you may need to contact your Partner or the extension publisher to perform these actions.
|
| |
|
1. Fix the extension error
|
| |
|
Option 1: Extension is required
|
| |
|
A. Make the minor change to the extension, compile the extension against the latest symbols for version 15.0.36560.0, and perform the necessary tests to ensure the functionality is correct. (If the extension is from AppSource, you will need to contact the publisher to get the extension fixed. AppSource contains support and help links for each of the app publishers.)
|
| |
|
B. Upload the extension using the Extension Management page in Business Central and select the appropriate version for which the updated extension is compatible. The extension will then be updated to this version when the update is attempted again. For more information, view Deploying a Tenant Customization. (If the extension is from AppSource, the publisher will need to get the compatible extension published.)
|
| |
|
Important: If you are using the extension, you can continue using the extension on the current version for 90 days. After 90 days, you will be updated to the next release without the extension. Please ensure that you have resolved the extension compatibility issue described above prior to such date.
|
| |
|
Option 2: Extension is not required
|
| |
|
Uninstall the extension using the Extension Management page in Business Central prior to the update being attempted again.
|
| |
|
2. Reschedule the update
|
| |
|
A. If the update is to a new major version, you can use the Business Central Admin Center to check and change when the update will be performed.
|
| |
|
B. If the update is to a new minor version, the update will be attempted again automatically using the configured upgrade window in the Business Central Admin Center.
|
|
|
|
| |
|
Because you have an active account and have been added as a notification recipient for the account, you will receive emails to inform you about account-related matters. If you no longer wish to receive these notification emails, you can contact the account administrator to be removed as a notification recipient.
|
|
Privacy Statement
Microsoft Corporation, One Microsoft Way, Redmond WA, USA 98052
|
|
| |
|
|
|
|
810
Share
Report
All responses (
Answers (
