Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 20, 2011 @ 21:14
    Jennifer Killingsworth
    0

    Error handling action: no parent node

    I moved a test copy of our website which is Umbraco 4.6.1 from a Windows 2003 server to a Windows 2008 server.  I then upgraded it to Umbraco 4.7.

    When I delete a file from the media section of the 4.7 version I get: Error handling action: no parent node.

    This did not happen on the 4.6.1/Win2003 version or the 4.6.1/Win2008 version of the site prior to being upgraded.

    Any ideas?

  • Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib
    Jun 20, 2011 @ 22:42
    Jan Skovgaard
    0

    Hi Jennifer

    Is there any information in the log table in the database? You could try to install the log4umbraco package, which gives you access to the logged information in the developer section.

    Could be interesting to see what it says.

    Hope this helps.

    /Jan

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 21, 2011 @ 15:08
    Jennifer Killingsworth
    0

    Thanks.  I'm not 100% sure what I'm looking for in the logs. I looked at log type Delete and for each there is nothing listing under Node.  I don't understand is why there isn't a node. 

    Also seeing lots of errors like: Couldn't find any page with the nodeId = 12488. This is most likely caused by the page isn't published! Parameter name: nodeId

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 27, 2011 @ 15:12
    Jennifer Killingsworth
    0

    Actually, I was wrong about something.  Simply moving Umbraco 4.6.1 to the Windows 2008 server results in No Parent Node errors.

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 27, 2011 @ 22:04
    Jennifer Killingsworth
    0

    Our DBA made a backup copy of the database and then I moved an Umbraco 4.6.1 copy of our website from a Windows 2003 server to a Windows 2008 server.

    Everything is working on the frontend, but if I delete either a page or an item from the media section I get "Error handling action no parent node".

    I've searched all over the place and can't find a solution. Please help!

     

     

  • webangelo 107 posts 190 karma points
    Jun 28, 2011 @ 17:36
    webangelo
    0

    Jennifer,

    It sounds like you moved both the DB and the front-end, is that correct?  Here are some quick things to check before we dig deeper.

    Did you double-check permissions on both the DB and your web directory?  Also did you try running a Republish Entire Site action?

    --Chris

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 28, 2011 @ 19:12
    Jennifer Killingsworth
    0

    Thanks Chris. 

    I get the error even if I point it to use the same database that is in use by our staging area - so I've ruled out db permissions.

    I reviewed the permissions on the site.  Everything looks okay, although I'm not sure about the ApplicationPoolIdentity in Windows 2008 - there's no such account on the server.  Bet that's the problem!

  • webangelo 107 posts 190 karma points
    Jun 28, 2011 @ 19:40
    webangelo
    0

    Actually the App Pool Identity does exist and can be assigned permissions, but it is kind of hidden.  It usually takes the form of IIS AppPool\AppPoolName (e.g. IIS AppPool\FWC).  It'll usually show up in the permissions as just the AppPoolName.  Permissions may or may not be the issue, but it's worth looking into for sure.

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 28, 2011 @ 20:33
    Jennifer Killingsworth
    0

    Yep, I found that! 

    Good News: I'm confident that the permissions are correct.

    Bad News: I'm still getting the same error.

    Sigh.

  • webangelo 107 posts 190 karma points
    Jun 28, 2011 @ 22:16
    webangelo
    0

    Jennifer,

    Can you email me the full error information that is generated when you attempt to delete?  I'll take a look at it when I get a chance and see if that leads me to anything.

    --Chris

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 28, 2011 @ 22:19
    Jennifer Killingsworth
    0

    "Error handling action no parent node" is the only error I see.

  • webangelo 107 posts 190 karma points
    Jun 28, 2011 @ 22:43
    webangelo
    0

    Does it show up in a pop-up bubble?  If not, where is the error relayed to you?

  • Jennifer Killingsworth 191 posts 248 karma points
    Jun 29, 2011 @ 01:55
    Jennifer Killingsworth
    0

    Yes, it shows up in a pop-up bubble in the lower right-hand side of the screen.

  • Simon steed 376 posts 688 karma points
    Jul 22, 2011 @ 20:59
    Simon steed
    0

    I've just started to get this on a new 4.7 build - UmbracoLog table just shows:

     

    1574    0    1052    2011-07-22 19:54:52.033    Delete   
    1575    0    0    2011-07-22 19:54:52.040    Error    Couldn't find any page with the nodeId = 0. This is most likely caused by the page isn't published!  Parameter name: nodeId
    1576    0    0    2011-07-22 19:54:52.040    Error    Couldn't find any page with the nodeId = 0. This is most likely caused by the page isn't published!  Parameter name: nodeId

    Node was originally published, after this error (with the red bubble in the bottom left corner) the node became unpublished - if I find out why, i'll update this post Tried republishing, going to try deleting the umbraco data file then republishing to see if that works

    Si

     

  • Jennifer Killingsworth 191 posts 248 karma points
    Jul 28, 2011 @ 20:29
    Jennifer Killingsworth
    0

    Ok, I moved a copy of existing Umbraco 4.6.1 site to another server.  This time I removed all the files in the App_Data folder except for the ones that were part of the original build (ClientDependency, ExamineIndexes, Packages, access.config and Umbraco.sdf).   This resolves the issue, but only if I keep the same URL.

    If I copy the exact same files/db to the same server, but located under a different web address - it doesn't fix it.

    This at least gives me a clue.

     

  • Jennifer Killingsworth 191 posts 248 karma points
    Sep 13, 2011 @ 16:23
    Jennifer Killingsworth
    0

    I found the problem.  We had a package called CMSImport PRO 1.1 installed, which was causing the error.  Since we aren't using it anymore - I uninstalled.

Please Sign in or register to post replies

Write your reply to:

Draft