This is a generic error message that can be recorded for a wide variety of problems. Basically, any time the Report Server has problems initiating an application it will record this message along with:
- Application name (i.e. WindowsService_21, WindowsService_13, WindowsService_8)
- Error description (and that can vary widely). Examples: "The endpoint cannot be created.", "The report server has encountered a configuration errorr", etc.
When applying various suggestions, one should only use those that are for the same error message.
Here are few suggestions:
Error: "The report server has encountered a configuration error" - Check if the account ASPNET is added in SQLServer2005ReportingServicesWebServiceUsers$<YourMachineName> group, if not, add it. Also, the web service identity has to be configured in the reporting services configure manager.
* * *
Error: "The endpoint cannot be created." - I used the following command:
netsh http show urlacl
From the output of the command I could see that the endpoint is running as NETWORK_SERVICE. I went into C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPM2010EVAL\Reporting Services directory and gave network service the rights to read and execute. When I restarted the SQL Service, it started to work.
* * *
Error: "The report server has encountered a configuration error." - Adding the SQL Server Service as dependency for the SQL Reporting service may help with this error.
* * *
Error: " Could not load file or assembly" - This may indicate that some required components are missing. Investigate the name of the missing application as shown in the event description and verify if that application should be installed. Either install the application or remove it from the actual configuration of the Report Server.