Query regarding error message in import export wizard

Question

"Could not load file or assembly 'Microsoft.DataTransformationServices.ScaleHelper, Version=16.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified. (DTSWizard)"

I am getting this message whenever trying to use the SQL import export wizard.

How will I solve this?

Answer 1

This error message typically indicates that there is an issue with a missing or incompatible assembly required by the SQL Import Export Wizard. Here are a few steps you can try to resolve this problem:

Verify the version of SQL Server: Make sure you have the correct version of SQL Server installed that matches the assembly version mentioned in the error message (Version=16.0.0.0 in this case).

Check the presence of the assembly: Confirm whether the assembly 'Microsoft.DataTransformationServices.ScaleHelper' is present in the specified location. The assembly should be located in the Global Assembly Cache (GAC) or in the same directory as the SQL Import Export Wizard executable.

Repair or reinstall SQL Server: If the assembly is missing or corrupted, you can try repairing or reinstalling SQL Server. This process will ensure that all required assemblies are properly installed.

Check for dependencies: The error message also mentions "or one of its dependencies." It's possible that the missing assembly relies on other assemblies that are not present. Ensure that all necessary dependencies are installed and accessible.

Update SQL Server and Visual Studio: If you're using an older version of SQL Server or Visual Studio, consider updating to a newer version. Newer versions often include bug fixes and updated dependencies, which could resolve the issue.

1. Verify user permissions: Ensure that the user account you are using to run the SQL Import Export Wizard has the necessary permissions to access and execute the required assemblies and dependencies.

Remember to back up any critical data or configurations before making changes to your system.

Answer 2

Hi Together,

Cumulative Update Package 6 for SQL Server 2022 - KB5027505 from July fixes this issue.

Best Regards,
Jochen