AWS SCT reports not running with Windows Login

When using Windows Authentication with AWS Schema Conversion Tool (SCT) for SQL Server connections, you're encountering a common issue related to the JDBC driver configuration for integrated authentication.

The error occurs because the JDBC driver isn't properly configured to use Windows Authentication. To resolve this issue, you need to take the following steps:

1. Make sure you have the sqljdbc_auth.dll file available. This DLL is required for Windows Authentication and should be included in your JDBC driver package.

2. Set up environment variables that point to your JDBC installation:

• Create a variable named SQLJDBC_HOME with the path to where your sqljdbc4.jar exists
• Create a variable named SQLJDBC_AUTH_HOME pointing to the auth folder where sqljdbc_auth.dll is located (use the x64 folder if you're on a 64-bit system)

3. Copy the sqljdbc_auth.dll file to the folder where your JDK/JRE is running. You may need to copy it to multiple locations such as:

• The JDK bin folder
• The JDK jre\bin folder
• The JDK jre\lib folder
• The JDK lib folder

4. Ensure that in your JDBC library folder, you only have the appropriate JDBC JAR file and remove any other sqljdbc*.jar files from that folder.

5. You can also try copying the sqljdbc_auth.dll file to the folder where your AWS SCT application is installed.

These steps should help configure the JDBC driver properly for Windows Authentication with AWS SCT. If you continue to have issues, you might want to temporarily switch to SQL Server Authentication for your SCT tasks until the Windows Authentication configuration is resolved.
Sources
Connect Microsoft SQL Servers with AWS Schema Conversion Tool - AWS Schema Conversion Tool