The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. To use one of the hotfixes in this package, you do not have to make any changes to the registry. You do not have to restart the computer after you apply this hotfix. If you do not see your language, it is because a hotfix is not available for that language. The "Hotfix download available" form displays the languages for which the hotfix is available. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article.
Apply this hotfix only to systems that are experiencing this specific problem. However, this hotfix is intended to correct only the problem that is described in this article. Resolution Hotfix informationĪ supported hotfix is available from Microsoft. However, the IBMJSSE2 provider returns an SSLContext instance that only supports the SSLv3 protocol. When a WebSphere application has FIPS enabled, the IBM Java Runtime Environment (JRE) requires the TLS protocol for SSL connections. In more detail, when Microsoft SQL Server JDBC Driver 2.0 passes "SSLv3" as the string argument, the Sun JSSE provider returns an SSLContext instance that supports both the SSLv3 protocol and the TLS protocol. However, the returned SSLContext instance may also support other protocols. According to the Java Secure Socket Extension (JSSE) reference guide, the SSLContext.getInstance function returns an SSLContext instance that supports the specified protocol. The string argument determines which protocols the returned context should support. Microsoft SQL Server JDBC Driver 2.0 calls the SSLContext.getInstance function.
However, Microsoft SQL Server JDBC Driver 2.0 requests the SSLv3 protocol. This issue occurs because the IBM WebSphere application requires the TLS protocol for SSL connections when the application has FIPS enabled. Error: SSLv3 protocol cannot be enabled in FIPS mode.DSRA0010E: SQL State = 08S01, Error Code = 0Īt .SQLServerConnection.terminate(Unknown Source)Īt .TDSChannel.throwSSLConnectionFailed(Unknown Source)Īt .TDSChannel.enableSSL(Unknown Source) : The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.
0 kommentar(er)
