October 25, 2018 at 3:25 pm
A new installed SQL 2016 server cannot execute maintenanceplans for backup databases.
In the maintenanceplan history I found this error messsage, but I cannot solve this.
Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 23:22:36 Error: 2018-10-25 23:22:37.38 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-25 23:22:37.38 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-25 23:22:37.52 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-25 23:22:37.54 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-25 23:22:37.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:22:36 Finished: 23:22:37 Elapsed: 1.437 seconds. The package execution failed. The step failed.
October 25, 2018 at 6:08 pm
Looks like it is running as the built-in service account. Did you give that account permissions in the instance to perform backups? It would also need permissions to whatever file path you are trying to write to. Microsoft recommends that this account be given 'sysadmin' in the SQL instance in order to perform all necessary functions.
https://docs.microsoft.com/en-us/sql/ssms/agent/set-service-startup-account-sql-server-agent-sql-server-configuration-manager?view=sql-server-2017
Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/
October 25, 2018 at 7:09 pm
robert 13122 - Thursday, October 25, 2018 3:25 PMA new installed SQL 2016 server cannot execute maintenanceplans for backup databases.
In the maintenanceplan history I found this error messsage, but I cannot solve this.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 23:22:36 Error: 2018-10-25 23:22:37.38 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-25 23:22:37.38 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-25 23:22:37.52 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-25 23:22:37.54 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-25 23:22:37.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:22:36 Finished: 23:22:37 Elapsed: 1.437 seconds. The package execution failed. The step failed.
If you used the defaults for the accounts and file locations, permissions should be fine. Any changes to the service accounts need to be done using SQL Server Configuration Manager as that will manage the permissions.
The issue may be due to the error message:
provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.
Since the error indicates it's a connection to the local server, try setting client configuration to Trust Server Certificate.
On the server in SQL Server Configuration Manager, on the left pane go down to the SQL Native Client Configuration node, right click, select properties and then in the configuration properties, set Trust Server Certificate to Yes.
Sue
October 26, 2018 at 1:59 am
Sue_H - Thursday, October 25, 2018 7:09 PMrobert 13122 - Thursday, October 25, 2018 3:25 PMA new installed SQL 2016 server cannot execute maintenanceplans for backup databases.
In the maintenanceplan history I found this error messsage, but I cannot solve this.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 23:22:36 Error: 2018-10-25 23:22:37.38 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-25 23:22:37.38 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-25 23:22:37.52 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-25 23:22:37.54 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-25 23:22:37.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:22:36 Finished: 23:22:37 Elapsed: 1.437 seconds. The package execution failed. The step failed.If you used the defaults for the accounts and file locations, permissions should be fine. Any changes to the service accounts need to be done using SQL Server Configuration Manager as that will manage the permissions.
The issue may be due to the error message:
provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.Since the error indicates it's a connection to the local server, try setting client configuration to Trust Server Certificate.
On the server in SQL Server Configuration Manager, on the left pane go down to the SQL Native Client Configuration node, right click, select properties and then in the configuration properties, set Trust Server Certificate to Yes.Sue
Thanks for your input Sue, I've the changes you suggested, but still this errormessage after executing the maintenanceplan.
The manual backup goes without any problems.
Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 09:38:25 Error: 2018-10-26 09:38:27.16 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-26 09:38:27.16 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-26 09:38:27.29 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-26 09:38:27.30 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-26 09:38:27.30 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 09:38:25 Finished: 09:38:27 Elapsed: 1.391 seconds. The package execution failed. The step failed.
October 26, 2018 at 10:45 am
robert 13122 - Friday, October 26, 2018 1:59 AMSue_H - Thursday, October 25, 2018 7:09 PMrobert 13122 - Thursday, October 25, 2018 3:25 PMA new installed SQL 2016 server cannot execute maintenanceplans for backup databases.
In the maintenanceplan history I found this error messsage, but I cannot solve this.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 23:22:36 Error: 2018-10-25 23:22:37.38 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-25 23:22:37.38 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-25 23:22:37.52 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-25 23:22:37.54 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-25 23:22:37.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:22:36 Finished: 23:22:37 Elapsed: 1.437 seconds. The package execution failed. The step failed.If you used the defaults for the accounts and file locations, permissions should be fine. Any changes to the service accounts need to be done using SQL Server Configuration Manager as that will manage the permissions.
The issue may be due to the error message:
provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.Since the error indicates it's a connection to the local server, try setting client configuration to Trust Server Certificate.
On the server in SQL Server Configuration Manager, on the left pane go down to the SQL Native Client Configuration node, right click, select properties and then in the configuration properties, set Trust Server Certificate to Yes.Sue
Thanks for your input Sue, I've the changes you suggested, but still this errormessage after executing the maintenanceplan.
The manual backup goes without any problems.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 09:38:25 Error: 2018-10-26 09:38:27.16 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-26 09:38:27.16 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-26 09:38:27.29 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-26 09:38:27.30 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-26 09:38:27.30 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 09:38:25 Finished: 09:38:27 Elapsed: 1.391 seconds. The package execution failed. The step failed.
Did you setup the encryption and the certificate? What type of certificate is it - self signed or CA?
Also - can you check your versions of SSMS and check the connection properties? What are the settings for encryption and trusting the server certificate?
Sue
October 29, 2018 at 1:41 am
Sue_H - Friday, October 26, 2018 10:45 AMrobert 13122 - Friday, October 26, 2018 1:59 AMSue_H - Thursday, October 25, 2018 7:09 PMrobert 13122 - Thursday, October 25, 2018 3:25 PMA new installed SQL 2016 server cannot execute maintenanceplans for backup databases.
In the maintenanceplan history I found this error messsage, but I cannot solve this.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 23:22:36 Error: 2018-10-25 23:22:37.38 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-25 23:22:37.38 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-25 23:22:37.52 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-25 23:22:37.54 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-25 23:22:37.54 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 23:22:36 Finished: 23:22:37 Elapsed: 1.437 seconds. The package execution failed. The step failed.If you used the defaults for the accounts and file locations, permissions should be fine. Any changes to the service accounts need to be done using SQL Server Configuration Manager as that will manage the permissions.
The issue may be due to the error message:
provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.Since the error indicates it's a connection to the local server, try setting client configuration to Trust Server Certificate.
On the server in SQL Server Configuration Manager, on the left pane go down to the SQL Native Client Configuration node, right click, select properties and then in the configuration properties, set Trust Server Certificate to Yes.Sue
Thanks for your input Sue, I've the changes you suggested, but still this errormessage after executing the maintenanceplan.
The manual backup goes without any problems.Message
Executed as user: NT Service\SQLAgent$SQL01. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 09:38:25 Error: 2018-10-26 09:38:27.16 Code: 0xC00291EC Source: {4054A2C5-08AF-4173-B475-A3B18A0BEAA3} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2018-10-26 09:38:27.16 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2018-10-26 09:38:27.29 Code: 0xC0024104 Source: Back Up Database (Full) Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Error: 2018-10-26 09:38:27.30 Code: 0xC0024104 Source: {EDE0B0D2-CE8D-41DC-8267-4E5FC76A7AF3} Description: The Execute method on the task returned error code 0x80131904 (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.)). The Execute method must succeed, and indicate the result using an "out" parameter. End Error Warning: 2018-10-26 09:38:27.30 Code: 0x80019002 Source: OnPostExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning DTExec: The package execution returned DTSER_FAILURE (1). Started: 09:38:25 Finished: 09:38:27 Elapsed: 1.391 seconds. The package execution failed. The step failed.Did you setup the encryption and the certificate? What type of certificate is it - self signed or CA?
Also - can you check your versions of SSMS and check the connection properties? What are the settings for encryption and trusting the server certificate?Sue
Thank you Sue.
No I've not setup any encryption and a certificate. It is a default setup en the SSMS is is v17.9.
What is the best way to install a cert?
Regards, Robert
October 29, 2018 at 2:54 pm
robert 13122 - Monday, October 29, 2018 1:41 AMThank you Sue.
No I've not setup any encryption and a certificate. It is a default setup en the SSMS is is v17.9.
What is the best way to install a cert?Regards, Robert
You would set it up in the same place you need to look and see if it's trying to use encryption.
In SQL Server configuration manager, go to SQL Server Network Configuration and right click on the Protocols for MSSQLSERVER and select properties. It's on this window where things get configured or checked for encryption. Check the Flags tab and see if Force Encryption is set to yes. Set it to no if it is selected, restart the instance and the check if you get the errors.
Sue
October 30, 2018 at 1:32 pm
Sue_H - Monday, October 29, 2018 2:54 PMrobert 13122 - Monday, October 29, 2018 1:41 AMThank you Sue.
No I've not setup any encryption and a certificate. It is a default setup en the SSMS is is v17.9.
What is the best way to install a cert?Regards, Robert
You would set it up in the same place you need to look and see if it's trying to use encryption.
In SQL Server configuration manager, go to SQL Server Network Configuration and right click on the Protocols for MSSQLSERVER and select properties. It's on this window where things get configured or checked for encryption. Check the Flags tab and see if Force Encryption is set to yes. Set it to no if it is selected, restart the instance and the check if you get the errors.Sue
Hi Sue, this was allready set to no. Do you have any futher suggestions?
Regards, Robert
October 30, 2018 at 5:41 pm
robert 13122 - Tuesday, October 30, 2018 1:32 PMSue_H - Monday, October 29, 2018 2:54 PMrobert 13122 - Monday, October 29, 2018 1:41 AMThank you Sue.
No I've not setup any encryption and a certificate. It is a default setup en the SSMS is is v17.9.
What is the best way to install a cert?Regards, Robert
You would set it up in the same place you need to look and see if it's trying to use encryption.
In SQL Server configuration manager, go to SQL Server Network Configuration and right click on the Protocols for MSSQLSERVER and select properties. It's on this window where things get configured or checked for encryption. Check the Flags tab and see if Force Encryption is set to yes. Set it to no if it is selected, restart the instance and the check if you get the errors.Sue
Hi Sue, this was allready set to no. Do you have any futher suggestions?
Regards, Robert
Nope. It would be either the server or client pieces and one would need to be set to encrypted. If none of those are set to be encrypted, not sure how you could get an SSL error.
Sue
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply