Server Out Of memory SharePoint 2007 SP1
in [Portal Server]
|
From: Huseyin Sarioglu Huseyin on 6 Nov 2008 08:25 Hi, Our customer gets this error. There are two servers. One of them is database server and other is front end. Both of them are 16 GB memory, Win2003 x64. There are approximately 60 workflows on a sub site. Thats all, one site and workflows on it. There is 16 GB memory and we get this error. Anyway, is there any fix or patch you know? "John Timney (MVP)" wrote: > This is normally associated with workflow problems. Did you recently add > any workflows throigh Sharepoint designer. > > Regards > > John Timney (MVP) > http://www.johntimney.com > http://www.johntimney.com/blog > > > "Yman" <Yman(a)discussions.microsoft.com> wrote in message > news:2011AB5F-71BE-4C06-8A58-6967DDA14105(a)microsoft.com... > > SharePoint running on VMware workstation 6.4. The host is windows XP SP2, > > the > > VMware is windows 2003 SP2 with Sharepoint 2007 SP1 installed + SQL 2005 > > SP2 > > 1.5 GB of RAM with Due CPU. Can anyone explain the cause of this message > > "Server Out Of Memory There is no memory on the server to run your > > program. > > Please contact your administrator with this problem. at > > Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback(String > > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > > Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback(String > > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > > Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData() at > > Microsoft.SharePoint.SPListItemCollection.GetItemIndexById(Int32 id) at > > Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at > > Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, > > Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& > > objAttachmentNames, Object& objAttachmentContents, Int32& parentFolderId) > > at > > Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean > > bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean > > bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean > > suppressAfterEvents) at > > Microsoft.SharePoint.SPListItem.MigrationAddOrUpdate(Boolean bAddNew, > > Boolean > > bIsPublish, Guid newGuidOnAdd, Boolean bNoVersion, Boolean > > suppressAfterEvents) at > > Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object > > obj, > > SerializationInfo info, StreamingContext context, ISurrogateSelector > > selector) at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type > > objectType, Boolean isChildObject) at > > Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type > > objectType, Boolean isChildObject, DeploymentObject envelope) at > > Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream > > serializationStream) at > > Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream > > serializationStream) at > > Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader > > xmlReader) at > > Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() > > at Microsoft.SharePoint.Deployment.SPImport.Run() " > > >
From: John Timney (MVP) on 6 Nov 2008 15:07 I'm not aware of any patch for it. Its usually a case of evluating the workflow thats caused the issue and working ut why its consuming the memory it is - if of course thats the cause. If you can, re-deploy the workflows and test to see whihc one if causing the problem, although with 60 thats going to be a tricky activity. Regards John Timney (MVP) http://www.johntimney.com http://www.johntimney.com/blog "Huseyin Sarioglu" <Huseyin Sarioglu(a)discussions.microsoft.com> wrote in message news:006A4805-0DBA-4A46-86F3-7B51CE34A15B(a)microsoft.com... > Hi, > Our customer gets this error. There are two servers. One of them is > database > server and other is front end. Both of them are 16 GB memory, Win2003 x64. > There are approximately 60 workflows on a sub site. Thats all, one site > and > workflows on it. There is 16 GB memory and we get this error. Anyway, is > there any fix or patch you know? > > "John Timney (MVP)" wrote: > >> This is normally associated with workflow problems. Did you recently add >> any workflows throigh Sharepoint designer. >> >> Regards >> >> John Timney (MVP) >> http://www.johntimney.com >> http://www.johntimney.com/blog >> >> >> "Yman" <Yman(a)discussions.microsoft.com> wrote in message >> news:2011AB5F-71BE-4C06-8A58-6967DDA14105(a)microsoft.com... >> > SharePoint running on VMware workstation 6.4. The host is windows XP >> > SP2, >> > the >> > VMware is windows 2003 SP2 with Sharepoint 2007 SP1 installed + SQL >> > 2005 >> > SP2 >> > 1.5 GB of RAM with Due CPU. Can anyone explain the cause of this >> > message >> > "Server Out Of Memory There is no memory on the server to run your >> > program. >> > Please contact your administrator with this problem. at >> > Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback(String >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at >> > Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback(String >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at >> > Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData() at >> > Microsoft.SharePoint.SPListItemCollection.GetItemIndexById(Int32 id) at >> > Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at >> > Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, >> > Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& >> > objAttachmentNames, Object& objAttachmentContents, Int32& >> > parentFolderId) >> > at >> > Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean >> > bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean >> > bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, >> > Boolean >> > suppressAfterEvents) at >> > Microsoft.SharePoint.SPListItem.MigrationAddOrUpdate(Boolean bAddNew, >> > Boolean >> > bIsPublish, Guid newGuidOnAdd, Boolean bNoVersion, Boolean >> > suppressAfterEvents) at >> > Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object >> > obj, >> > SerializationInfo info, StreamingContext context, ISurrogateSelector >> > selector) at >> > Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type >> > objectType, Boolean isChildObject) at >> > Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type >> > objectType, Boolean isChildObject, DeploymentObject envelope) at >> > Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream >> > serializationStream) at >> > Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream >> > serializationStream) at >> > Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader >> > xmlReader) at >> > Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() >> > at Microsoft.SharePoint.Deployment.SPImport.Run() " >> >> >>
From: Huseyin Sarioglu on 7 Nov 2008 03:58 Thanks for answer. This error is not continuous. Once or twice in a month. And it is fixed by iisreset. Yesterday I noticed that virtual memory settings of front-end server has been changed. It is limited to 2048 MB. I've changed a few settings in Performance Options. Current settings : - Visual Effects : Adjust for best performance - Advanced -> Virtual Memory - System managed size I wish this is the main reason of problem. "John Timney (MVP)" wrote: > I'm not aware of any patch for it. Its usually a case of evluating the > workflow thats caused the issue and working ut why its consuming the memory > it is - if of course thats the cause. > > If you can, re-deploy the workflows and test to see whihc one if causing the > problem, although with 60 thats going to be a tricky activity. > > Regards > > John Timney (MVP) > http://www.johntimney.com > http://www.johntimney.com/blog > > > "Huseyin Sarioglu" <Huseyin Sarioglu(a)discussions.microsoft.com> wrote in > message news:006A4805-0DBA-4A46-86F3-7B51CE34A15B(a)microsoft.com... > > Hi, > > Our customer gets this error. There are two servers. One of them is > > database > > server and other is front end. Both of them are 16 GB memory, Win2003 x64. > > There are approximately 60 workflows on a sub site. Thats all, one site > > and > > workflows on it. There is 16 GB memory and we get this error. Anyway, is > > there any fix or patch you know? > > > > "John Timney (MVP)" wrote: > > > >> This is normally associated with workflow problems. Did you recently add > >> any workflows throigh Sharepoint designer. > >> > >> Regards > >> > >> John Timney (MVP) > >> http://www.johntimney.com > >> http://www.johntimney.com/blog > >> > >> > >> "Yman" <Yman(a)discussions.microsoft.com> wrote in message > >> news:2011AB5F-71BE-4C06-8A58-6967DDA14105(a)microsoft.com... > >> > SharePoint running on VMware workstation 6.4. The host is windows XP > >> > SP2, > >> > the > >> > VMware is windows 2003 SP2 with Sharepoint 2007 SP1 installed + SQL > >> > 2005 > >> > SP2 > >> > 1.5 GB of RAM with Due CPU. Can anyone explain the cause of this > >> > message > >> > "Server Out Of Memory There is no memory on the server to run your > >> > program. > >> > Please contact your administrator with this problem. at > >> > Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback(String > >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > >> > Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback(String > >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > >> > Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData() at > >> > Microsoft.SharePoint.SPListItemCollection.GetItemIndexById(Int32 id) at > >> > Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at > >> > Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, > >> > Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& > >> > objAttachmentNames, Object& objAttachmentContents, Int32& > >> > parentFolderId) > >> > at > >> > Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean > >> > bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean > >> > bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, > >> > Boolean > >> > suppressAfterEvents) at > >> > Microsoft.SharePoint.SPListItem.MigrationAddOrUpdate(Boolean bAddNew, > >> > Boolean > >> > bIsPublish, Guid newGuidOnAdd, Boolean bNoVersion, Boolean > >> > suppressAfterEvents) at > >> > Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object > >> > obj, > >> > SerializationInfo info, StreamingContext context, ISurrogateSelector > >> > selector) at > >> > Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type > >> > objectType, Boolean isChildObject) at > >> > Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type > >> > objectType, Boolean isChildObject, DeploymentObject envelope) at > >> > Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream > >> > serializationStream) at > >> > Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream > >> > serializationStream) at > >> > Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader > >> > xmlReader) at > >> > Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() > >> > at Microsoft.SharePoint.Deployment.SPImport.Run() " > >> > >> > >> > > >
From: Stefan Weyer (maxxcomm) on 7 Nov 2008 05:06 Hi Huseyin, As far as I see the is a dual core on the server. If the problem occurs, what about the CPU? Are they on 100% and are they both on the same level? Did your customer do any customizations and/or programming or does he use 3rd-Party Webparts? If so, did the developers specially dispose objects like SPSite and SPWeb? Also do have a look here: http://blogs.technet.com/stefan_gossner/archive/2007/11/26/dealing-with-memory-pressure-problems-in-moss-wss.aspx HTH, Cheers Stefan "Huseyin Sarioglu" <HuseyinSarioglu(a)discussions.microsoft.com> wrote in message news:E8BBDCC0-2CA7-4C42-B39C-D839460FBF5B(a)microsoft.com: > Thanks for answer. > This error is not continuous. Once or twice in a month. And it is fixed by > iisreset. > Yesterday I noticed that virtual memory settings of front-end server has > been changed. It is limited to 2048 MB. I've changed a few settings in > Performance Options. Current settings : > - Visual Effects : Adjust for best performance > - Advanced -> Virtual Memory - System managed size > > I wish this is the main reason of problem. > > "John Timney (MVP)" wrote: > > > I'm not aware of any patch for it. Its usually a case of evluating the > > workflow thats caused the issue and working ut why its consuming the memory > > it is - if of course thats the cause. > > > > If you can, re-deploy the workflows and test to see whihc one if causing the > > problem, although with 60 thats going to be a tricky activity. > > > > Regards > > > > John Timney (MVP) > > http://www.johntimney.com > > http://www.johntimney.com/blog > > > > > > "Huseyin Sarioglu" <Huseyin Sarioglu(a)discussions.microsoft.com> wrote in > > message news:006A4805-0DBA-4A46-86F3-7B51CE34A15B(a)microsoft.com... > > > Hi, > > > Our customer gets this error. There are two servers. One of them is > > > database > > > server and other is front end. Both of them are 16 GB memory, Win2003 x64. > > > There are approximately 60 workflows on a sub site. Thats all, one site > > > and > > > workflows on it. There is 16 GB memory and we get this error. Anyway, is > > > there any fix or patch you know? > > > > > > "John Timney (MVP)" wrote: > > > > > >> This is normally associated with workflow problems. Did you recently add > > >> any workflows throigh Sharepoint designer. > > >> > > >> Regards > > >> > > >> John Timney (MVP) > > >> http://www.johntimney.com > > >> http://www.johntimney.com/blog > > >> > > >> > > >> "Yman" <Yman(a)discussions.microsoft.com> wrote in message > > >> news:2011AB5F-71BE-4C06-8A58-6967DDA14105(a)microsoft.com... > > >> > SharePoint running on VMware workstation 6.4. The host is windows XP > > >> > SP2, > > >> > the > > >> > VMware is windows 2003 SP2 with Sharepoint 2007 SP1 installed + SQL > > >> > 2005 > > >> > SP2 > > >> > 1.5 GB of RAM with Due CPU. Can anyone explain the cause of this > > >> > message > > >> > "Server Out Of Memory There is no memory on the server to run your > > >> > program. > > >> > Please contact your administrator with this problem. at > > >> > Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback(String > > >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > > >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > > >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > > >> > Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback(String > > >> > bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, > > >> > SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, > > >> > ISPDataCallback pPagingCallback, ISPDataCallback pSchemaCallback) at > > >> > Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData() at > > >> > Microsoft.SharePoint.SPListItemCollection.GetItemIndexById(Int32 id) at > > >> > Microsoft.SharePoint.SPListItem.EnsureItemIsValid() at > > >> > Microsoft.SharePoint.SPListItem.PrepareItemForUpdate(Guid newGuidOnAdd, > > >> > Boolean bMigration, Boolean& bAdd, Boolean& bPublish, Object& > > >> > objAttachmentNames, Object& objAttachmentContents, Int32& > > >> > parentFolderId) > > >> > at > > >> > Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean > > >> > bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean > > >> > bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, > > >> > Boolean > > >> > suppressAfterEvents) at > > >> > Microsoft.SharePoint.SPListItem.MigrationAddOrUpdate(Boolean bAddNew, > > >> > Boolean > > >> > bIsPublish, Guid newGuidOnAdd, Boolean bNoVersion, Boolean > > >> > suppressAfterEvents) at > > >> > Microsoft.SharePoint.Deployment.ListItemSerializer.SetObjectData(Object > > >> > obj, > > >> > SerializationInfo info, StreamingContext context, ISurrogateSelector > > >> > selector) at > > >> > Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type > > >> > objectType, Boolean isChildObject) at > > >> > Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type > > >> > objectType, Boolean isChildObject, DeploymentObject envelope) at > > >> > Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream > > >> > serializationStream) at > > >> > Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream > > >> > serializationStream) at > > >> > Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader > > >> > xmlReader) at > > >> > Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() > > >> > at Microsoft.SharePoint.Deployment.SPImport.Run() " > > >> > > >> > > >> > > > > > >
|
Pages: 1 Prev: stsadm -o export with versions 4 Next: using java script in survey sharepoint list |