Today I saw this error message and was able to fix by renaming the original source files in Visual Studio 2010 to remove special characters. After checking on Google it appears that symbols such as ~!@#$%^&* may cause issues. Lesson learned: keep file names simple so SharePoint is happy.
Add-SPSolution: Failed to extract the cab file in the solution.
The below error might appear if you are using Access Services 2010 for the first time. The local Access 2010 publishing wizard will create RDL and RSDS files for reports you have. However, the SSRS server side configuration may require a minor update to enable ADS (Access Data Server). See http://technet.microsoft.com/en-us/library/ee662542.aspx for full details.
The instructions are pretty clear except for where to find the “rssrvpolicy.config” file. Mine was under C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServer. Hope that helps. If you’d like to learn Access Service 2010 on your system be sure to check out the Northwind 2010 Web Database at http://office.microsoft.com/en-us/templates/results.aspx?qu=northwind&ex=1
An error has occurred during report processing. (rsProcessingAborted) An attempt has been made to use a data extension ‘ADS’ that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound)
An error has occurred during report processing. (rsProcessingAborted) The Group expression for the grouping ‘Group1’ contains an error: Request for the permission of type ‘Microsoft.Office.Access.Server.Security.AccessServicesPermission, Microsoft.Office.Access.Server.Security, Version=184.108.40.206, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ failed. (rsRuntimeErrorInExpression)
Many SharePoint farms display the below warning. Unfortunately it tends to get people’s blood pressure up. While it’s good to know about your farm, some of the underlying conditions may persist or even by expected. A bright red color on the homepage creates a sense of panic which generally isn’t helpful. For my CA homepage I made a simple CSS addition via Content Editor Web Part to override the background color.
I still see the messages, but they come across less like a blaring three alarm fire and more like a gentle reminder.
The SharePoint Health Analyzer has detected some critical issues that require your attention. View these issues.
Below is the internal code for a Content Editor Web Part to apply more calm color styling.