000036731 - Error message in RSA NetWitness Endpoint: "Could not find server 'siliserv\ecatsql1' in sys.servers"

Document created by RSA Customer Support Employee on Sep 17, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036731
Applies ToRSA Product Set: NetWitness Endpoint
RSA Product/Service Type: NetWitness Endpoint
RSA Version/Condition: 4.3.x, 4.4.x
Platform: Windows
 
IssueDuring normal use of the UI application or in errors seen in the database, the following error message is seen, possibly as a popup message when clicking on machines in the Machines tab of the UI:

 

System.Data.SqlClient.SqlException (0x80131904): Could not find server 'siliserv\ecatsql1' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at DatabaseTools.AsyncPagedDataLoad`1.LoadDataThreadProc(PagedThreadParameters aThreadParameter) ClientConnectionId:82e3d252-8804-433b-aef3-5e27092552bb
Error Number:7202,State:2,Class:11


 
CauseThis error is caused by attempting to access data that is not actually present in the database. In the case of clicking on a module from the UI, the machine has actually been rolled off and removed, but the UI cache has not cleared sufficiently to reflect this in the UI. Consequently, the machine, which will usually have a very old Last Seen date and be offline, will not open.

This is not the only instance where this error could be generated, but its the most prevalent one.
ResolutionFirst, it must be recognized that in normal circumstances, this is data that has legitimately been rolled off and is no longer valid on the system. In the case of Machines in the Machines tab, the proper procedure is to clear the UI cache.

Follow the steps in kb 000033129 to clear the cache.
NotesThere has been confusion on what the meaning of this error message indicates in the past. This kb is also meant to clear up that confusion.

Attachments

    Outcomes