We took network traces, reviewed the IIS logs, a few dumps, reviewed the SSRS logs too and the cause of the 404 eluded us.  The break through came when I noticed that the format of the 404 page matched that of IIS which showed that the error was coming from IIS rather than the Report Viewer control or SSRS itself.  From there we enabled the developer tools within IE (hit F12) and performed a network trace for the browser session alone while reproducing the issue.

After no small amount of trial and error we discovered that the issue related to the size of the query that was being passed to IIS, this was after a few hours which involved copying and renaming the reports to have differing lengths of path and filename.  The length of the query was below that which SSRS can handle (260 characters) and the error being thrown by IIS led us to look at filters in IIS.  My customer then dug into their IIS configuration further and discovered that though there were no filters enabled there was a maximum query length set of 256 characters.  After increasing this to 2048 the issue was resolved.

To check this setting, open IIS Manager and navigate to the "features view" for the site you are hosting the Report Viewer control in then double click on "Request Filtering".  Click on the "Rules" tab and then "Edit Feature Settings" and you should find the "Maximum Query String" setting there.  Increase the number and you should see this issue resolved.

Jason

So, from now on for .NET Data Access and SQL Server related posts stick to here;
https://blogs.msdn.com/b/jneave

For my personal projects on topics including .NET Gadgeteer, Netduino, home brewing, 3d printing, electronics, home theatre and random stuff head here;
www.jedibowler.com

Regards,
Jason

1. "Report server is not responding" error in the browser when connecting to the Report Manager website.
2. The following message in an ASP.NET entry in the application event log on the server:

     Exception information:
        Exception type: MissingMethodException
        Exception message: Method not found: 'Void Microsoft.ReportingServices.Diagnostics.UserUtil.CleanCurrentUserName()'.

It this case the cause was a mismatch in the ReportingServicesWebServer.dll assembly version, for some reason the assembly hadn't been updated when the service pack was applied and the assembly was an older version than ReportingServicesService.exe.  Looking through our internal KB it seems that the recommendation was to destroy the installation of SQL Server as a whole and reinstall, in a few cases that didn't solve it either.  Becuase it seems that the only option provided was a reinstall I felt a risky manouver was worth trying and it turned out to be a success. 

Backup then delete the offending assembly then apply the latest cumulative update, a reboot may be required. 

The assembly is replaced as a result of the CU update and all the assemblies are brought up to the same version, it should be as easy as that and certainly a lot quicker than a resinstallation!

Please note, this may still not resolve your issue but if it does it will save you many hours of reinstallation.  Please ensure you perform full backups of your databases on the off chance it makes things worse and bare in mind that the logic inside the CU updater itself may change in the future.  That said, if it does work feel free to drop me a comment as confirmation. :)

Regards,
Jason

Symptoms

An SSIS package fails with the following error;

Executing the query "Some_Query" failed with the following error: "A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)".

Cause

If priority boost is enabled for an instance on the server in question then while under stress it is possible for the OS to be denied access to required resources that can cause the above behaviour to occur and the likelihood of this behaviour occurring increases when multiple instances are on the same machine with the option enabled.

You can ascertain the state of priority boost by running the following command;

EXEC sp_configure 'priority boost'

GO

As priority boost is an advanced command, you may need to enable them first otherwise you will see the following error;

Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51

The configuration option 'priority boost' does not exist, or it may be an advanced option.

To enable them, run the following script;

EXEC sp_configure 'show advanced options', 1

RECONFIGURE WITH OVERRIDE

GO

The following shows the “EXEC sp_configure ‘priority boost’” results from a server that has priority boost disabled however the service has not been restarted so is still active at runtime.

name                                minimum     maximum     config_value run_value

----------------------------------- ----------- ----------- ------------ -----------

priority boost                      0           1           0            1

Resolution

For each instance on the server, run the following;

EXEC sp_configure 'priority boost', 0

RECONFIGURE WITH OVERRIDE

GO

More Information

Priority boost:
https://msdn.microsoft.com/en-in/library/ms180943(v=SQL.105).aspx

Sp_configure:
https://msdn.microsoft.com/en-in/library/ms188787(v=SQL.105).aspx

https://msdn.microsoft.com/en-us/library/ms157403.aspx

For issues with SSRS in native mode enabling HTTP logging is very useful and creates log files in the same format as IIS, mostly because SSRS2005 is hosted in IIS and SSRS2008 onwards hosts ASP.Net itself so under the hood it is likely the same logging code as IIS iteself.  This has proven very useful for myself so thought I'd share with my readers, whoever you are. :)

Jason

I'd reccomend everyone seeing this issue run the script rather than checking the 32 on 64 setting in the GUI, for some reason the script succeeded where the GUI failed.

https://msdn.microsoft.com/en-us/library/bb677367(SQL.90).aspx

Hope this helps,
Jason

Regards,
Jason

https://ranversvsvmfactory.codeplex.com/wikipage

The Factory is a set of scripts and guidance that allows for the creation of an ISO image that allows for the automated creation of a VS of even TFS virtual machine to be created with the minimum of fuss.  There is also a TFS Virtualisation Guidance document which tells you everything you need to know in order to virtualise your instance and what issues you may see with performance.

I was the lead for the TFS aspect of the document and the work my team and the rest of the guys involved is nothing short of phenomenal.  I hope you all can benefit from our hard work.

Enjoy!

Jason

For those who may have noticed a decrease in the number of non-TFS related posts on here you may be interested in heading over to my personal blog.  I've decided to separate professional and personal projects so most of my Home Server and Media Centre posts now go up over there.

https://jedibowler.spaces.live.com

It's a shameless plug I know. ;)

Regards,
Jason

 After many attempts to install TFS 2008 on WHS I ended up giving up on the whole idea.  Reporting Services and WSS kept throwing up roadblocks periodically and seemed to make it more hassle that it’s worth.  From the first rumbling I heard internal regarding TFS 2010 and new configuration options however I had hope that things would be considerably easier.  Enter TFS Basics.

TFS 2010 can now be configured with or without SharePoint and Reporting Services, it can also now be installed against SQL Express.  In fact, if you install TFS 2010 and follow the steps to install as TFS Basic SQL Express will be installed and configured automatically! 

Installation on Home Server is a breeze, get the bits from MSDN and install from the Tfs-x86 folder.  Once installation completes the configuration wizard should open, click on “TFS Basic” in the left hand menu and click next a few times.  Installation is that simple!  The rest of this post will cover how to configure your instance of TFS to use your homeserver.com certificate and enable you to connect via the internet.

Without further adieu…

1. Open a remote connection to your Home Server using Remote Desktop.
2. Download and install TFS 2010 Beta2 (easy)
3. Install TFC 2010 Beta2 somewhere and test local connectivity
4. Follow these steps to export the Home Server certificate, you will be looking for one that matches your *.homeserver.com (or similar) URL.
   https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/2cfeeba2-511f-47e8-913c-f196b74e6a44.mspx?mfr=true
5. Open inetmgr and find the "Team Foundation Server" website then right click and open the properties dialog. In the Directory Security tab click on "Server Certificate" and the certificate wizard should show itself. Click on Next.
   
6. We will want to import the certificate so click on the radio button then click next.

   

7. Navigate to the location of the PFX file from the previous step and click next.

   

8. Click next and enter the name of the password you entered for the PFX file.
9. Enter the port you wish to use for SSL, 8181 for example.

   

10. Review the details and click next.
    
11. Click on the Web Site tab and if not present, enter the port specified for SSL in the SSL Port text box.
12. Done.

That should be it, you will need to follow the steps to forward the ports on your router such that a public port on your router passes through to the SSL port on your Home Server and then you will be able to connect locally and remotely.  Please be aware that some routers will route their external address to their control panel.  If you see issues connecting to TFS using the public name then try to connect to your WHS Remote Access page and ensure it connects to your Home Server rather than the router.

Hopefully your router will play ball and you will be up and running, otherwise likely a bit of Binging will get you the help you need.  Enjoy and feel free to add comments if you have any questions.

Jason