it's really hard to say what it may be - i'd suggest you open the site in firefox as if it's a permanent loop that will let you know, but the erro would suggest a long running query -check that you did not overwrite your connectionstrings with invalid ones. I would also suggest enabling log4net (http://www.dotnetnuke.com/Resources/Wiki/Page/log4net-In-DotNetNuke.aspx) to see if that offers any help diagnosing what might be going wrong. Finally if you can access the database, check the EventLog table for any logged exceptions

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Hi Both,

In response to both of your queries i can confirm that before the upgrade, the event log was cleared, i have also tried this with Firefox but with no luck. Cathal I can confirm the connection strings have not changed. I have also tried changing the log script to ALL and others but the error message doesnt change. There is an exception error in the db logs but not anything that could assist me on correcting the error.

Sebastian you mentioned about the security on file or folders what could have changed in the requirements for folder security between version 6.0.2 to 6.1.3 remembering i had this fully operational before the upgrade to 6.1.3.

is there any more suggestions, could ti be a schedule that is running that could be cause the stack trace error and if so should i look at turning some of them off in the db?