Report Server File Upload fails-Collection of common programming errors

11 years ago
admin
2 minutes

  • msdn I am using SQL Server Enterprise 2008 with the Latest Service Pack installed, and I have all the latest patches for .NET Framework Service Packs. My machine specs are: Intel Core 2 duo with 4GB of RAM, so you can take for granted that all of the abovementioned programs are 32bit versions (x86). My report Server is also configured in native mode with no SSL options or configurations whatsoever, just the default recommended option to connect, and the credential account used for my ReportServer Database is the common NT AUTHORITY/NETWORK SERVICE account. If it’s of any relevance, my Report Server Service runs under the Network Service built-in account too. No execution accounts selected.  I am trying to create a report model with BIDS from a local database (adventure works). It seems that, although my report server’s upload limit is the default one (4.096KB) or so it should, as I have made no changes on that, my report server FAILS to upload files greater than 10KB. Using Visual Studio to upload an .rdl report greater than 10KB, it takes about 2 to 3 mins before reporting “process timeout”. Using Visual Studio to upload a report model project, .smdl file that is, Visual Studio takes 2 to 3 mins before reporting “the underline connection has been closed: an error occured on a recieve”. Using my browser to upload *any* kind of file greater than 10KB, it takes 2 mins for the progress bar to fill up, then after that, it asks for my credentials, I supply them, again waiting, credentials etc etc. Uploading files less than 10KB get uploaded just fine.

  • msdn1

  • msdn2

    PROBLEM SOLVED.

    I formatted the forementioned PC and reinstalled Windows XP, SPs, SQL Server, SPs, Visual Studio, SPs in that order. The only thing missing from the new configuration is IIS Services and IIS manager but I don’t know if this has anything to do with the problem described.


  • msdn3

    Good..

    Yes. SSRS 2008 no longer required IIS, which will use the HTTP.SYS instead and hence the reason.