Just moved a site to production enviroment from local test. When trying to updade pages or publish i get Out of memory exception thrown. Is this due to lack of physical/virtual memory just or can it be because of something else? I tried to update a CSS file and that went fine, but i suppose that updating a css isn't as memory consuming as working with actual nodes/xml.
I have read alot of posts regarding this issue, but haven't come to a conclusion. Is it possible that something else is causing this error? Like permissions on files/folders etc.
Running VPS, SQL server 2005 Mngmt Studio Express, IIS6.
Have a own app pool and site set up in iis for this site. Also running on this server is another umbraco site, and then three databases...
Okay, when shutting down the other site and keeping my fingers crossed and then try the same as mentioned above it worked! Bottom line is that i hadn't enough memory, as the exception stated... Buy more memory and fire it up again...
System out of memory exception on publish
Hi all!
Just moved a site to production enviroment from local test. When trying to updade pages or publish i get Out of memory exception thrown. Is this due to lack of physical/virtual memory just or can it be because of something else? I tried to update a CSS file and that went fine, but i suppose that updating a css isn't as memory consuming as working with actual nodes/xml.
I have read alot of posts regarding this issue, but haven't come to a conclusion. Is it possible that something else is causing this error? Like permissions on files/folders etc.
Running VPS, SQL server 2005 Mngmt Studio Express, IIS6.
Have a own app pool and site set up in iis for this site. Also running on this server is another umbraco site, and then three databases...
Any pointers are much appreichiated!
Additional info:
Total memory: 576mb,
Free memory: 145 mb,
Usage: 74.66%
(When not doing anything in the back end or front end)
Okay, when shutting down the other site and keeping my fingers crossed and then try the same as mentioned above it worked! Bottom line is that i hadn't enough memory, as the exception stated... Buy more memory and fire it up again...
is working on a reply...