Accept 00000001 Driver



Hello Advanced Installer team,
TLS 1.0 is deprecated since June 30, 2018, and use of TLS 1.2 is strongly encouraged. Eventually, some customers have started to switch to TLS 1.2 only.
  1. Dec 20, 2014 Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior. Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.
  2. SSL connection error: error:00000001:lib (0):func(0):reason(1) #986. Arnoldtonderaimarunda opened this issue Jun 26, 2018 3 comments Comments. Copy link Quote reply.
  3. Hello All, we currently had a situation on where a server was unreachable through RDP. Upon digging into this it was noticed that the possible cause of this issue was mfehidk.sys(due to some logs) I would highly appreciate if somebody could tell me if mfehidk.sys could affect a server in this way.
  4. A Commercial Driver License (CDL) authorizes an individual to operate a commercial motor vehicle or combination of motor vehicles used to transport passengers or property. Individuals applying for a Commercial Driver License should recognize that this is a professional license with more testing requirements than other licenses.
I am using ODBC Connection Test in an installer built with AI 15.1.
Accept 00000001 Driver

Latest Microsoft OLE DB Driver for SQL Server. The first step towards resolving the SSL Security error, is to make sure that the version of the target SQL Server instance you want to connect to, is supported by the driver. For example, Microsoft OLE DB Driver 18.1 for SQL Server supports connecting to SQL Server 2012 or later.

When the SQL server's SCHANNEL.DLL is configured to only support TLS 1.2, the connection test fails with 'Connection timeout'. I can, however, connect through SSMS using encrypted TCP/IP, so TLS 1.2 seems to be working server-side.
Our .NET app had the same problem, which I have already fixed using the lines:
For your reference, the registry file used by our customer to enforce TLS 1.2 is as follows:

Code: Select all

(Server reboot required for changes to take effect)
Kind regards,
AlexanderHello Advanced Installer team,
TLS 1.0 is deprecated since June 30, 2018, and use of TLS 1.2 is strongly encouraged. Eventually, some customers have started to switch to TLS 1.2 only.

Accept 00000001 Driver Test

Accept 00000001 driver testI am using ODBC Connection Test in an installer built with AI 15.1.
When the SQL server's SCHANNEL.DLL is configured to only support TLS 1.2, the connection test fails with 'Connection timeout'. I can, however, connect through SSMS using encrypted TCP/IP, so TLS 1.2 seems to be working server-side.

Accept 00000001 Driver Portal


Our .NET app had the same problem, which I have already fixed using the lines:
For your reference, the registry file used by our customer to enforce TLS 1.2 is as follows:

Accept 00000001 Driver Jobs


Code: Select all

(Server reboot required for changes to take effect)
Kind regards,
Alexander



Comments are closed.