sql server reporting services: What were the problems with SP1 that SP2 fixed and what new problems
did SP2 cause?

The only problem I am aware of so far is if you use the ReportViewer control
that ships with VS 2005, doing a print preview has issues (I gather it
depends on the design of the report if there is a problem or not). There is
a work around, no hotfix yet that I have seen.

SP1 removed the select all from the multi-select parameters. There was a
hotfix for this (which I used), SP2 encorporated the hotfix.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]

There is a problem with the date picker control when running from
http:\\machine\reportserver.
It returns dates in US format. A few others have posted this problem on this
newsgroup.

It's fine when building in dev studio or when run from
\\machinename\reports.

I also have a problem deleting reports but no one else has reported this
issue.

Paul


[quoted text, click to view]

If your report has a subscription you cannot delete it. I couldn't delete my
subscription either so I resorted to SQL.I saw this problem prior to SP2.

If you need to delete subscriptions via SQL let me know.


--
Bruce Loehle-Conger
MVP SQL Server Reporting Services


[quoted text, click to view]

"Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in
news:#3NeVitcHHA.3960@TK2MSFTNGP04.phx.gbl:

[quoted text, click to view]

No, I didn't even think of that. It was failing from Report Manager (which
uses the web services interface). So I created SQL to do what I wanted.


--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

If I delete I get "An internal error occurred on the report server. See the
error log
for more details. (rsInternalError)"

I have tried the web interface and connecting to the report server through
SSMS.

I can overwrite by re-deploying. I can "move" a report to another folder but
it leaves the old copy in place.

Any ideas?

Report services is running under login NETWORK_SERVICES
SQL Server build 9.0.3152.


The error log contains
03/14/07 13:25:46, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
() failed (00000514)
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
supplied
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 4720
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags =
0x0
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr =
0x47405860
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
= 0x00000000
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr =
0x00000000
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =
<NULL>
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName =
<NULL>
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
used
03/14/07 13:25:46, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not
used
03/14/07 13:25:57, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not
used
03/14/07 13:25:57, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0001.mdmp
03/14/07 13:25:57, ACTION, w3wp.exe, Watson Invoke: No

The decision to put "Select All" for multi-valued parameters in SSRS was a
good one. The decision to make it universal and non-configurable was bad.
In many cases, we have implemented an All parameter which is coupled with a
proc that optimizes the query when the user wants all members.

Microsoft really dropped the ball hard on this one. They are not allowing
the report developer/administrator to decide in which cases sending all
parameter values is going to hurt performance and which will be OK.

The excuse that they don't want to change the RDL in service packs is lame.
If that is such an issue, then let it be something you can configure at the
server or folder level, or even allow it to be passed in as a parameter in
the url.