Start a conversation

Error 'Unexpected error scanning SQL Server XXX, error: Could not load file or assembly' when auditing a SQL server

Versions / Builds Affected

EventsManager 2013 SR1 (20130606)

Status

Resolved

Problem Summary

EventsManager fails to retrieve events from a SQL server.

TT / JIRAID

322

How to Identify

To identify the issue you will find one of the following errors: 1. Go to Status > Job Activity > Operational History: Unexpected error scanning SQL Server DOMAIN\SERVER, error: Could not load file or assembly 'Microsoft.SqlServer.SqlEnum, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies 2. Open SQLcollector.log file : 2013-07-22, 15:53:36, 015, 0, 60c, d58, error, SQLCollector.dll, StartSQLScan, Unexpected error scanning SQL Server DOMAIN\SERVER, error: Could not load file or assembly 'Microsoft.SqlServer.SqlEnum, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified., internal 2013-07-22, 15:53:36, 062, 0, 60c, d58, error, SQLCollector.dll, StartSQLScan, Stack trace is: at GFILog.LogError(String message, Object[] args)

Workaround / Fix Details

Development has deployed a patch through EventsManager auto updates (20131009_ESM2013SR1_patch00)

Required Actions

Ensure that the customer is on the latest build (20130606) and have them ensure that auto updates are applied-specifically make sure that "20131009_ESM2013SR1_patch00" has been applied.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments