Skip to main content
Rollback to Revision 2
Source Link
Hannah Vernon
  • 70.5k
  • 22
  • 177
  • 321

TLS1.0 Disableddisabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS1TLS 1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application whichthat is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL which givesand it returns the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server, the. The test worked fine for provider SQL Server Native Client 11.0 or indeed usingand I can also connect with SSMS.

So isIs there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 Disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS1.0 and installed SQL Express 2016. I've then attempted to install a 3rd party application which is going to install a website and supporting DB etc. The first thing it does is test connection to SQL which gives the error

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server, the test worked fine for provider SQL Server Native Client 11.0 or indeed using SSMS.

So is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS 1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application that is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL and it returns the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server. The test worked fine for provider SQL Server Native Client 11.0 and I can also connect with SSMS.

Is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

Rollback to Revision 1 - Edit approval overridden by post owner or moderator
Source Link
Paul
  • 1.5k
  • 5
  • 18
  • 38

TLS1.0 disabledDisabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS 1TLS1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application thatwhich is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL and it returnswhich gives the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server. The, the test worked fine for provider SQL Server Native Client 11.0 and I can also connect withor indeed using SSMS.

IsSo is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS 1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application that is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL and it returns the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server. The test worked fine for provider SQL Server Native Client 11.0 and I can also connect with SSMS.

Is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 Disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS1.0 and installed SQL Express 2016. I've then attempted to install a 3rd party application which is going to install a website and supporting DB etc. The first thing it does is test connection to SQL which gives the error

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server, the test worked fine for provider SQL Server Native Client 11.0 or indeed using SSMS.

So is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 Disableddisabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS1TLS 1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application whichthat is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL which givesand it returns the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server, the. The test worked fine for provider SQL Server Native Client 11.0 or indeed usingand I can also connect with SSMS.

So isIs there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 Disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS1.0 and installed SQL Express 2016. I've then attempted to install a 3rd party application which is going to install a website and supporting DB etc. The first thing it does is test connection to SQL which gives the error

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server, the test worked fine for provider SQL Server Native Client 11.0 or indeed using SSMS.

So is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

TLS1.0 disabled and 3rd party OLE DB use

I'm provisioning a new server as part of which we have disabled TLS 1.0 and installed SQL Server Express 2016. I've then attempted to install a 3rd party application that is going to install a website and supporting DB etc. The first thing it does is test the connection to SQL and it returns the following error:

Connection Problem: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error

To attempt to work out the issue I created a UDL file on my desktop and reproduced this error when using the Provider Microsoft OLE DB Provider for SQL Server. The test worked fine for provider SQL Server Native Client 11.0 and I can also connect with SSMS.

Is there anyway I can force the 3rd party installer to use a different provider? Is there anyway I can log what type of connection it is attempting?

Source Link
Paul
  • 1.5k
  • 5
  • 18
  • 38
Loading