FIX: SQL Server 2014 PowerShell script jobs trigger DCOM errors after you install Azure PowerShell

Applies to: SQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 Enterprise

Symptoms


Assume that you install Azure PowerShell on an instance of SQL Server 2014, and then you run a SQL Server Agent job that contains PowerShell script job steps. In this situation, the job runs successfully, but you may see DCOM errors that resemble the following in the System log:
DCOM was unable to communicate with the computer Microsoft.WindowsAzure.Commands.SqlDatabase.Types.ps1xml using any of the configured protocols; requested by PID 4728 (file_path\SQLPS.exe).

DCOM was unable to communicate with the computer Microsoft.WindowsAzure.Commands.SqlDatabase.dll using any of the configured protocols; requested by PID 4728 (file_path\SQLPS.exe).

Resolution


This problem was first fixed in the following cumulative update for SQL Server:


Status


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

References


Learn about the terminology Microsoft uses to describe software updates.