Legacy v3.0.6 problem - Object reference not set to an instance of an object
Hi guys,
I've been pulling my hair out on this a bit so I'm hoping someone can help. I have a client with an old v3.0.6 site and they migrated their hosting to a different server (on shared hosting). But now when you go to edit a content page you get the following error:
Server Error in '/' Application. Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [NullReferenceException: Object reference not set to an instance of an object.] umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +257 umbraco.controls.ContentControl..ctor(Content c, publishModes CanPublish, String Id) +1103 umbraco.cms.presentation.editContent.OnInit(EventArgs e) +490 System.Web.UI.Control.InitRecursive(Control namingContainer) +333 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378
I first thought it was something to do with permissions as it seemed they were not set on the migration. So I set the permissions up accordingly (using Plesk) but still get the YSOD above. I can see the content tree and all the nodes no problem, and other sections like Settings and Developer are also fine. Just clicking on any node results in the YSOD. Even when you right click on a node you don't see the Umbraco context menu, you just get the standard browser menu.
I've recreated the site on my local dev machine and connected to the live database and it seems to work ok.
Suggestions anyone? I know this version is going back some but any advice would be great.
Not sure what the live version is using, all I know it uses Plesk control panel. Not sure if it's the setup or missing components on the server, but without knowing I can't ask the hosting company to apply changes.
Check your file permissions. The app_pool needs to have a lot of permissions. Also be sure you've got a full-trust environment. These are the two biggies for errors in v3 and Plesk is a bit awkward to get around to ensure these settings, which makes it worse. You might need to get the hosting provider involved.
Also, since this is a v3 site, you might find the legacy forum.umbraco.org helpful. That's where all the v3 info is found.
Still no dice. Hate to say that I've given up on this issue (already spent too much time) and put forward to the client to update to latest version. Let's see.
Legacy v3.0.6 problem - Object reference not set to an instance of an object
Hi guys,
I've been pulling my hair out on this a bit so I'm hoping someone can help. I have a client with an old v3.0.6 site and they migrated their hosting to a different server (on shared hosting). But now when you go to edit a content page you get the following error:
I first thought it was something to do with permissions as it seemed they were not set on the migration. So I set the permissions up accordingly (using Plesk) but still get the YSOD above. I can see the content tree and all the nodes no problem, and other sections like Settings and Developer are also fine. Just clicking on any node results in the YSOD. Even when you right click on a node you don't see the Umbraco context menu, you just get the standard browser menu.
I've recreated the site on my local dev machine and connected to the live database and it seems to work ok.
Suggestions anyone? I know this version is going back some but any advice would be great.
Thanks.
-Checked .NET version?
-Tried using xhtmlConformance mode="Legacy"/> ?
Best Regards,
Vincent
Thanks for the reply Vincent.
- It's running .NET 2.0 (2.0.50727.0)
- xhtmlConformance - this seems to be working fine on my dev environment with 'Strict'. Changing to 'Legacy' doesn't make a difference.
Your local dev, does it use IIS 6 / 7 (or other?)
Dev version is using IIS 7.
Not sure what the live version is using, all I know it uses Plesk control panel. Not sure if it's the setup or missing components on the server, but without knowing I can't ask the hosting company to apply changes.
Check your file permissions. The app_pool needs to have a lot of permissions. Also be sure you've got a full-trust environment. These are the two biggies for errors in v3 and Plesk is a bit awkward to get around to ensure these settings, which makes it worse. You might need to get the hosting provider involved.
Also, since this is a v3 site, you might find the legacy forum.umbraco.org helpful. That's where all the v3 info is found.
cheers,
doug.
Thanks Doug, I'll re-check through these and see what happens from there. Plesk is a pain in the proverbial to say the least!
Was just thinking just how far Umbraco has come since v3
Still no dice. Hate to say that I've given up on this issue (already spent too much time) and put forward to the client to update to latest version. Let's see.
is working on a reply...