Copied to clipboard

Flag this post as spam?

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


  • Andreas 3 posts 22 karma points
    Jan 18, 2012 @ 13:46
    Andreas
    0

    Content only visible in preview

    Hi guys,

    I'm panicking right now. I have managed to screw up something in our umbraco installation so that every page you try to visit gives you a "An error occurred while processing your request."

    All my content is still visible in content tree and preview shows everything fine. I have tried republishing and also to rebuild the xml tables with no luck.

    Can anybody help me?

  • Stephen 204 posts 246 karma points
    Jan 18, 2012 @ 13:53
    Stephen
    0

    Can you show us a screen grab or the error? Sounds like a permissions thing on the application pool....

    S

  • Andreas 3 posts 22 karma points
    Jan 18, 2012 @ 14:04
    Andreas
    0

    All I see is the "An error occurred while processing your request." on a blank page, even with customerrors off in web-config.

    The only thing I have found in the UmbracoLog that looks interesting is this:

    Error Republishing: System.ArgumentException: Item has already been added. Key in dictionary: '1543'  Key being added: '1543'     at System.Collections.Hashtable.

    Insert(Object key, Object nvalue, Boolean add)     at System.Collections.Hashtable.Add(Object key, Object value)     at umbraco.content.LoadContentFromDatabase(Boolean loadDocuments)
  • Rodion Novoselov 694 posts 859 karma points
    Jan 18, 2012 @ 14:23
    Rodion Novoselov
    0

    It seems to me that I've already seen such a situation once but I don't remember exactly how it was gone. I would try to stop completely the iis application, remove the umbraco content file (the default one is "umbraco.config" ) and than to start the application back and republish the entire site.

  • Andreas 3 posts 22 karma points
    Jan 18, 2012 @ 14:28
    Andreas
    0

    Ok so by some magic I managed to get it up and running within 30 minutes of posting here, I have been troubleshooting for 2 days up until now :)

    Ridion: I actually tried your solution with no succcess. I ended up having to unpublish everything from the database (cmsDocument) and when doing a republish after that the wierd error was gone.

    Thanks for fast responses guys!

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies