Errors and events reference (Reporting Services)
This article provides information about errors and events for SQL Server Reporting Services. The Reporting Services log files also contain error information. For more information about the types of log files that are available and how to view the logs, see Reporting Services log files and sources.
Cause and resolution for reporting services error messages
Cause and resolution information is available for the errors most frequently searched for on the Microsoft web sites. For more information, see Cause and resolution of Reporting Services errors.
Report server events
The following report server events are recorded in the Microsoft Windows application log.
| Event ID | Type | Category | Source | Description |
|---|---|---|---|---|
| 106 | Error | Scheduling | Report Server | SQL Server Agent must be running when you define a scheduled operation (for example, report subscription and delivery). |
| 107 | Error | Startup/Shutdown | Report Server Scheduling and Delivery Processor |
<Source> can't connect to the report server database. For more information, see Report Server Windows Service (MSSQLServer) 107. |
| 108 | Error | Extension | Report Server web portal |
<Source> can't load a delivery, data processing, or rendering extension. Most likely, this error is the result of an incomplete deployment or removal of an extension. For more information, see Deploy a data processing extension and Deploy a delivery extension. |
| 109 | Information | Management | Report Server web portal |
A configuration file was modified. For more information, see Reporting Services configuration files. |
| 110 | Warning | Management | Report Server web portal |
A setting in one of the configuration files was modified such that it's no longer valid. A default value is used instead. For more information, see Reporting Services configuration files. |
| 111 | Error | Logging | Report Server web portal |
<Source> can't create the trace log. For more information, see Report server service trace log. |
| 112 | Warning | Security | Report Server | The report server detected a possible denial of service attack. For more information, see Reporting Services security and protection. |
| 113 | Error | Logging | Report Server | The report server can't create a performance counter. |
| 114 | Error | Startup/Shutdown | web portal | The web portal can't connect to the Report Server service. |
| 115 | Warning | Scheduling | Scheduling and Delivery Processor | A scheduled task in the SQL Server Agent queue was modified or deleted. |
| 116 | Error | Internal | Report Server web portal Scheduling and Delivery Processor |
An internal error occurred. |
| 117 | Error | Startup/Shutdown | Report Server | The report server database is an invalid version. |
| 118 | Warning | Logging | Report Server web portal |
The trace log isn't at the expected directory location; a new trace log is created in the default directory. For more information, see Report server service trace log. |
| 119 | Error | Activation | Report Server Scheduling and Delivery Processor |
<Source> wasn't granted access to the contents of the report server database. |
| 120 | Error | Activation | Report Server | The symmetric key can't be decrypted. Most likely, there was a change to the account that the service runs under. For more information, see Configure and manage encryption keys (Report Server Configuration Manager). |
| 121 | Error | Startup/Shutdown | Report Server | Remote Procedure Call (RPC) Service failed to start. |
| 122 | Warning | Delivery | Scheduling and Delivery Processor | Scheduling and Delivery Processor can't connect to the SMTP server that is used for e-mail delivery. For more information about SMTP server connections, see E-mail settings - Reporting Services native mode (Configuration Manager). |
| 123 | Warning | Logging | Report Server web portal |
The report server failed to write to the trace log. For more information about trace logs, see Report server service trace log. |
| 124 | Information | Activation | Report Server | The Report Server service was initialized. For more information, see Initialize a report server (Report Server Configuration Manager). |
| 125 | Information | Activation | Report Server | The key used for encrypting data was successfully extracted. For more information about keys, see Configure and manage encryption keys (Report Server Configuration Manager). |
| 126 | Information | Activation | Report Server | The key used for encrypting data was successfully applied. For more information about keys, see Configure and manage encryption keys (Report Server Configuration Manager). |
| 127 | Information | Activation | Report Server | Encrypted content was successfully removed from the report server database. For more information about deleting nonrecoverable encrypted data, see Configure and manage encryption keys (Report Server Configuration Manager). |
| 128 | Error | Activation | Report Server | Reporting Services components from different editions can't be used together. |
| 129 | Error | Management | Report Server Scheduling and Delivery Processor |
An encrypted configuration file setting can't be decrypted. |
| 130 | Error | Management | Report Server Scheduling and Delivery Processor |
<Source> can't find the configuration file. The report server requires configuration files. |
| 131 | Error | Security | Report Server Scheduling and Delivery Processor |
An encrypted user data value couldn't be decrypted. |
| 132 | Error | Security | Report Server | A failure occurred during encryption of user data. The value can't be saved. |
| 133 | Error | Management | Report Server web portal Scheduling and Delivery Processor |
A configuration file failed to load. This error might occur if the XML isn't valid. |
| 134 | Error | Management | Report Server | The report server failed to encrypt values for a setting in a configuration file. |