Answer My Searches

So I got this error when running a report in SQL Server Reporting Services that takes several minutes to run:

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

It turns out you just have to go to the web config file in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer and change the timeout value to something high enough.

(Be sure to back up your web config file before editing it.)

Source

One way to do this is to change the interactive size of the report to something very long or short. For example if you want 1000 rows per page (don’t ask!) you can change the interactive size length to something like 200 inches.

It takes some trial and error to find the right length to use.

More discussion here.

The trick is that the grand total needs to be the first group. So delete your existing groups, and then add your grand total group first. Then add back in your original groups.

I also set the group on expression to =1 so that it effectively groups on nothing and gives you a grand total over all the rows.

Just enter one of these expressions into the default parameter box when you’re setting up parameters in SQL Server Reporting Services:

=DateSerial(Year(Now), Month(Now), 1) for first day of the month and
=DateSerial(Year(Now), Month(Now)+1, 0) for the last day of the month.

Source

One day I went to Reporting Service’s Report Manager and tried to run a report. But instead of getting a beautiful report rendered in front of my eyes, I got this weird error message:

The encrypted value for the "UnattendedExecutionAccount\Password" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation)
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)

To fix this I went into Reporting Services Configuration, and then to the Execution Account section. I unchecked “specify an execution account” and then rechecked it, and applied the settings. After that my reports started working again.

By the way for the execution account I’m using LOCALMACHINE\ASPNET with a blank password.

Update:

The above solution didn’t end up working afterall. Instead i just left “specify an execution account” unchecked since I don’t seem to be using it for anything anyway.