Elegant Code » debugging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Calls to ReportExecutionService.Render() Hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/?utm_source=rss&utm_medium=rss&utm_campaign=calls-to-reportexecutionservice-render-hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/#comments Mon, 25 Jan 2010 23:27:44 +0000 Tony Rasa http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/ Given: One Windows Service, written in C#, using SQL Reporting Services via the SSRS web services.  MyApp.Service waits for work requests to come in, and when it finds them it uses SSRS to generate some PDFs (among a bunch of other stuff).  The Windows Service code is in one project, “myapp.service,” and the code that does all the work is in a shared project, “myapp.core.”. 

Problem: The raw bytes of the PDF are returned from SSRS by using the class Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService, via the Render() method.  This code works just fine in Dev, Test, and Stage environments – but in Production, without fail, this Render() method hangs and will never return back to the service process.

The Fix:  This functionality is a small bit in a much larger application, and even the PDF generation is a smallish piece of some larger responsibilities for the service.  So first, I want to isolate the behavior, and then duplicate it. 

I wrote a test windows service consisting of one project, that does one thing: when a timer fires, a hardcoded request to the production Reporting Services is made to get a PDF bytestream.  This service does what is expected in Dev and Stage, but when I tried to install it on Production:

An exception occurred while trying to find the installers in the C:\webreader\webreader.svc.exe assembly.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Aborting installation for C:\webreader\webreader.svc.exe.

Can’t load a type?!  So I copy Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll into the program directory, and my test service installs and works perfectly.  Copying the same files into the production service’s directory also fixes the problem.

 

So, if your Reporting Services ASMX calls are hanging, try changing your references over to “Copy Local” and see what happens…

 

Why this is weird: If those DLLs were missing or corrupt, then why did the original App code load and run (and hang)?  I thought perhaps the wrong version was referenced in the GAC, but no there were NO Microsoft.ReportViewer.*.dll’s registered.  The service installer caught the missing types when the references were all in one assembly, but didn’t have any problems when the references were spread into a 2nd assembly. 

Just when I think “hey, maybe I’m getting a hang of this .NET stuff” a problem like this happens…

]]> http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/feed/ 3 Debugging XAML http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Elegant Code » debugging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Calls to ReportExecutionService.Render() Hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/?utm_source=rss&utm_medium=rss&utm_campaign=calls-to-reportexecutionservice-render-hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/#comments Mon, 25 Jan 2010 23:27:44 +0000 Tony Rasa http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/ Given: One Windows Service, written in C#, using SQL Reporting Services via the SSRS web services.  MyApp.Service waits for work requests to come in, and when it finds them it uses SSRS to generate some PDFs (among a bunch of other stuff).  The Windows Service code is in one project, “myapp.service,” and the code that does all the work is in a shared project, “myapp.core.”. 

Problem: The raw bytes of the PDF are returned from SSRS by using the class Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService, via the Render() method.  This code works just fine in Dev, Test, and Stage environments – but in Production, without fail, this Render() method hangs and will never return back to the service process.

The Fix:  This functionality is a small bit in a much larger application, and even the PDF generation is a smallish piece of some larger responsibilities for the service.  So first, I want to isolate the behavior, and then duplicate it. 

I wrote a test windows service consisting of one project, that does one thing: when a timer fires, a hardcoded request to the production Reporting Services is made to get a PDF bytestream.  This service does what is expected in Dev and Stage, but when I tried to install it on Production:

An exception occurred while trying to find the installers in the C:\webreader\webreader.svc.exe assembly.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Aborting installation for C:\webreader\webreader.svc.exe.

Can’t load a type?!  So I copy Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll into the program directory, and my test service installs and works perfectly.  Copying the same files into the production service’s directory also fixes the problem.

 

So, if your Reporting Services ASMX calls are hanging, try changing your references over to “Copy Local” and see what happens…

 

Why this is weird: If those DLLs were missing or corrupt, then why did the original App code load and run (and hang)?  I thought perhaps the wrong version was referenced in the GAC, but no there were NO Microsoft.ReportViewer.*.dll’s registered.  The service installer caught the missing types when the references were all in one assembly, but didn’t have any problems when the references were spread into a 2nd assembly. 

Just when I think “hey, maybe I’m getting a hang of this .NET stuff” a problem like this happens…

]]> http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/feed/ 3 Debugging XAML http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/?utm_source=rss&utm_medium=rss&utm_campaign=calls-to-reportexecutionservice-render-hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/#comments Mon, 25 Jan 2010 23:27:44 +0000 Tony Rasa http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/ Given: One Windows Service, written in C#, using SQL Reporting Services via the SSRS web services.  MyApp.Service waits for work requests to come in, and when it finds them it uses SSRS to generate some PDFs (among a bunch of other stuff).  The Windows Service code is in one project, “myapp.service,” and the code that does all the work is in a shared project, “myapp.core.”. 

Problem: The raw bytes of the PDF are returned from SSRS by using the class Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService, via the Render() method.  This code works just fine in Dev, Test, and Stage environments – but in Production, without fail, this Render() method hangs and will never return back to the service process.

The Fix:  This functionality is a small bit in a much larger application, and even the PDF generation is a smallish piece of some larger responsibilities for the service.  So first, I want to isolate the behavior, and then duplicate it. 

I wrote a test windows service consisting of one project, that does one thing: when a timer fires, a hardcoded request to the production Reporting Services is made to get a PDF bytestream.  This service does what is expected in Dev and Stage, but when I tried to install it on Production:

An exception occurred while trying to find the installers in the C:\webreader\webreader.svc.exe assembly.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Aborting installation for C:\webreader\webreader.svc.exe.

Can’t load a type?!  So I copy Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll into the program directory, and my test service installs and works perfectly.  Copying the same files into the production service’s directory also fixes the problem.

 

So, if your Reporting Services ASMX calls are hanging, try changing your references over to “Copy Local” and see what happens…

 

Why this is weird: If those DLLs were missing or corrupt, then why did the original App code load and run (and hang)?  I thought perhaps the wrong version was referenced in the GAC, but no there were NO Microsoft.ReportViewer.*.dll’s registered.  The service installer caught the missing types when the references were all in one assembly, but didn’t have any problems when the references were spread into a 2nd assembly. 

Just when I think “hey, maybe I’m getting a hang of this .NET stuff” a problem like this happens…

]]> http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/feed/ 3 Elegant Code » debugging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Calls to ReportExecutionService.Render() Hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/?utm_source=rss&utm_medium=rss&utm_campaign=calls-to-reportexecutionservice-render-hang http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/#comments Mon, 25 Jan 2010 23:27:44 +0000 Tony Rasa http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/ Given: One Windows Service, written in C#, using SQL Reporting Services via the SSRS web services.  MyApp.Service waits for work requests to come in, and when it finds them it uses SSRS to generate some PDFs (among a bunch of other stuff).  The Windows Service code is in one project, “myapp.service,” and the code that does all the work is in a shared project, “myapp.core.”. 

Problem: The raw bytes of the PDF are returned from SSRS by using the class Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService, via the Render() method.  This code works just fine in Dev, Test, and Stage environments – but in Production, without fail, this Render() method hangs and will never return back to the service process.

The Fix:  This functionality is a small bit in a much larger application, and even the PDF generation is a smallish piece of some larger responsibilities for the service.  So first, I want to isolate the behavior, and then duplicate it. 

I wrote a test windows service consisting of one project, that does one thing: when a timer fires, a hardcoded request to the production Reporting Services is made to get a PDF bytestream.  This service does what is expected in Dev and Stage, but when I tried to install it on Production:

An exception occurred while trying to find the installers in the C:\webreader\webreader.svc.exe assembly.
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Aborting installation for C:\webreader\webreader.svc.exe.

Can’t load a type?!  So I copy Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll into the program directory, and my test service installs and works perfectly.  Copying the same files into the production service’s directory also fixes the problem.

 

So, if your Reporting Services ASMX calls are hanging, try changing your references over to “Copy Local” and see what happens…

 

Why this is weird: If those DLLs were missing or corrupt, then why did the original App code load and run (and hang)?  I thought perhaps the wrong version was referenced in the GAC, but no there were NO Microsoft.ReportViewer.*.dll’s registered.  The service installer caught the missing types when the references were all in one assembly, but didn’t have any problems when the references were spread into a 2nd assembly. 

Just when I think “hey, maybe I’m getting a hang of this .NET stuff” a problem like this happens…

]]> http://elegantcode.com/2010/01/25/calls-to-reportexecutionservice-render-hang/feed/ 3 Debugging XAML http://elegantcode.com/2009/04/14/debugging-xaml/?utm_source=rss&utm_medium=rss&utm_campaign=debugging-xaml http://elegantcode.com/2009/04/14/debugging-xaml/#comments Wed, 15 Apr 2009 01:43:01 +0000 Brian Lagunas http://elegantcode.com/2009/04/14/debugging-xaml/ Okay, so I have been asked this question more than almost any XAML related question in the past few weeks; How do I debug XAML?  The problem with XAML’s powerful binding model is that it can be difficult to debug errors in your binding paths.

Lets say I have the following code snippet:

<StatusBar>
   <StatusBarItem>
       <TextBlock Text="{Binding Messssage}" />
   </StatusBarItem>
</StatusBar>

As you can see my property Message is totally misspelled.  If I were to run this application nothing would ever appear in my status bar, and I would not know why.  I didn’t get any compile errors, and my view renders perfectly in my designer, so what the hell is going on.  You might spend hours looking at your object’s property, stepping through the property changed events, or just saying XAML is a piece of crap and I give up.  Well never fear, I am about to reveal the secret to debugging your XAML.

Look in your Output Window!

OutputWindow

Yes, the nearly always forgotten Output Window.  As you can see, if you click on the image above, it tells me that I have a binding expression path error and gives the line number where the error occurred.  So don’t spend hours stepping through code looking for a ghost.  Just check your Output Window.

]]> http://elegantcode.com/2009/04/14/debugging-xaml/feed/ 1