Edit

Share via

Known issue in the December Security and Quality Rollups 3210137 and 3210138 for the .NET Framework 4.5.2 on Windows 8.1, Windows Server 2012 R2, and Windows Server 2012

  • Article

This article helps you work around the problem that occurs when applications connect to an instance of Microsoft SQL Server on the same computer.

Applies to:   .NET Framework 3.5 Service Pack 1
Original KB number:   3214106

Summary

The December 13, 2016, Security and Quality Rollup updates 3210137 and 3210138 contain a known issue that affects the .NET Framework 4.5.2 running on Windows 8.1, Windows Server 2012 R2, and Windows Server 2012. The issue was also present in the November 15, 2016, rollup updates that were superseded by the December updates. This article contains a workaround for this issue.

Symptoms

Applications that connect to an instance of Microsoft SQL Server on the same computer generate the following error message:

provider: Shared Memory Provider, error: 15 - Function not supported

To work around this issue, use one of the following methods.

Workaround 1

Disable the Shared Memory and Named Pipes protocols on the server side to force TCP-only connections to SQL Server. To do this, follow these steps.

Important

Before you disable other protocols, make sure that the TCP/IP protocol is enabled.

  1. Start SQL Server Configuration Manager.

    SQL Server Configuration Manager.

  2. Expand the SQL Server Network Configuration node.

  3. Select the Protocols for <SQLServer_instance> node for the instance of SQL Server that you're connecting to.

  4. Right-click Shared Memory, and then select Disable.

    Screenshot of the sql server configuration manager window, showing menus to disable the protocol item named Shared Memory.

  5. Repeat step 4 for Named Pipes, if it's enabled.

    Note

    TCP/IP should be the only protocol in this list that's enabled.

  6. Select the SQL Server Services node.

  7. Right-click the instance of SQL Server that you updated.

  8. Select Restart.

    Screenshot shows menus to restart a SQL Server instance.

Workaround 2

Create an alias on the server to force TCP protocol for local applications. To do this, see the following MSDN and TechNet topics:

Workaround 3

Disable shared memory from the Client Configuration tool (32-bit and 64-bit). To do this, follow these steps:

  1. Start the Client Configuration tool on the server by typing cliconfg.exe.

  2. If it's selected, clear the Enable shared memory protocol check box.

    Screenshot of the SQL Server Client Network Utility dialog box. The Enable shared memory protocol check box is cleared.

    Note

    On a 64-bit server, if you run 32-bit applications that connects to SQL Server, you must run this procedure by using the 32-bit Client Configuration tool that is located in the C:\Windows\SysWOW64 folder.

Applies to

This issue applies to users who have the .NET Framework 4.5.2 installed on Windows 8.1, Windows Server 2012 R2, or Windows 2012, and who have applied either of the following December 2016 updates:

  • Security and Quality Rollup for the .NET Framework 4.5.2 on Windows 8.1 and Windows Server 2012 R2 (KB3210137)
  • Security and Quality Rollup for the .NET Framework 4.5.2 on Windows Server 2012 (KB3210138)

This issue is also present in the following (now superseded) November 2016 Preview of Quality Rollup updates:

  • November 2016 Preview of Quality Rollup for the .NET Framework 3.5, 4.5.2, 4.6, 4.6.1 on Windows 8.1 and Server 2012 R2 (KB3196684)
  • November 2016 Preview of Quality Rollup for the .NET Framework 3.5, 4.5.2, 4.6, 4.6.1 on Windows Server 2012 (KB3195383)
  • November 2016 Preview of Quality Rollup for the .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1 on Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB3196686)
  • November 2016 Preview of Quality Rollup for the .NET Framework 2.0 SP2, 4.5.2, 4.6 on Windows Vista SP2 and Windows Server 2008 SP2 (KB3195382)

Resolution

This issue is resolved in the following updates: