An error occurred during client rendering.,An error has occurred during report processing.,The connection is not open.,Query execution failed for data

If using sql server reporting service and the report's datasource connected to Microsoft Sql Server 2008 Analysis services. When you are opening the report by using a non-administrative account you may receive different error messages. The error messages will vary depends on credential settings of datasource in report manager In case of windows integrated security If you are using windows integrated security you will receive the following error messages. A) An error occurred during client rendering. B) An error has occurred during report processing. C) Query execution failed for dataset ''. D) The connection is not open. If your report manager configuration does not require any credentials error message will be The current action cannot be completed. The user data source credentials do not meet the requirements to run this report. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified. (rsInvalidDataSourceCredentialSetting) If your configuration is like stored securely in the report or using Os credentials when connecting datasource or impersonate authentication or the user specified have sufficiant permissions the message will be as of first case. Reasons TACS LLC Dubai Time Attendance Dubai Access Control System Gate Barrier HRMS Solutions EID Reader Software EID Reader Building Maintanance UHF Reader

When you open the report, the data source of the report connects to SQL Server 2008 Analysis Services by using the data source credential. After the connection is established, successive requests to SQL Server 2008 Analysis Services do not reuse the data source credential. Instead, successive requests use the credential of the current user. This causes the problem that is mentioned in the "Symptoms" section.

Ref : http://support.microsoft.com/kb/973588 Solution You must use SQL Server 2008 Service Pack 1 (SP1) to fix this problem HAPPY PROGRAMMING