SharePoint 2010: Problems with integration with Reporting Services

[visioneye]

The configuration of the integration of SQL Server Reporting Services (SSRS) in SharePoint 2010 is very easy when working with single-server installations. However, this change when we have a farm mode installation on the one hand we have our database server and the other our front web (for a small farm). But while the ways to configure the integration of SSRS 2010 are clear, we can find problems to make integration work effectively. Fortunately, Microsoft has placed at our disposal a page where you can find different types of errors that can occur and the solution for them . In our case, we have been very useful for operational SSRS integration with SharePoint on the farm that we have implemented in the CIIN. Can anyone over there can explain me more about the problems with integration with Reporting Services.

[Kirmiac]

If you run into this predicament, the first thing you do is run should the add-in manually. This will permit you to get the binaries installed and run the custom action (Usually the reason the add-in Fails to install) manually. If you do this, view the messages you can display and the reason it failed Without HAVING to run the installer over and over. Here are the steps to run the installer in files-only mode and running the custom action subsequently:

1. Open a command prompt.
2. Change to the directory Where the .Msi file reside.
3. Type msiexec / i SharePointRS.msi SKIPCA = 1
4. The installer opens. Just follow the normal flow, and it should finish lucratively.
5. Type cd% temp%
6. Type rscustomaction / i

[HellBoy21]

There Are Only A Few rare WHERE marry this will help resolve the issue You are HAVING. For example, if the Reporting Services binary files Have Been somehow corrupted or Are Not all the correct version, uninstalling and reinstalling Can Be useful. These types of Issues Should Be very clear, Because You Should Receive Various errors in Regards to Failure loading assemblies or assembly mismatches in versions. These errors dog Appear in the event log as well as the Reporting Services error logs. Uninstalling and reinstalling Reporting Services not does it eliminate the database connected with it. Therefore, if you reconnect to the old database after you reinstall Reporting Services, the dilemma (s) before you were experiencing are likely to return. Also this is a very time overwhelming process because you have to install Reporting Services and then relate service packs and hot fixes to get back to the state in before you were you uninstalled the program. Any custom amendments to the Reporting Services configuration files will need to be made again.

[Zenon]

I would like to discuss about some possible error messages, which is "SharePoint content service is null. Report Server may not have joined the SharePoint farm, or Report Server service account may not have been granted access to the farm." And the following are the Resolution if this problem is encountered:

• You will require installing the SharePoint Web front end from the media. This does not have to be a complete installation, just the web front end installation. The installer for this should connect the Reporting Services server to the SharePoint farm. If it does not, you can rerun the SharePoint Configuration Wizard and pursue the steps to join the server to the SharePoint farm.
• These accounts are involuntarily denied access to the SharePoint databases if they are located on the same server, THEREFORE because Reporting Services and not can be used. You will need to modify both the application pool and the Windows service to run under a domain account.
• Substantiate that the database is in SharePoint Integrated mode on the Database Setup Portion of the Reporting Services Configuration tool. If it is not, you will need to create a new database in integrated mode.
• Install SP2 or later for SQL Server 2005.

[Rob Dizzle]

Sometimes, it also pops up saying that "Object Reference not set to an instance of an object". This CAN OCCUR inaccuracy if, after the Reporting Services Add-in is installed and activated on a SharePoint site anthology, SharePoint is uninstalled, and the user attaches the content databases Then that were formerly used with the Reporting Services integration to a new SharePoint Web Application. Your option is to get a memory dump on the rscustomaction.exe process using WinDbg to determine Where the failure occurred. You can do this by Following These Steps:

1. Open WinDbg, and click File, and Then click Attach to Executable.
2. Select the file rscustomaction.exe.
3. In the Arguments box, type / i.
4. Set the Start value to the directory Directory rscustomaction.exe reside in.
5. Type g to get the process running and wait for the AV to occur.
6. If the error is Not an AV (0xc0000005), type g to continue execution Until it occurs.
7. After WinDBG That breaks on error type. Dump / ma c: \ dumps \ mydump.dmp. to write out the dump file.