000033899 - Windows Machine throws exception when opened from machine View/Modules Summary tab (L2Analyst or L1Analyst) in RSA ECAT

Document created by RSA Customer Support Employee on Aug 30, 2016Last modified by RSA Customer Support on May 3, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033899
Applies ToRSA Product Set: ECAT, NetWitness Endpoint
RSA Version/Condition:,, 4.2.x, 4.3.x, 4.4.x
Platform: Windows
O/S Version: 2008 Server R2, 2012 Server
IssueUnhandled exceptions are being thrown when attempting to access the Modules Summary tab if they do so using the ECAT User L1 Analyst or L2 Analyst user permissions.
CauseAfter upgrading from ECAT or to any higher version, an unhandled exception is thrown if an L2 Analyst or L1 Analyst user clicks on an item in the Modules Summary tab.  

This is because for ECAT and, the Linked Servers were created as “@srvproduct = N'MSSQL', @provider = N'SQLNCLI',” which have been changed post to “@srvproduct=N'MSSQL_NATIVE_CLIENT', @provider=N'SQLNCLI'.”
ResolutionAfter upgrading from ECAT or, do the following:
  1. On the ECAT Primary Server, extract the existing LinkedServer connection as follows:
    In SSMS, connect to your server instance > Server Objects > LinkedServers > XXX (Linked Server of the Primary Server as well as Linked Server of any Secondary Servers) > right-click and select Script Linked Server As > Create To > New Query Window > Save this file.
  2. On the ECAT Primary Server, drop the linked servers for Secondary if the srvproduct is “MSSQL” (this can be checked in the script generated in step 1). Do this for both the linked servers if using multi-server configuration.
  3. Execute the following script on the ECAT Primary Server, by providing the details of the Secondary Server:

DECLARE @RemoteUserPasswordNVARCHAR(50)
DECLARE @FK_LinkedServersINT
DECLARE @ErrorMessageNVARCHAR(2048)
-- TODO: Set parameter values here.
EXECUTE @RC= [dbo].[usp_InsertLinkedServer]
  ,@FK_LinkedServers OUTPUT
  ,@ErrorMessage OUTPUT


  1. After step 3 is executed successfully, execute the following stored procedure on the ECAT Primary Server:

Exec usp_PropagateMCSCredential
NotesThis article assumes there is in fact secondary servers associated with the deployment of the ECAT servers, otherwise, we don't expect to see this error.