Try to get it running using 
http://wiki.magnolia-cms.com/display/WIKI/How+to+repair+broken+configuration 
and create missing node in config workspace. Then after restart you should be 
able to see more details on what happened. My guess is you deactivated some 
node used by stk or site configuration. Search for that uuid on author.
Alternatively you can get your instance running using groovy rescue servlet.
HTH,
Jan

Sent from my iPad

On Nov 13, 2011, at 4:36 PM, "Magnolia Forums (on behalf of Robert Bowen)" 
<[email protected]> wrote:

> I am not sure what happened but when I start my Tomcat now I get this error:
> 
> 
> [i]ERROR  info.magnolia.content2bean.impl.Content2BeanProcessorImpl 
> 13.11.2011 16:07:55 -- can't read index of the node [ExtendingContentWrapper 
> for config:[]]
> javax.jcr.InvalidItemStateException: e27113b4-39f1-42b2-a8d1-9ac1191de722: 
> the item does not exist anymore[/i]
> 
> ... and my magnoliaPublic isn't starting.
> 
> What's the easiest way to "reset" it? Delete the "repositories" directory? 
> Delete the public tables (in my case the tables that start with 
> pub_${wsp.name}_ and pub_version_)?
> 
> I am not sure what happened ... the only thing I can think of is that I 
> deleted one data node using the JCR browser. Can this cause the public 
> instance to corrupt?
> 
> -- 
> Context is everything: 
> http://forum.magnolia-cms.com/forum/thread.html?threadId=cd0fb18e-57c6-490f-ba08-6e48e8c1f494
> 
> 
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------


----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to