SSIS Excel Destination Editor意外关闭，配置遇阻求助

Hey there, sorry to hear you're hitting this frustrating glitch while getting started with SSIS! Let's break down some practical fixes that usually resolve this unexpected editor shutdown issue:

1. Verify Excel Connection Manager Configuration #

• Double-check you're using the correct driver version in your Excel Connection Manager:
  • For .xlsx files (Excel 2007+), select Microsoft Excel 12.0 XML or a newer driver option.
  • For legacy .xls files, use Microsoft Excel 97-2003 driver. Mismatched drivers often cause UI oddities like this.
• Ensure the target Excel file isn't open in another program (like Excel itself)—file locks can trigger silent crashes in the SSIS editor. Also, use an absolute file path in the connection manager (avoid relative paths during setup).

2. Refresh or Repair SSIS/SSDT Components #

• Restart first: Close all Visual Studio/SSDT windows, restart your computer, and reopen your project. Temporary cache corruption is a common culprit here.
• Repair SSDT: If restarting doesn't help, go to Control Panel → Programs and Features, find your Visual Studio version, right-click → Change → Repair. This fixes corrupted installation files related to SSIS tools.
• Check Office Data Drivers: Install the matching-bit version of the Microsoft Access Database Engine (32-bit if your SSDT is 32-bit, 64-bit if it's 64-bit). Mixed-bit drivers frequently cause SSIS Excel component failures.

3. Bypass the "New..." Button by Manually Creating the Excel Sheet #

Since the "New..." dialog is crashing, work around it with these steps:

1. Open your target Excel file outside of SSIS, create a new worksheet with column names and data types matching your OLE DB Source (you can adjust later if needed).
2. Save and close the Excel file.
3. Back in SSIS, open the Excel Destination Editor—your new worksheet should now appear in the Name of the Excel sheet dropdown. Select it, then head to the Mappings tab to align source and destination columns.

4. Check Project and SSIS Version Compatibility #

• Make sure your SSIS project version matches your installed SSDT version (e.g., SQL Server 2019 SSIS needs SSDT 2019 or later). Version mismatches can break UI components.
• Try creating a brand-new blank SSIS project, add only the basic OLE DB Source → Excel Destination flow, and test the "New..." button there. If it works, your original project might have corrupted cache files.

内容的提问来源于stack exchange，提问作者JacobD