Could not execute statement on remote server 'RiskFabric_ASDB'
search cancel

Could not execute statement on remote server 'RiskFabric_ASDB'

book

Article ID: 230409

calendar_today

Updated On: 02-27-2025

Products

Information Centric Analytics

Issue/Introduction

After upgrading Information Centric Analytics (ICA) to version 6.5.4 MP1 (6.5.4.0100), the Calculate Risk Scores step (20) of the nightly RiskFabric Processing job fails and the following error message is logged in the SQL Server Agent history log and in the RiskFabric relational database table dbo.Log_DataTransformation:

Error Msg: Could not execute statement on remote server 'RiskFabric_ASDB'.

In rare cases, when attempting to create a new risk vector in the Analyzer, the following error is also logged in the RiskFabric relational database table dbo.Log_SQL:

SQLLogType

Detail

EXCEEDED spAnalyzer_EntityScoperFilterByMeasureAndDimension_GetAll
ERROR
Error: Error parsing column <number> (FilterValueType=MDX - String) ...** Inner Exception ** Error: Requested value 'MDX' was not found....

Environment

Release : 6.x

Component : Risk Vectors

Cause

ICA version 6.5.4 (6.5.4.0000) queries the RiskFabric cube using the OPENQUERY method for executing MDX statements and is incompatible with the EXECUTE_AT execution method and setting added to version 6.5.4 MP1 (6.5.4.0100) for cube queries.

This condition and these symptoms may be caused by any of the following:

  1. One or more risk vector definitions are not converted to JSON and the general portal setting MDX Scoper Execution Method is set to EXECUTE AT
  2. Risk vector definitions stored as JSON were corrupted during the upgrade to MP1 and contain unexpected HTML encodings. For example, one or more risk vector RiskQuery values have HTML-encoded characters in place of the characters > and ' (single quote). These are formatted as JSON. Consequently, the stored procedure passes the entire JSON wrapper in lieu of parsing the individual SQL and MDX queries.
  3. The inability to create a new risk vector in the Analyzer is caused by installing or upgrading to 6.5.4 MP1 and later restoring a backup of the Risk Fabric Server Web folder on the application server from the original 6.5.4 installation.

Resolution

The following query will confirm whether one or more risk vector definitions have not been converted to JSON:

USE RiskFabric;
GO

WITH cte AS
(
 SELECT RiskQuery
 FROM dbo.UserRiskVectors
 WHERE RiskQuery LIKE 'SELECT%'
 
 UNION
 
 SELECT RiskQuery
 FROM dbo.PersonRiskVectors
 WHERE RiskQuery LIKE 'SELECT%'
 
 UNION

 SELECT RiskQuery
 FROM dbo.ApplicationRiskVectors
 WHERE RiskQuery LIKE 'SELECT%'
 
 UNION
 
 SELECT RiskQuery
 FROM dbo.ComputerEndpointRiskVectors
 WHERE RiskQuery LIKE 'SELECT%'
 
  UNION
 
  SELECT RiskQuery
 FROM dbo.IPRiskVectors
 WHERE RiskQuery LIKE 'SELECT%'
  )

SELECT COUNT(*) AS "Risk_Vectors_Requiring_Conversion"
FROM cte;

If the query returns a result greater than 0, follow this procedure:

  1. On the server hosting IIS and the ICA application, run a command prompt as an administrator with sufficient privileges to query the RiskFabric relational database
  2. Navigate to the folder \Program Files\Bay Dynamics\Risk Fabric Server Web\RiskFabric.CommandR
    NOTE: The default installation path is on the system drive (typically C:\); your location may vary.
  3. Execute the following command:
    RiskFabric.CommandR.exe SyncAnalyzerObjects "Data Source=<database_server_hostname>[/<named_instance>][,<alternate_port_number>];Initial Catalog=RiskFabric;Integrated Security=SSPI;" RiskVector

If this command fails or risk vector definitions were corrupted during the upgrade to 6.5.4 MP1, each affected risk vector's RiskQuery value must be edited to remove any HTML encodings. This can be done manually with the assistance of Broadcom support or by deleting and re-creating the affected risk vector(s). Contact Broadcom support to discuss these options.

If a backup of 6.5.4 was restored in an environment running 6.5.4 MP1 or greater, follow this procedure:

  1. With the assistance of a Microsoft SQL Server DBA, create a backup of the RiskFabric relational database
  2. Create a backup of the following folder on the application (IIS) server:
    %SystemDrive%\Program Files\Bay Dynamics\Risk Fabric Server Web
  3. On the IIS server, open Internet Information Services (IIS) Manager and stop the RiskFabricAppPool
  4. On the IIS server, run the Symantec ICA Installation software and select the option Full Install
  5. When prompted, select the existing Website NamePort, and Website URL, as well as the existing Installation DirectoryService Account, and Administrator Account
  6. When prompted, select the existing SQL Server host server and DatabaseAnalysis Services host server and DatabaseConnection Credentials, and Default Domain
  7. If you previously installed the database utilities with MP1, do not install them again
  8. Select the option to enable verbose logging during installation and save the verbose log once the installation has completed
    NOTE: If errors or warnings were reported, also save that version of the log. Review the error(s) in the log to determine the cause(s) of failure, create a support case one the Broadcom Support Portal, and attach the log files to the case
  9. If for any reason you're unable to select the existing website, SQL database, or SSAS database to proceed with the installation, follow the procedure in the readme.txt file bundled with the installer for 6.5.4 MP1 HF1.