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)

   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.

a.       Check, if your SharePoint Frontend Server Network Service has appropriate rights on your SharePoint_Config Database (while executing the rsCustomAction, the SharePoint Server directly tries to set several objects in the config DB).

b.   Now run rsCustomAction again.

Yes, I know I should have started this much earlier. I didn’t got the time and right personal priority for being a Blogger. But this should change now!

So, hopefully I can find much more Things to report and to give you The right thing for Reports!

Best Regards,
Volker

Before I begin to explain, what detailed steps are necessary, let me shortly mention where you should know one’s way about Reporting topics:

•        Expressions…
  ..can be used in many ways. You can’t know everything about but some basics should be familiar to you.
  
•        Calculated fields…
  …can be added to Datasets in order to use some additional columns with formulas or as they are already titled: with calculations.

Let’s assume that you want to report data out of a SSAS cube. But you don’t like to spend hours on writing the right MDX query. Here is a solution to reduce the need of complex MDX with 1 additional action you have to take on your dimension. Just add another attribute indicating the direction of your KPI. Will it increase the start value or decrease? I will explain the reason for this later on.

1.      For my example I use a simple T-SQL query to simulate the cubes’ output to SSRS:

select ’dev1’ as description, 120 as val1, 1 as direction
union
select ’dev2’ as description, 20 as val1, -1 as direction
union
select ’dev3’ as description, 15 as val1, -1 as direction
union
select ’dev4’ as description, 10 as val1, -1 as direction
union
select ’dev5’ as description, 30 as val1, 1 as direction
union
select ’dev6’ as description, 20 as val1, 1 as direction

The result looks like this:

2.      Define a Dataset with the query above (including a Data Source which you need to create first).

3.      Now add a Calculated Field with the name “Val2” and the expression:
=Fields!val1.Value*Fields!Direction.Value

4.      Drag a Chart from the toolbox and drop it to the Report body and select "Range" as Type

5.      Drag the column val1 from the Report Data Area and drop it to the data fields area

6.      Edit the Series Properties and replace the Top Value field by the following expression:

=Fields!val1.Value +

IIF(Fields!Direction.Value=1,

       Previous(RunningValue(Fields!val2.Value,Sum,Nothing)),

       RunningValue(Fields!val2.Value,Sum,Nothing)))

replace the Buttom Value field by the following expression:

=IIF(RowNumber("DataSet1")=1 and Fields!Direction.Value=1,

0,

IIF(Fields!Direction.Value=1,

       Previous(RunningValue(Fields!val2.Value,Sum,Nothing)),

       RunningValue(Fields!val2.Value,Sum,Nothing)))

Notice:
The RunningValue is always summerized on postive and negative values of the Calculated Field.
The beam needs to be positive without Plus or Minus sign. This little trick guarantees the right position.

7.      Drag the column description from the Report Data Area and drop it to the category fields area

8.     Let’s improve the column colors by setting the Fill Color of your <Expr> Series to the expression:

=IIF(Fields!Direction.Value=1,"LimeGreen","Red")

9.    Finish – you’re done except improving Titles, Legends, etc…