SQL Server 2008-2012 Reporting Services (Events)

Version 2

    This template checks critical events of Microsoft SQL Server 2008-2012 Reporting Services.

    Prerequisites: WMI access to the target server.

    Credentials: Windows Administrator on the target server.


    Monitored Components

    Scheduling: SQL Server Agent Must Be Running

    This monitor returns the following event: SQL Server Agent must be running when you define a scheduled operation (for example, report subscription and delivery).

    Event ID: 106 (Application Log)

     

    No Connection to Report Server Database

    This monitor returns the following event: The SQL Server Report Server service cannot connect to the report server database. This error occurs during a service restart if a connection to the report server database cannot be established.

    Start the Database Engine service if it is not running and check that remote connections are enabled for TCP/IP protocol. Use the Reporting Services Configuration tool to configure the report server database and service account.

    Event ID: 107 (Application Log)

     

    Extensions Loading Error

    This monitor returns the following event: Report Server cannot load a delivery, data processing, or rendering extension. Most likely, this is the result of an incomplete deployment or removal of an extension.

    Event ID: 108 (Application Log)

     

    Trace Log Creation Error

    This monitor returns the following event: Report Server cannot create the trace log.

    Event ID: 111 (Application Log)

     

    Possible Denial of Service Attack

    This monitor returns the following event: The report server has detected a possible denial of service attack.

    Event ID: 112 (Application Log)

     

    Performance Counters Creation Error

    This monitor returns the following event: The report server cannot create a performance counter.

    Event ID: 113 (Application Log)

     

    No Connection to Report Manager

    This monitor returns the following event: Report Manager cannot connect to the Report Server service.

    Event ID: 114 (Application Log)

     

    Internal Error

    This monitor returns the following event: An internal error occurred.

    Event ID: 116 (Application Log)

     

    Database Invalid Version

    This monitor returns the following event: The report server database is an invalid version. For more information, see http://technet.microsoft.com/en-us/library/ms156468(v=sql.100).aspx

    Event ID: 117 (Application Log)

     

    Access Denied to Server Database

    This monitor returns the following event: Report server has not been granted access to the contents of the report server database.

    Event ID: 119 (Application Log)

     

    Symmetric Key Cannot Be Decrypted

    This monitor returns the following event: The symmetric key cannot be decrypted. Most likely, the there has been a change to the account that the service runs as.

    Event ID: 120 (Application Log)

     

    RPC Failed to Start

    This monitor returns the following event: Remote Procedure Call (RPC) Service failed to start.

    Event ID: 121 (Application Log)

     

    No Connection to SMTP Server

    This monitor returns the following event: Scheduling and Delivery Processor cannot connect to the SMTP server that is used for e-mail delivery.

    Event ID: 122 (Application Log)

     

    Trace Log Writing Error

    This monitor returns the following event: The report server failed to write to the trace log.

    Event ID: 123 (Application Log)

     

    Components Version Mismatch

    This monitor returns the following event: Reporting Services components from different editions cannot be used together.

    Event ID: 128 (Application Log)

     

    Configuration Decryption Error

    This monitor returns the following event: An encrypted configuration file setting in cannot be decrypted.

    Event ID: 129 (Application Log)

     

    Configuration File Not Found

    This monitor returns the following event: Report server cannot find the configuration file. Configuration files are required by the report server.

    Event ID: 130 (Application Log)

     

    User Data Decryption Error

    This monitor returns the following event: An encrypted user data value could not be decrypted.

    Event ID: 131 (Application Log)

     

    User Data Encryption Error

    This monitor returns the following event: A failure occurred during encryption of user data. The value cannot be saved.

    Event ID: 132 (Application Log)

     

    Configuration File Loading Error

    This monitor returns the following event: A configuration file failed to load. This error may occur if the XML is not valid.

    Event ID: 133 (Application Log)

     

    Configuration File Encryption Error

    This monitor returns the following event: The report server failed to encrypt values for a setting in a configuration file.

    Event ID: 134 (Application Log)

     

    Portions of this document are based on the following sources:
    http://technet.microsoft.com/en-us/library/ms165307(v=sql.100).aspx
    http://technet.microsoft.com/en-us/library/cc627471(v=sql.110).aspx
    http://technet.microsoft.com/en-us/library/ms159650.aspx

    Last updated: 2/18/2014