The RiskFabric Processing or RiskFabric Intraday Processing job fails on one or more steps and an error similar to either of the following is logged in the SQL Server Agent job history log:
Unable to start execution of step 16 (reason: JobOwner [domain\]<account> doesn't have permissions to use proxy 5 for subsystem ANALYSISCOMMAND). The step failed.Unable to start execution of step 22 (reason: JobOwner [domain\]<account> doesn't have permissions to use proxy 6 for subsystem CmdExec). The step failed.
For similar errors affecting the Bay Dynamics AD Connector Job, refer to KB article 276209.
The ICA service account under which the proxy credential runs has not been granted permissions to access the proxy, or the proxy has been disabled.
To grant the ICA service access to the proxy, follow this procedure:
[domain\]<ica_service_account>
with the ICA service account name and <proxy_name>
with the name of the proxy:
USE msdb;
GO
EXEC msdb.dbo.sp_grant_login_to_proxy @proxy_name=N'<proxy_name>', @login_name=N'[domain\]<ica_service_account>';
GO
Confirm the proxy is enabled by following this procedure:
<proxy_name>
with the name of the proxy:
USE msdb;
GO
SELECT p.[name] AS "Proxy_Name",
p.[enabled] AS "Enabled",
c.[name] AS "Credential_Name",
c.credential_identity AS "Credential_Identity"
FROM dbo.sysproxies AS p
INNER JOIN sys.credentials AS c
ON p.credential_id = c.credential_id
WHERE p.[name] = '<proxy_name>';
GO
If the proxy is not enabled (Enabled = 0
), follow this procedure:
<proxy_name>
with the name of the proxy:USE msdb;
GO
EXEC dbo.sp_update_proxy @proxy_name = N'<proxy_name>', @enabled = 1;
GO
If the proxy is not configured to use the RiskFabric Nightly Processing
credential, follow this procedure:
<proxy_name>
with the name of the proxy:
USE msdb;
GO
EXEC sp_update_proxy @proxy_name = N'<proxy_name>', @credential_name = N'RiskFabric Nightly Processing';
GO
Under certain rare circumstances, the following error may be returned when modifying the proxy:
Alter failed for '<proxy_name>'. (Microsoft.SqlServer.Smo)
Additional Information:
Object reference not set to an instance of an object. (Microsoft.SqlServer.Smo)
To resolve this error, follow this procedure:
<proxy_name>
Risk Fabric Nightly Processing
RiskFabric Nightly Processing
for CmdExec
steps; RiskFabric Proxy
for Analysis Services Command
steps)