Installing SQL Server 2008 Reporting Services Addin (rsSharePoint) x86 or x64

Artigo
02/24/2010

Did you already install Reporting Services in every possible combination? I guess “no”, but you would agree that you had problems at least during one installation. A common problem is the integration of SSRS into SharePoint regardless if you install SSRS 2008, R2 or 2005, regardless if you use SharePoint 2007 or 2010.

The first step is always to configure the Report Server including Service Account and Database for the “Integrated Mode” – usually no problem.

But now if you try to run the “rsSharePoint.msi” (especially in x64 Environments), you are sitting in front of your Server session, waiting for the completion of the last step “Removing backup files”. If you are getting an error message, the nightmare begins:

What went wrong? Where can you see the cause of the error?

First resolution attempt:
https://technet.microsoft.com/en-us/library/aa905871.aspx

If it doesn’t fit, here’s a possible solution:

1. Check the Log-file provided by the rsCustomAction.exe

a. Open the Command prompt

b. Change directory by typing “cd %temp%” (if you’re not on drive C – just change the drive after typing the last command)

c. Now go one directory backwards by typing “cd ..”

d. Find the appropriate log file e.g. “RS_SP_0.log” and open it

e. If it looks like the following, proceed to step 2

User: SYSTEM

Installing Report Server feature.

Calling copyappbincontents command.

copyappbincontents command completed successfully.

Adding ReportServer feature to farm.

Install error: A web configuration modification operation is already running.

Error details: System.InvalidOperationException: A web configuration modification operation is already running.

at Microsoft.SharePoint.Administration.SPWebService.ApplyWebConfigModifications()

at Microsoft.ReportingServices.SharePoint.UI.ReportServerFeature.AddWebConfigModifications(SPWebService service)

at Microsoft.ReportingServices.SharePoint.UI.ReportServerFeature.FeatureInstalled(SPFeatureReceiverProperties properties)

at Microsoft.SharePoint.Administration.SPFeatureDefinition.DoInstallationCallout(Boolean fInstall)

at Microsoft.SharePoint.Administration.SPFeatureDefinition.Install()

at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.Add(String relativePathToFeatureManifest, Guid solutionId, Boolean force)

at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.Add(String relativePathToFeatureManifest, Guid solutionId)

at RSCustomAction.ReportServerFeature.<>c__DisplayClass3.<AddFeatureToFarm>b__1()

at RSCustomAction.ReportServerFeature.RetryFailedOperation(RetryFunction function, Int32 numTries)

at RSCustomAction.ReportServerFeature.AddFeatureToFarm(Guid featureGuid, Guid solutionGuid, String featureFolderName, Int32 numTries)

at RSCustomAction.ReportServerFeature.AddToFarm(Int32 numTries)

at RSCustomAction.RSFeatureSetup.Install(Boolean repair, Int32 addRetries)

Uninstalling Report Server feature.

Uninstalling ReportServer feature.

ReportServer feature was uninstalled.

Uninstalling ReportServerItemSync feature.

ReportServerItemSync feature was uninstalled.

Stopping W3SVC service.

2. The typical cause for the exception above is:

a. A previous installation effort caused a new SharePoint Timer job definition which hasn’t been deleted correctly (therefore you get the highlighted exception message):
"Windows SharePoint Services Web.Config Update" with a schedule type of "one-time"

b. When you try to run manually “rsCustomAction –i”, you will get the error again :-(.

c. So, before running the rsCustomAction again, just delete the timer job “Windows SharePoint Services Web.Config Update” (you’ll find it under Central Administation – Operations – Timer job definitions)

3. If your logfile looks like this:

User: SYSTEM

Installing Report Server feature.

Calling copyappbincontents command.

copyappbincontents command completed successfully.

Adding ReportServer feature to farm.

Install error: The EXECUTE permission was denied on the object 'proc_putObject', database 'SharePoint_Config', schema 'dbo'.

Error details: System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'proc_putObject', database 'SharePoint_Config', schema 'dbo'.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)

at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)

at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure)

at Microsoft.SharePoint.Administration.SPPersistedObject.Update()

at Microsoft.SharePoint.Administration.SPPersistedObject.Update(Boolean ensure)

at Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T newObj, Boolean ensure)

at Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T newObj)