An error has occurred during report processing. (rsProcessingAborted)

When running SQL Reporting Services Reports deployed for Dynamics GP 2010 we receive the error:

"An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'DataSourceGPCompany'. (rsErrorOpeningConnection)"
 
Resolution:
As the SQL Server Reporting Services service is on a different server to the database server we could not use the Windows authentication for the datasources.  To correct amend each datasource (one per company and one for Dynamics database), and mark each to use SQL Server authentication.  Use a SQL login to with sufficent rights

Parser Error Message: Cannot use 'partitionResolver' unless the mode is 'StateServer' or 'SQLServer'

Installed SSRS 2005 on a Sharepoint MOSS 2007 server and what a pain as I realise SSRS did not work due to confliction with MOSS. Error was shown when trying to access it:

"Parser Error Message: Cannot use 'partitionResolver' unless the mode is 'StateServer' or 'SQLServer'"

1. Create a new virtual directory off \inetpub\wwwroot\
2. Give it a specific port number I used SSRS / 87
3. Configure (in SSRS) a new "Report Server Virtual Directory"
4. Configure (in SSRS) a new "Report Manager Virtual Directory"
5. Go to Web Service Identity and click the New button next to Report Server
6. Create a new App Pool for RS to run within, I used SSRSAppPool
7. Set the authenticated user for the new app pool to the SQL Server Service account you used to set up MOSS such as OSS_USER
8. This should have all the SQL permissions you need to run SSRS (I hope...)
9. Set Report Server and Report Manager to the new app pool and click Apply
10. After making these changes run IISRESET go to the following URL's:
http://Myserver:87/ReportServer/
http://Myserver:87/Reports/

Microsoft SQL Server 2008 R2 November CTP Report Builder 3.0

Microsoft SQL Server 2008 R2 Report Builder 3.0 provides an intuitive report authoring environment for business and power users. It supports the full capabilities of SQL Server 2008 R2 Reporting Services. The download provides a stand-alone installer for Report Builder 3.0.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f78b6b1e-8ccb-407a-bc3e-7955d60e1a6c

SSRS and forcing rectangle to not overlap on to second page

Using SSRS 2005 we had an issue with a report that contained a table and a rectangle at the bottom of the report. The rectangle acted as a printed form at the bottom of the report, however if the table contained too many lines then part of the rectangle would print on the next page. The solution seems to be to put the a new list box underneath the rectangle and this then forced the rectangle to always print as a whole

what a pain. I believe this is easier in SSRS 2008

The value provided for the report parameter 'XXXX' is not valid for its type

I received an error in Visual studion 2005 when trying to pass a parameter to my datasource. My parameter was a datetime field which the user uses a calendar to select their require date. In the datasource was a column called TRXDATE which was a datetime column. Everytime i tried to rest the report within Visual Basic I received the following error ('XXXX' being my parameter)

The value provided for the report parameter 'XXXX' is not valid for its type

After a few wasted hours which i will never get back, I realised that the problem was down to Visual Basic 2005 and nothing to do with my report. When publishing the report to Report Server it worked fine.

My advice when receiving this issue is to try the following:

1. Test the datasource in SQL. Check that it works with a date being passed through with the format of YYYY-MM-DD. If no then the problem is the data source
2. Publish the report to reportserver and test. If problem then check parameter and datasource setup in Visual Studio 2005
3. Look forward to the upgrade to SQL Server 2008

'/' is an unexpected token. The expected token is '='. Line 9, position 33.

When running a large SQL Server Reporting Services 2005 report I was receiving the following error:

'/' is an unexpected token. The expected token is '='. Line 9, position 33.

Resolution was to change the Web Config file, located at the following location - C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer. I adjusted the executionTimeout element from 90 to 900 in this file to correct the issue.