I have the same issue on an instance where no SSL certificate is installed.
I found out that it only occurs when using SSMS 20. In SSMS 19 the creation of the job for SSIS works fine.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In a test environment with SQL Server 2022 Developer Edition, I am trying to create a job to run an SSIS package.
These same packages have been successfully tested in SQL 2019.
When trying to create the job, configuring it as follows:
General / Owner : Administrator, I also tried with NT SERVICE\SQLSERVERAGENT
New Step:
type: SQL SERVER INTEGRATION SERVICES PACKAGE,
Package Source: SSIS Catalog
Source: localhost
Log on to the server: use windows authentication (only option for localhost)
When I click on the button to select the package, an error occurred:
"
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
ADDITIONAL INFORMATION:
The certificate chain was issued by an authority that is not trusted
"
I am logged into the Database Engine using the Windows Authentication option.
Is it really mandatory to use a certificate when running the package on localhost ? Any tips on how to resolve this problem?
Additional Notes: After installing sql 2022, I installed "Microsoft Sql Server Native Client"
I have the same issue on an instance where no SSL certificate is installed.
I found out that it only occurs when using SSMS 20. In SSMS 19 the creation of the job for SSIS works fine.
Despite the SSMS version being updated to 20.1, issues with SSIS connectivity still persist as a known problem. The only solution remains to use the older version 19.3.
Refer to this.
Hi,Marcio Matos
SSL verification is required whenever you need to connect to a database engine instance.
This article may help you fix this issue:
Best regards
Mikey Qiao
Hope my answer may help you.
Sqlserver 2022 uses ssl by default. It also uses a self signed (untrusted) certificate by default unless the installer configured trusted certificates.
you can via the connection string disable encryption, or trust the unsigned certificate. See Scenario 2 option 1.
I am facing the same problem using SSMS v20.1 and SQL Server 2019