There are lots of reasons this error message can occur, see: http://www.google.com/search?q=sharepoint+Server+Out+Of+Memory. In my case it happened when a new site was being provisioned using a custom site definition during the ApplyWebTemplate call. Turned out the there were subtle errors in my onet.xml. In particular I was referencing some document templates using an incorrect path:
Posts Tagged ‘onet.xml’
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.ApplyWebTemplate(String bstrUrl, String& bstrWebTemplate, Int32& plWebTemplateId)
Posted in bugs, sharepoint, tagged bug, onet.xml, sharepoint on December 15, 2009 | Leave a Comment »
Provisioning a Web Part with a predefined ID in your onet.xml of element manifest.
Posted in sharepoint, tagged onet.xml, provisioning, sharepoint, webpart on November 29, 2009 | Leave a Comment »
From time to time you might want to provision your WebParts using the CAML markup and then modify them in a feature later on. Most examples on the web find the webpart based on it’s title. i.e. However you can specify the ID of a web part in your onet.xml / element manifest like so: [...]
How to add an image web part / ImageWebPart part via your onet.xml or elements manifest
Posted in sharepoint, tagged ImageWebPart, onet.xml, sharepoint, webpart on November 16, 2009 | Leave a Comment »
Properties of note: ImageLinkUrl to image, can be relative. Note tokens are supported in this xml element, i.e. ~SiteCollections/SiteCollectionImages/logo.gif
How to add a content editor web / ContentEditorWebPart part via your onet.xml or elements manifest
Posted in sharepoint, tagged ContentEditorWebPart, onet.xml, sharepoint, webpart on November 16, 2009 | Leave a Comment »
The important part here is to remember to html encode the Content element. You can encode html online using this handy website: http://www.opinionatedgeek.com/dotnet/tools/htmlencode/Encode.aspx
