执行SSIS包时加载Microsoft.AnalysisServices.AdomdClientUI.dll失败求助

Hey there! Let's work through this missing DLL error you're hitting when running your SSIS package with dtexec—since you're new to Analysis Services, I'll break down practical, targeted fixes that often resolve this specific issue.

• Verify the correct ADOMD Client version is installed
  The 13.0.0.0 version corresponds to SQL Server 2016. Head to Control Panel > Programs and Features and check if you have Microsoft Analysis Services ADOMD Client 13.0 installed. If it's missing, grab the matching version from official SQL Server installation resources (make sure to pick the right architecture—x86 or x64—to match your SSIS and dtexec setup).

• Match dtexec architecture with your ADOMD Client installation
  dtexec has both 32-bit and 64-bit versions:

  • 32-bit path: C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\dtexec.exe
  • 64-bit path: C:\Program Files\Microsoft SQL Server\130\DTS\Binn\dtexec.exe
    If you're using the 32-bit dtexec but only installed the 64-bit ADOMD Client (or vice versa), the DLL won't be found. Install the ADOMD Client version that matches your dtexec architecture, or switch to using the dtexec version that aligns with your existing ADOMD Client.

• Add the DLL to the Global Assembly Cache (GAC)
  If the ADOMD Client is already installed but the DLL still isn't detected, manually register it in the GAC. Open an elevated Command Prompt (run as administrator) and run this command, adjusting the path to match your installation:

  gacutil /i "C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.AnalysisServices.AdomdClientUI.dll"
  

  For x86 installations, replace Program Files with Program Files (x86).

• Check SSIS package dependencies and runtime settings
  Open your SSIS package in SQL Server Data Tools (SSDT) or Visual Studio:

  • Verify that the package references the 13.0.0.0 version of Microsoft.AnalysisServices.AdomdClientUI.dll (check the References section). If it's pointing to a different version, update the reference to match your environment.
  • Ensure the package's Run64BitRuntime property matches your system architecture (set to True for 64-bit, False for 32-bit). This setting controls which runtime environment the package uses, which can affect DLL loading.

• Repair your SQL Server installation
  If none of the above steps work, there might be a corrupted or incomplete SQL Server component installation. Open the SQL Server Installation Center, navigate to the Maintenance tab, and select Repair. Choose your target SQL Server instance and follow the prompts—this will reinstall any missing or damaged components, including the problematic DLL.

Start with the first two steps first, as they're the most common causes of this error. If you run into specific issues with any of these fixes (like not finding the ADOMD Client installer, or errors running gacutil), feel free to share more details about your setup (SQL Server version, which dtexec path you're using, etc.) and we can narrow it down further.

内容的提问来源于stack exchange，提问作者Neriman Merve Unsal