Alerts and Jobs for transaction log processing

Scenario: I have an alert defined which monitors the transaction log. It should start a job which should backup the transaction log once the log is 75 percent full.

So far so good.

The challenge is to give the database name to the command for backing up (in our case it is a external tool) the appropriate transaction log

I know, that you can use tokens (A-DBN) to do this.

I know, that there is a bug in this area, so tokens are not set correctly in SP1

Question:

Is there any trick/alternative to create a workaround?

Regards

Norbert

If you created a WMI Event alert you may be able to read the Database name as part of the event $(WMI(DatabaseName))

Aggregation Processing Use of All Processors Issue

In 2000 when MSAS wanted to create aggs it did a great job without me doing anything of using all available processors pretty darn near or at 100%. In SSAS 2005 I have an 8-processor box (4 dual cores actually) and its only using 1 of the 8. Anyone know how to unlock that? Some property perhaps?

If you split the cube into several partions by using dates, AS2005 will use more than one processor.

Regards

/Thomas

|||

Based on 8 processors I used 8 partitions and it did better, but not much. Then I tried 16 partitions (many programs use 4X threads per processor to maximize parellelization, but if something is well written 1x should be sufficient) and I think it helped - utilization is up to 30 or 40 percent during the cube process part, but the aggregation part is still pretty low - 20-30% overall.

How many procs do you have and what utilization are you seeing during agg processing?

|||

The cubes I work with are small and they run on a four CPU box. By using partitions I was able to reduce the the processing time by 50 percent for one of the cubes.

I have not measured utilization, only processing time.

You will have to consider your I/O system as well and memory setting for SSAS2005. Maybe your low utilization depends on bottlenecks in memory or I/O?

Regards

Thomas

after upgrading to sept ctp 2005 reports with subreports fail

I just installed September 2005 CTP and all reports with subreports
getting an error:
Error occured during local report processing. An internal error occured
on the report server.
If i delete subreports everything is fine. The error log says
following:
09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x47405858
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0001.mdmp
09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3444
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x11A21E9C
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0002.mdmp
09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
AdjustTokenPrivileges () failed (00000514)
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
4 supplied
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2732
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
= 0x0
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x10B35858
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
ExceptionRecordPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
= <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
not used
09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\SQLDmpr0003.mdmp
09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
Any ideas?
Everything was fine in June CTP versionDid you upgrade the June CTP or did you remove everything (including the
dotnet 2.0 framework beta) first?
This CTP does not upgrade, you have to remove everything first and then
install.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126801637.855296.186610@.g49g2000cwa.googlegroups.com...
>I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||removed everything twice and reinstalled|||I just created one (report/subreport). I suggest trying recreating the
report from scratch (or at least the subreport and then re-embed it).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126803423.272541.149830@.g47g2000cwa.googlegroups.com...
> removed everything twice and reinstalled
>|||that what i did also. did not help.
here is another hint:
if i put this subreport under the group footer (or header) that i want,
report fails.
If i move subreport to different group header it works.|||If you email me the rdl and rdl.data files for both report and subreport I
will see about getting it to the correct person at MS. Just remove NOSPAM
from my email address.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126807105.990018.151820@.z14g2000cwz.googlegroups.com...
> that what i did also. did not help.
> here is another hint:
> if i put this subreport under the group footer (or header) that i want,
> report fails.
> If i move subreport to different group header it works.
>|||before I'll do this try to reproduce it this way:
create report with 4 groups:
Group1
Group2
Group3
Group4
create subreport
put subreport under group 4 (or 3, header, footer, detail - does not
matter)
report will not run (at least for me)
if you put it inder group 1 or 2, report will work in Sept CTP 2005
package|||Great repro. I will pass it on to MS.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126879282.885405.84350@.g47g2000cwa.googlegroups.com...
> before I'll do this try to reproduce it this way:
> create report with 4 groups:
> Group1
> Group2
> Group3
> Group4
> create subreport
> put subreport under group 4 (or 3, header, footer, detail - does not
> matter)
> report will not run (at least for me)
> if you put it inder group 1 or 2, report will work in Sept CTP 2005
> package
>|||now, i think i know what really happened:
I have 4 groups
Group1
Group2
Group3
Group4
if one of the values for Group4 ( in my case Group3 also) will be null,
subreport that you will put under this group will make main report to
fail. And it happens only in Sept CTP 2005 package|||Great, I'll make sure someone gets this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<bosstan1@.gmail.com> wrote in message
news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> now, i think i know what really happened:
> I have 4 groups
> Group1
> Group2
> Group3
> Group4
> if one of the values for Group4 ( in my case Group3 also) will be null,
> subreport that you will put under this group will make main report to
> fail. And it happens only in Sept CTP 2005 package
>|||hi, i have hit this same problem as well. has a fix or workaround been
identified yet?
thanks,
steve
"bosstan1@.gmail.com" wrote:
> I just installed September 2005 CTP and all reports with subreports
> getting an error:
> Error occured during local report processing. An internal error occured
> on the report server.
> If i delete subreports everything is fine. The error log says
> following:
> 09/15/05 07:55:10, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x47405858
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 07:55:10, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 07:55:15, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0001.mdmp
> 09/15/05 07:55:15, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:15:42, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 3444
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x11A21E9C
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:15:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:15:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0002.mdmp
> 09/15/05 08:15:45, ACTION, aspnet_wp.exe, Watson Invoke: No
> 09/15/05 08:23:14, ERROR , SQLDUMPER_UNKNOWN_APP.EXE,
> AdjustTokenPrivileges () failed (00000514)
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters:
> 4 supplied
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID => 2732
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags
> = 0x0
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x10B35858
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,
> ExceptionRecordPtr = 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName
> = <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName => <NULL>
> 09/15/05 08:23:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7
> not used
> 09/15/05 08:23:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump
> completed: D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\SQLDmpr0003.mdmp
> 09/15/05 08:23:16, ACTION, aspnet_wp.exe, Watson Invoke: No
> Any ideas?
> Everything was fine in June CTP version
>|||Has anyone found a solution to this? I am running into the same issues.
"Bruce L-C [MVP]" wrote:
> Great, I'll make sure someone gets this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <bosstan1@.gmail.com> wrote in message
> news:1126887557.215825.300160@.f14g2000cwb.googlegroups.com...
> > now, i think i know what really happened:
> > I have 4 groups
> > Group1
> > Group2
> > Group3
> > Group4
> >
> > if one of the values for Group4 ( in my case Group3 also) will be null,
> > subreport that you will put under this group will make main report to
> > fail. And it happens only in Sept CTP 2005 package
> >
>
>