Additional fixes included in Security Update for Service Bus 1.1 for Windows Server (KB2979588)

Issues that this cumulative update resolves

• Microsoft Security Bulletin MS14-042 for Service Bus 1.1 for Windows Server
  
  For more information about the security vulnerability, see https://technet.microsoft.com/library/security/MS14-042.

• The MaxMessageSizeInBytes setting in the ServiceBus environment is not honored for AMQP sends, as in the following scenario:

  • When a Service Bus client uses the AMQP protocol, users may receive a “javax.jms.JMSException” exception message.

  • This exception occurs when Service Bus tries to send messages that are larger than 256 KB, regardless of the configuration value for MaxMessageSizeInBytes.

  • The value of MaxMessageSizeInBytes can be modified in the NetMessagingProtocolHead binding in the Microsoft.ServiceBus.Gateway.exe.config file.

• The Set-SBNamespace PowerShell command sometimes returns an ArgumentOutofRangeException error, as in the following scenario:

  • When customers run the Set-SBNamespace PowerShell command together with the –ManageUsers option, they experience the following exception:
    
    System.ArgumentOutOfRangeException: The argument PrimaryKey cannot exceed 256 characters
    Parameter name: PrimaryKey
    at Microsoft.ServiceBus.Messaging.SharedAccessAuthorizationRule.set_PrimaryKey(String value)
    at Microsoft.ServiceBus.Commands.AuthorizationRuleHelper.Encrypt(AuthorizationRules rules, String encryptionToken)

  • This issue occurs when the customer runs the Set-SBNamespace command and the –ManageUsers option multiple times.

• Service Bus configuration fails, as in the following scenario:

  • A customer uses a custom certificate, and the Subject contains additional fields beyond the Common Name (CN) field.

  • The Service Bus Configuration Wizard finishes and then displays a green check mark. However, Service Bus has not been configured correctly and does not work as expected.

  To determine whether Service Bus is affected by this issue, run the SB-GetMessageContainer PowerShell command. This will indicate the state of the message container or containers. The “Not Loaded” and “Creating” states are affected by this issue when “Active” is the expected state.

• The Workflow Manager configuration may fail when it uses the same custom certificate as the Service Bus server, as in the following scenario:

  • A customer tries to configure a Workflow Manager farm by using the Network Load Balancer workaround (described at https://support.microsoft.com/kb/2949779).

  • Workflow Manager is using the same custom certificate that the Service Bus server is using.

• Service Bus Configuration Wizard sometimes fails when it's using databases that have SQL Mirroring enabled, as in the following scenario:

  • A customer who uses Service Bus Configuration Wizard or who runs the New-SBFarm PowerShell command and receives the following error message:
    
    Configuration operation failed. Please drop databases and use "Create a New Farm" again.

  • In the “Details” section, the user sees the following:

    • The operation cannot be performed on database 'SBDatabase' because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

    • ALTER DATABASE statement failed

  • This issue may occur when SQL mirroring is enabled.
    
    Note When you use pre-created databases with SQL mirroring, you must set the following attributes on the databases. If these attributes are not set, the New-SBFarm PowerShell command will fail even after this update has been applied.

    • On the Service Bus Gateway database, add the following attributes:
      
      snapshot_isolation_state = 1
      is_read_committed_snapshot_on = 1

  • On each of the Service Bus Message Container databases, add the following attributes:
    
    snapshot_isolation_state = 1
    is_read_committed_snapshot_on = 1
    is_trustworthy_on = 1

Cumulative update package information

File information

The English (United States) version of this cumulative update package uses a Microsoft Windows Installer package to install the cumulative update package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.