SharePoint University

Hi Folks

 Has anyone seen the following error in SharePoint. I have 0.5 GB left on our SQL Server 2005. Can anyone assist. I don't want to have to reboot the database server.

Go back to site 
Error 
 
   
"Server Out Of Memory

There is no memory on the server to run your program. Please contact your administrator with this problem.
Troubleshoot issues with Windows SharePoint Services."

 Regards

 David Thomson

Were you able to resolve this issue, and if so, could you kindly post the resolution?  I'm running into the same error message, but have adequate disk space and physical and virtual memory for the operation to perform, so I'm curious as to what you may have found.

 Thanks,

Share~a~Pint

Are you running your SQL Server and Sharepoint on the same box?  Can you tell us a little about your environment, like what's running on each server, RAM, speed, CPUs, etc.  It could be a lot of things but without knowing more about your setup it's about impossible to give any advice!

 Linda
 

The environment is setup as follows:

1 SQL 2005 instance on a Windows 2003 R2 SP2 server. 6GB RAM, 3.7Ghz x 4, Dual Core. Plenty of free disk space (20GB to 200GB available on each drive)

1 MOSS Web front-end, Windows 2003 R2 SP2, 6GB RAM, 3.7Ghz x 4, Dual Core.

          --Web front-end is running WSS Help Search, WSS Incoming Email and WSS Web Application 

1 MOSS Application server, Windows 2003 R2 SP2, 6GB RAM, 3.7Ghz x 4, Dual Core.

         --Application server is running the following: CA, Document Conversion Launcher, Excel Calculation Services, Office SharePoint Server Search, WSS Incoming Email, WSS Search.

I am seeing an occassional error on the web front end, however from what I can see all of the databases are accessible by SharePoint while this error is being reported, and the sites are still being served:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3760
Date:  1/30/2008
Time:  2:11:15 AM
User:  N/A
Computer: <webfrontend>
Description:
SQL Database 'SharePoint_Config2' on SQL Server instance 'SQLNode\SQLInstance,7001' not found. Additional error information from SQL Server is included below.

Cannot open database "SharePoint_Config2" requested by the login. The login failed.
Login failed for user 'ADMIN\webfrontend$'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

In researching the above error, I've encountered some SPWRITER.EXE "high" priority errors in the log files. Here is an example of one:

01/29/2008 16:40:45.87  SPWRITER.EXE (0x08F0)                    0x0D04 Windows SharePoint Services    Database                       880i High     System.Data.SqlClient.SqlException: Cannot open database "SharePoint_Config2" requested by the login. The login failed.  Login failed for user 'ADMIN\webfrontend$'.     at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)     at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)     at System.Data.SqlClient.SqlConnection.Open()     at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection() 

 Any help or suggestions that you could provide would be appreciated.

Thanks!

 I'm going to assume that you've already checked to make sure that the ADMIN\webfrontend$ account is not locked out, and that it has correct privileges on the SQL box for your SharePoint_Config2, and that a SharePoint_Config2 database actually does exist. 

I see something similar when my network drops connections which unfortunately happens several times a day.  I have no control over the network.  

If you've checked all rights and made sure no lock outs and your not experiencing any down time from it then you may be having dropped packets too.

Linda 

The admin\webfrontend$ account is the local machine account, I believe, and is not locked out.  The SharePoint_Config2 does exist and is the correct config database for it to be looking at.  The permissions that the account has in SQL are 'Connect SQL' and 'View Any Database'. When I look at the permissions that are set on the SharePoint_Config2 database specifically, I do not see this admin\webfrontend$ account listed at all. 

 I went to try to add permissions on the SharePoint_Config2 database to this account, but it does not let me add it.  I can try talking to our SQL dba's to see if they can do it...but I have sa access to the SQL environment so I'm suprised that I couldn't add it.  I did see that an account named admin\appserver$  (I've been replacing our server names with webfrontend$ and appserver$) does have permissions here.

I don't think network drops are an issue.  I receive 100% successful ping response when pinging  the server continuously for a few minutes.  Of course, there could be different activities going on, on the network throughout the day that could result in lost packets, but that is doubtful at best.

Quick question for you, Do you have custom code for ex Webparts, Custom field controls, etc

Sharepoint objects you instantiate from custom code needs to be disposed properly

Take a look at this article on best practices using IDisposable WSS objects

http://msdn2.microsoft.com/en-us/library/aa973248.aspx

 Common Coding issues when using windows sharepoint services object model

http://msdn2.microsoft.com/en-us/library/bb687949.aspx

HTH

<Ram/>

I just figured this out. Took me forever.

Go to Operations. Then under Security Configuration go to Service Accounts.

 Select the Web Application Pool option. Then for the web service select Windows SharePoint Services Web Application.

 Select the DefaultAppPool (or whatever app pool was created for the default web site for your farm).

Then select configurable and enter your domain service account information so that it is running under a domain service account rather than the Network Service account.

Hi David

You can resolve the issue if you follow the steps according to the following KB Article. But make sure before to applying the article keep the backup of your registry.

 http://support.microsoft.com/kb/126962

 Hope it will work.

 Regards

 Sachin