.png)
Report Server Events
SQL Server 2000
The following report server events are recorded in the 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> cannot connect to the report server database. For more information, see Troubleshooting Server and Database Problems. |
| 108 | Error | Extension | Report Server
Report Manager | <Source> cannot load a delivery, data processing, or rendering extension.
Most likely, this is a result of an incomplete deployment or removal of an extension. For more information, see Deploying a Data Processing Extension and Deploying a Delivery Extension. |
| 109 | Information | Management | Report Server
Report Manager | A configuration file has been modified. For more information, see Reporting Services Configuration Files. |
| 110 | Warning | Management | Report Server
Report Manager | A setting in one of the configuration files has been modified such that it is no longer valid. A default value will be used instead. For more information, see Reporting Services Configuration Files. |
| 111 | Error | Logging | Report Server
Report Manager | <Source> cannot create the trace log. For more information, see Reporting Services Trace Logs. |
| 112 | Warning | Security | Report Server | The report server has detected a possible denial of service attack. For more information, search on denial of service attack in Books Online. |
| 113 | Error | Logging | Report Server | The report server cannot create a performance counter. |
| 114 | Error | Startup/Shutdown | Report Manager | Report Manager cannot connect to the Report Server service. |
| 115 | Warning | Scheduling | Scheduling and Delivery Processor | A scheduled task in the SQL Server Agent queue has been modified or deleted. |
| 116 | Error | Internal | Report Server
Report Manager Scheduling and Delivery Processor | An internal error occurred. |
| 117 | Error | Startup/Shutdown | Report Server | The report server database is an invalid version. For more information, see Troubleshooting Server and Database Problems. |
| 118 | Warning | Logging | Report Server
Report Manager | The trace log is not at the expected directory location; a new trace log will be created in the default directory. For more information, see Reporting Services Trace Logs. |
| 119 | Error | Activation | Report Server
Scheduling and Delivery Processor | <Source> has not been granted access to the contents of the report server database. |
| 120 | Error | Activation | Report Server | The symmetric key cannot be decrypted. Most likely, the there has been a change to the account that the service runs as. For more information, see Managing Encryption Keys. |
| 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 cannot connect to the SMTP server that is used for e-mail delivery. For more information about SMTP server connections, see Configuring a Report Server for E-Mail Delivery. |
| 123 | Warning | Logging | Report Server
Report Manager | The report server failed to write to the trace log. For more information about trace logs, see Reporting Services Trace Logs. |
| 124 | Information | Activation | Report Server | The Report Server service has been activated. For more information about activation, see Activating a Report Server Instance. |
| 125 | Information | Activation | Report Server | The key used for encrypting data was successfully extracted. For more information about keys, see Managing Encryption Keys. |
| 126 | Information | Activation | Report Server | The key used for encrypting data was successfully applied. For more information about keys, see Managing Encryption Keys. |
| 127 | Information | Activation | Report Server | Encrypted content was successfully removed from the report server database. For more information about deleting non-recoverable encrypted data, see Managing Encryption Keys. |
| 128 | Error | Activation | Report Server | Reporting Services components from different editions cannot be used together. |
| 129 | Error | Management | Report Server
Scheduling and Delivery Processor | An encrypted configuration file setting in cannot be decrypted. |
| 130 | Error | Management | Report Server
Scheduling and Delivery Processor | <Source> cannot find the configuration file. Configuration files are required by the report server. |
| 131 | Error | Security | Report Server
Scheduling and Delivery Processor | An encrypted user data value could not be decrypted. |
| 132 | Error | Security | Report Server | A failure occurred during encryption of user data. The value cannot be saved. |
| 133 | Error | Management | Report Server
Report Manager Scheduling and Delivery Processor | A configuration file failed to load. This error may occur if the XML is not valid. |
| 134 | Error | Management | Report Server | The report server failed to encrypt values for a setting in a configuration file. |
