I have a very strange problem, i have this quite simple webform:
using System; using umbraco.presentation.nodeFactory; namespace IntraConnect { public partial class Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { var test = new Node(); } } }
the line:
var test = new Node();
Makes the WebDev.WebServer20.exe crash when i exit the debugger.
If i single step, it never returns from that line.
Other Umbraco functions like:
var members = Member.GetAll;
Works fine.
I work against this Umbraco installation:
umbraco v 4.0.2.1 (Assembly version: 1.0.3441.17657)
For a very long time, there was no problem at all, then for some unknown reason it started to crash. I have no clue why that problem suddently arrived :-(
I am trying to get permission to upgrade the umbraco installation, but no luck yet.
Does any of you have any ideas what i can do to solve the problem ?
Why are you using a parameterless constructor to create a node?
What do you hope to achieve, NodeFactory is read only access to the content cache so typically you'd instantiate with and Id or the static GetCurrent method.
After debugging through the Umbraco source code, i found out the umbracoSettings.config file was missing for some weird reason.
This had a rather bad effect on Umbraco, because it wanted to log something, had to read that config file to be sure logging was enabled. The file was not found, which did throw an exception. And inside this exception it wanted to log it, then it had to see if logging was enabled and wupti loop of death!
Which made the VS2010 webserver crash.
I am running a rather old version of Umbraco, hope this bug has been fixed since.
new Node() crashes WebDev.WebServer20.exe
Hi there
I have a very strange problem, i have this quite simple webform:
the line:
Makes the WebDev.WebServer20.exe crash when i exit the debugger.
If i single step, it never returns from that line.
Other Umbraco functions like:
Works fine.
I work against this Umbraco installation:
umbraco v 4.0.2.1 (Assembly version: 1.0.3441.17657)
For a very long time, there was no problem at all, then for some unknown reason it started to crash. I have no clue why that problem suddently arrived :-(
I am trying to get permission to upgrade the umbraco installation, but no luck yet.
Does any of you have any ideas what i can do to solve the problem ?
Why are you using a parameterless constructor to create a node?
What do you hope to achieve, NodeFactory is read only access to the content cache so typically you'd instantiate with and Id or the static GetCurrent method.
Hi Darren
Thanks for your answer.
I have just tried to simplify the crashing example as much as possible, to much I can hear :)
What I am actually trying to do, is to get a specific node:
And then get it's children to convert some of the content to a PDF file.
If I change to the above line, the problem is still the same :-(
Isn't there anyone who has an idea ?
Event Viewer should have the full stack trace that will help lead you to the issue.
On a semi-related note 4.0.x is a very out dated release (4.6.1 is the current stable) and no longer bug-fixed. I'd strongly recommend upgrading.
Hi Slace
Trust me i would love to upgrade, still trying to get the permission to do it :-(
Thanks for the tips.
In my event viewer on the development machine i get this:
Faulting application webdev.webserver20.exe, version 10.0.30319.1, stamp 4ba204ca, faulting module kernel32.dll, version 5.1.2600.5781, stamp 49c4f482, debug? 0, fault address 0x00012afb.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
When trying to debug:
var test = new Node(1389);
It hangs, and i get the error when i stop the debugger.
Any ideas?
Finally I found out what was causing the problem.
After debugging through the Umbraco source code, i found out the umbracoSettings.config file was missing for some weird reason.
This had a rather bad effect on Umbraco, because it wanted to log something, had to read that config file to be sure logging was enabled. The file was not found, which did throw an exception. And inside this exception it wanted to log it, then it had to see if logging was enabled and wupti loop of death!
Which made the VS2010 webserver crash.
I am running a rather old version of Umbraco, hope this bug has been fixed since.
is working on a reply...