Dynamics Community Forum Thread Details

Microsoft Dynamics 365 (on premises) Update 9.1.39 - Upgrade error

hello everyone,

i have a problem on upgrading microsoft dynamics 365 server:

First Problem of the Update:
Error during the action Microsoft.Crm.UpdateWrapper.InstallVCRedist9SP1.
Error installing the required components: Microsoft Visual C++ Redistributable 2008 SP1

I could resolve it by repairing Microsoft Visual C++ 2010 x64 Redistributable. For that I had to copy the installation files to the given root folder in the installtion process, where you have to give a source.

After that the installation runs on the error (KB5064483.log):

Error 2771: Upgrade of feature Tools has a missing component.
Error| An unexpected error occurred while installing this package. There may be a problem with the package. The error code is 2771. , Error, OK, Option1
Action completed at 08:26:00: CostFinalize. Return value 3.

In the log file KB5064483_Msp.log is more information about the error:

SELMGR: ComponentId '{A2B3F2B0-1407-9952-929C-B2F15C874C44}' is registered to feature 'Tools', but is not present in the Component table. Removal of components from a feature is not supported!
MSI (s) (78:14) [08:25:57:362]: Note: 1: 2771 2: Tools
DEBUG: Error 2771: Upgrade of feature Tools has a missing component.
MSI (s) (78:14) [08:26:00:877]: Product: Microsoft Dynamics 365 Server -- An unexpected error occurred while installing this package. There may be a problem with the package. The error code is 2771. Arguments: Tools, ,

Action completed at 08:26:00: CostFinalize. Return value 3.

I couldn't find what this component is, so i had a look into the log file of the last update an found this line:

Executing op: ComponentRegister(ComponentId={A2B3F2B0-1407-9952-929C-B2F15C874C44},KeyPath=C:\Program Files\Dynamics 365\LangPacks\1031\Xrm\sql\9\Scripts\DBUpdate_CollationFix.sql,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=1)

Our System:
Windows Server 2016
SQL Server 2016
Current Microsoft Dynamics 365 Server Version: 9.1.35.06 on premises
Update Microsoft Dynamics 365 Server Version: 9.1.39.04
Microsoft Visual C++ Redistributable 2008 x64 9.0.30729.6161
Microsoft Visual C++ Redistributable 2010 x64 10.0.40219

What could be the error?

Could it be that the Dynamics update should have been performed before a Windows update?
Or could missing permissions be the reason? (I am a local admin and deployment manager)

Categories:

Microsoft Dynamics CRM

Hi,

The error you're encountering during the upgrade to Dynamics 365 Server version 9.1.39.04—specifically Error 2771: Upgrade of feature Tools has a missing component—is typically related to inconsistencies in the Windows Installer database, often caused by missing or corrupted components from previous installations.

Here are a few steps that may help resolve the issue:

Repair Previous Installations: As you've already done with the Visual C++ Redistributables, ensure that all prerequisite components (especially older versions like VC++ 2008 and 2010) are properly installed and repaired. Sometimes the installer expects specific files or registry entries that may have been removed or altered.

Clean Up Installer Cache: Use tools like the Windows Installer CleanUp Utility (if still available) or manually clean up remnants of previous updates that might interfere with the current installation.

Check Component Table: The log mentions a missing component registered to the Tools feature. This could be a leftover reference from a previous update. If possible, inspect the MSI database using tools like Orca to verify the presence of the component {A2B3F2B0-1407-9952-929C-B2F15C874C44} in the Component table.

Reinstall the Previous Update: Try reinstalling or repairing the previous update (9.1.35.06) to restore any missing components before attempting the upgrade again.

Run Installer with Logging: Continue using detailed logging (/L*v) during installation to capture all errors. This can help identify the exact step where the failure occurs.

Microsoft Support: If the issue persists, consider contacting Microsoft Support with your logs. This error may require a manual fix or patch from their side, especially if it's related to a corrupted update package [1].