.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
MarieAdela
Imran Ghani
Post New Web Links

System.out of memory exception in sql server 2005 repoting services

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :
 

hi,

this is ram,

I am new to the reporting services,just one month back i joined in the company.there i got trained in ssrs 2005 .

nd my pblm is i inserted one of the csv file into the sql server 2005,it contains 102866 records,nd then i started generating summarized record through sql server 2005 reporting services.when i started generating the reports with few columns i didnt get any pblm,but when i started including more columns with aggregate functions i am getting the ecxeption called system out of memory exception.and by google search i found some solutions like enabling the AWE,but still i am getting the same exception

my server configuration is

64 bit windows server 2003,

4GB RAM

SQL SERVER 2005 STANDARD EDITION

PLEASE HELP ME OUT IN RESOLVING THIS ISSUE,I WILL BE VERY THANKFUL TO YOU,

THANKS IN ADVANCE.

 






View Complete Post


More Related Resource Links

SQL Server 2005 Try and Catch Exception Handling

  
I'm pretty excited to see that there is some real error handling for T-SQL code in SQL Server 2005. It's pretty painful to have your wonderfully architected .NET solution tainted by less-than-VBScript error handling for stored procedures in the database. The big difference being the addition of TRY..CATCH blocks. Let's take a look:

SQL Server 2005: Jazz Up Your Data Using Custom Report Items In SQL Server Reporting Services

  

Custom report items in SQL Server 2005 Reporting Services address your needs for custom reports without the pain of doing it from scratch.

Teo Lachev

MSDN Magazine October 2006


Data Points: Report Controls in SQL Server 2005 Reporting Services

  

Reporting has always been one of the dark arts of development. The tools typically seem to do just enough to get you to a certain point, then leave you to find workarounds to solve more complex issues.

John Papa

MSDN Magazine July 2006


Data Points: Designing Reports with SQL Server Reporting Services 2005

  

Many applications require some degree of integration with a reporting tool. A good solution, SQL ServerT Reporting Services 2005, provides Web-based reports and can be integrated into both Windows® Forms and Web-based applications.

John Papa

MSDN Magazine June 2006


Data Points: SQL Server 2005 XML Support, Exception Handling, and More

  

SQL Server 2005 includes several important improvements to the Transact-SQL (T-SQL) language. One added feature is a new kind of trigger that fires when data definition language (DDL) statements run.

John Papa

MSDN Magazine May 2006


SQL Server 2005: Unearth the New Data Mining Features of Analysis Services 2005

  

In SQL Server 2005 Analysis Services you'll find new algorithms, enhancements to existing algorithms, and more than a dozen added visualizations to help you get a handle on your data relationships. Plus, enhancements to the Data Mining Extensions to SQL along with OLAP, DTS, and Reporting Services integration make it possible to create a new breed of intelligent apps with embedded data mining technology. Here the author explains it all.

Jamie MacLennan

MSDN Magazine September 2004


Problem when installing Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint

  
Hi,

I have configured the SharePoint Production Server(Standalone) with WS 2008 64 bit version, SQL Server 2005 with SP3 , Visual Studio 2008 and MOSS 2007(SP3). I have configured SSRS 2005 in SharePoint integration mode. Everything works fine till the last step. Now, i am trying to install Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies feature and failed. I am getting below error message.

Product: Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies -- You must first install SharePoint Server before installing SQL Server 2005 Reporting Services Add-in for SharePoint Technologies



Any help will be very appreciated!

Thanks,
-Raj

'System.OutOfMemoryException' SQL Server 2005

  
Looking for a solution to SQL Server 2005 'System.OutOfMemoryException' error, or at least the root cause of this error.   Following please find:1) Description of problem2) Exact error message3) Query that fails (against large 'SourceTable', but works against smaller subsets of 'SourceTable' )4) Query that works (above, split apart) on any size table5) Machine and SQL configuration and versions DESCRIPTION OF PROBLEM-------------------------------------------------------I am getting a 'System.OutOfMemoryException' error running a simple query on a large table in SQL SERVER 2005. If I run with a fresh boot, only me on the server, and only SQL Server Management Studio open with 1 query window, I'll get this error when I run it against my full-sized SourceTable.  Task Manager indicates there is still more than 7 Gig of physical memory available! (see system configuration at end of this note).   The query runs to competion if I run it against a smaller 'SourceTable'.    If I break out the matchup to the derived table from the query into a separate step, the query will run until completion against any size table I throw at it.   I've searched the web, and found that people are getting this error with SQL Server 2005, but not with SQL Server 2000.  It looks like people are encountering it in various queries that should work, and in other circumstances such as when runn

SQL Server 2005: Install reporting services - which version?

  
Hello - I installed SQL Server 2005 as part of an SBS2008 install. I need to install reporting services, but now I'm having trouble identifying which version (X64 or X86) I'm running. Is there an easy way of figuring out which installation disk I need to insert for SQL Server 2005? Thanks, Nick.

Kerberos issue with SQL Reporting Services 2005 on Server 2003 R2

  
Hi Guys,apologies if this is the incorrect forum, so moderators, feel free to move it to SQL/IIS/SharePoint as appropriate... [Windows Server Security moderator pushed me this direction]I have a test environment that I'm trying to get SQL Reporting Services 2005 SP3 working in integrated mode with SharePoint 2007 SP2.The environment is all in VMWare, running Server 2003 R2 x86 and is layed out like this:SERVER A:AD/DNS/DHCPSERVER B:SQL 2005 SP3 CU8SERVER C:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82SERVER D:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82Through the use of DNS and (SharePoint) Alternate Access Names, SERVER D is used to deliver the Main Content in SharePoint and the Reporting Service website.  SERVER C is used to deliver the Central Admin, SSP and MySite.I've set up SPN's for the SharePoint App Pools, using the following: [main content] setspn -S HTTP/SERVERA DOMAIN\AppPoolUserA setspn -S HTTP/SERVERA.FQDN DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB.FQDN DOMAIN\AppPoolUserA [repor

I am getting System.Web.Services.Protocols.SoapHeaderException: Server unavailable error?..

  
 Hi,    I am using WSE 3.0 for my applicaton. when run from the client end I am getting following error.System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.ApplicationException: WSE841: An error occured processing an outgoing fault response. ---> System.Web.Services.Protocols.SoapHeaderException: Microsoft.Web.Services3.Security.SecurityFault: Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.  at Microsoft.Web.Services3.Design.RequireSoapHeaderAssertion.RequireSoapHeaderFilter.ProcessMessage(SoapEnvelope envelope)  at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)  at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope requestEnvelope)  at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage message)  at System.Web.Services.Protocols.SoapServerProtocol.Initialize()  at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)  --- End of inner exception stack trace ---  --- End of inner exception stack trace ---         Help needed on this. re

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Object canno

  
hello,i am using a web servicewrtitten in .net and i access the webservice from my wepApplication i get this error System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Object cannot be cast from DBNull to other types.my code is access webservice: protected void btnSave_Click(object sender, EventArgs e)        {            int intStatusCode;            dtProjectStatus = (DataTable)ViewState["dtProjectStatus"];            try            {                objService.Credentials = System.Net.CredentialCache.DefaultCredentials;                if(dtProjectStatus.Rows.Count>0)                {                  intStatusCode = objService.InsertTest(dtProjectStatus);                }   

SharePoint integration with SQL Server 2005 Reporting Services

  
Hello Everyone,   I have been banging my head against the wall with trying to integrate SharePoint 2007 and SQL Reporting Services.  If anyone could offer any assistance, I would appreciate it greatly. I have been following these 2 websites down to the letter in trying to configure everything:     1. http://msdn2.microsoft.com/en-us/library/bb326356.aspx     <---Microsoft's Steps   2. http://blogs.msdn.com/sharepoint/archive/2007/02/19/microsoft-sql-server-2005-sp2-reporting-services-integration-with- wss-3-0-and-moss-2007.aspx   <---SharePoint Blog Group     Basically my setup is as follows:   Server 1 = SharePoint 2007 Server 2 = SQL Server Reporting Services SP2 / SharePoint 2007 services Server 3 = Database   Server1 is setup and running SharePoint 2007 fine with no problems. It was installed under the complete option with its own server farm. Then with the Server2, SharePoint 2007 is installed again, also under the complete complete option, and configured to join Server1's server farm. In this way, Server2 is able to supply Server1 with services and it has been said that if you are using 2 different servers, one for SharePoint and one for Reporting Services, you need to have an instance of SharePoint on the reporting services box. With a SharePoint "front-end" the reporting-services now has a way to also join Server1s farm.   This is where the headache be

SQL Server Reporting Services 2008 R2 - The configuration system has already been initialized

  
After correcting issues related to .NET 4.0, I am now encountering the error below. It occurs when I attempt to access one of the two web sites. I've been tracking my install/config progress here: http://serverfault.com/questions/178353/what-would-cause-a-500-internal-server-error-when-accessing-the-report-manager-ur   Error Log: appdomainmanager!DefaultDomain!ae8!09/07/2010-14:47:12:: i INFO: Appdomain:13 ReportServer_11-11-129283588326974843 started. appdomainmanager!DefaultDomain!ae8!09/07/2010-14:47:12:: e ERROR: AppDomain ReportServer_11 failed to start. Error: The configuration system has already been initialized. library!DefaultDomain!ae8!09/07/2010-14:47:12:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: Failed to create HTTP Runtime, Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_11.  ---> System.InvalidOperationException: The configuration system has already been initialized.    at System.Configuration.ConfigurationManager.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)    at System.Web.Configuration.HttpConfigurationSystem.EnsureInit(IConfigMapPath configMapPath, Boolean listenToFileChange

Purpose of "NT AUTHORITY\SYSTEM" login in SQL Server 2005

  
Hi All Does anybody know what the "NT AUTHORITY\SYSTEM" login create during a SQL Server 2005 instillation is used for? Does this login pose a security risk, and can it be removed safely?  It seems to me as if it is similar to the "Bultin\Administrator" login which we remove from our production servers? Regards Stevo

Run Reporting services 2005 with databases housed on SQL Server 2008?

  
Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade both to 2008 at some point but would like to do the SQL database engine first. So I would be running something like this: Server A: SQL 2005 Reporting Services Server B: SQL 2008 database engine - housing ReportServer and ReportServerTempDB Is this configuration supported? If I do this would I just need to run the DB's in 9.0 compatibility mode until we upgrade the RS server? Would it be better to upgrade the RS box first or both of them at the same time instead of doing the database engine first?

Run Reporting services 2005 with databases housed on SQL Server 2008?

  
Hi, I posted this in the RS forum as well but was thinking it would be better here. I'm not sure if I can move a post to  a different forum or not so sorry for the double post. I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade both to 2008 at some point but would like to do the SQL database engine first. So I would be running something like this: Server A: SQL 2005 Reporting Services Server B: SQL 2008 database engine - housing ReportServer and ReportServerTempDB Is this configuration supported? If I do this would I just need to run the DB's in 9.0 compatibility mode until we upgrade the RS server? Would it be better to upgrade the RS box first or both of them at the same time instead of doing the database engine first?
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend