Debugging Report Manager

Hi,
I have created a custom data processing extension that retrieves a Data
Table object from my DAL. It all works fine in the report designer, I can
preview the report and data is returned etc However when I deploy the report
and then try to access via the report manager web interface I get an error
has occurred during report processing... I can't for the life of me see what
is could be causing the error and I don't know how to debug this
Can anyone provide any useful tips/tricks?
ThanksMy bet is that dotnet security is tripping you up. When in development you
are the admin of the box and have all the rights you need to do anything.
The context of your assembly in production is different and you need to
setup the rights for the assembly. That is my guess anyway.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Neil" <Neil@.discussions.microsoft.com> wrote in message
news:B8854717-92A7-4ED1-8FDC-0D8462A594AB@.microsoft.com...
> Hi,
> I have created a custom data processing extension that retrieves a Data
> Table object from my DAL. It all works fine in the report designer, I can
> preview the report and data is returned etc However when I deploy the
> report
> and then try to access via the report manager web interface I get an error
> has occurred during report processing... I can't for the life of me see
> what
> is could be causing the error and I don't know how to debug this
> Can anyone provide any useful tips/tricks?
> Thanks
>

Debugging Custom Report Data Processing extension

Hi,

I've created our own custom report data processing extension and it works successfully. I also know how to debug the extension while in the Report Designer environment (in Visual Studio).

However, is it possible to debug the extension in the run-time mode. That is, when I run Report Manager to view the report that usees this extension.

Thank you very much

Yes, you should be able to attach a remote debugger to the IIS worker process, just like an ASP.NET application.|||Please help! I still don't know how to debug during run-time ... FYI, I'm using Windows 2003 Server. I can't seem to find the ASP.NET worker process ... am I missing anything?

I have no problems previewing the report data in report designer. However, when I try to run the report in report manager, I get this error:

"An error has occurred during report processing."

What could possibly be wrong? Any thoughts?

Thank you!!|||On Windows 2003, attach the debugger to w3wp.exe

-- Robert

Debugging Custom Report Data Processing extension

Hi,

I've created our own custom report data processing extension and it works successfully. I also know how to debug the extension while in the Report Designer environment (in Visual Studio).

However, is it possible to debug the extension in the run-time mode. That is, when I run Report Manager to view the report that usees this extension.

Thank you very much

Yes, you should be able to attach a remote debugger to the IIS worker process, just like an ASP.NET application.|||Please help! I still don't know how to debug during run-time ... FYI, I'm using Windows 2003 Server. I can't seem to find the ASP.NET worker process ... am I missing anything?

I have no problems previewing the report data in report designer. However, when I try to run the report in report manager, I get this error:

"An error has occurred during report processing."

What could possibly be wrong? Any thoughts?

Thank you!!|||On Windows 2003, attach the debugger to w3wp.exe

-- Robert

debugging a Custom Data Processing Extension

How do I go about debugging a Custom Data Processing Extension written in VB
or C#? How do I tell the debugger which process to attach to?
--
-PeterPlease check RS books online:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_extend_dataproc_9plu.asp?frame=true
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"jpstewart" <jpstewart@.discussions.microsoft.com> wrote in message
news:F42133CD-B143-4E63-8461-0E6785EE8F5B@.microsoft.com...
> How do I go about debugging a Custom Data Processing Extension written in
> VB
> or C#? How do I tell the debugger which process to attach to?
> --
> -Peter
>

Debug deployed extension

I have a custom data extension I'm working on. I can debug this when the
report using it is being designed by adding a line in the code for the
extension like:
System.Diagnostics.Debugger.Break();
When I then run the report in design mode I'll get a choice of debuggers and
I can then open one and debug the extension.
However, if I then deploy the report (with
System.Diagnostics.Debugger.Break(); still in the code) and run the report
from say Report Manager or just via URL I don't get the choice to debug and
the report just seems to hang. Right now this is all just on my one
development PC (when I'm deploying I'm actually just deploying it to my
development machines version of reporting services).
Any thoughts on the problem or how to debug a deployed custom extension?
Cheers!Hi Cayman:
You might have to use Debugger.Launch if the debugger is not already
attached (which you can check with the Debugger.IsAttached property).
Is this in a custom assembly? Let me know if this works, I might check
it out later this evening. I imagine there still might be a problem
since the reporting service has it's own desktop / winsation where GUI
elements appear that are invisible to the logged in user. An old
school solution to this problem is to run as Local System and check
"Allow service to interact with desktop", but running as Local System
is risky, and allowing a service to interact with the desktop is even
riskier, because a malicious program could start pumping Windows
messages into the service.
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Thu, 11 Nov 2004 07:00:06 -0800, "Cayman Visitor" <Cayman
Visitor@.discussions.microsoft.com> wrote:
>I have a custom data extension I'm working on. I can debug this when the
>report using it is being designed by adding a line in the code for the
>extension like:
>System.Diagnostics.Debugger.Break();
>When I then run the report in design mode I'll get a choice of debuggers and
>I can then open one and debug the extension.
>However, if I then deploy the report (with
>System.Diagnostics.Debugger.Break(); still in the code) and run the report
>from say Report Manager or just via URL I don't get the choice to debug and
>the report just seems to hang. Right now this is all just on my one
>development PC (when I'm deploying I'm actually just deploying it to my
>development machines version of reporting services).
>Any thoughts on the problem or how to debug a deployed custom extension?
>Cheers!