FIX: SQL Server StreamInsight 1.2 installation fails or StreamInsight application does not run if FIPS is enabled

Gælder for: SQL Server 2008 R2 StandardSQL Server 2008 R2 EnterpriseSQL Server 2008 R2 Web


Scenario 1
Consider the following scenario:
  • You enable Federal Information Processing Standard (FIPS) on a computer.
  • You try to install Microsoft SQL Server StreamInsight 1.2 on the computer.
In this scenario, the installation fails. Additionally, you receive the following error message:
StreamInsight 1.2 Setup Interrupted

Setup was interrupted before StreamInsight 1.2 could be completely installed.

Your computer has not been modified. To complete installation at another time, please run setup again.
Scenario 2
Consider the following scenario:
  • You install SQL Server StreamInsight 1.2 on a computer.
  • You enable Federal Information Processing Standard (FIPS) on the computer.
  • You try to run a StreamInsight application.
In this scenario, the application does not run. Additionally, you receive an error message that resembles the following:
The specified StreamInsight instance name 'Default' is not valid or could not be found.

at Microsoft.ComplexEventProcessing.Diagnostics.Exceptions.Throw(Exception exception)

at Microsoft.ComplexEventProcessing.EmbeddedServerProxy.GetInstanceWithExistenceCheck(String instanceName)

at Microsoft.ComplexEventProcessing.EmbeddedServerProxy..ctor(String instanceName)

at Microsoft.ComplexEventProcessing.Server.Create(String instanceName)

Note This example error message assumes that "Default" is the instance name.


This issue occurs because the cryptography algorithm that is used by StreamInsight is non-FIPS compliant. Additionally, the FIPS-compliant algorithm experiences some performance degradation in queries that partition events into event groups by using the "group by" functionality.
Note The current fix uses the FIPS-compliant algorithm only if FIPS is turned on on your computer.


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about FIPS 140 Evaluation, go to the following Microsoft website:To enable FIPS on your computer, run the following command at a command prompt:
REG ADD HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy /v Enabled /t REG_DWORD /d 1 /f