Fatal Error starting up: Registry root not present

[stk137]

starting Alfresco I am now getting

ERROR [web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Failed to start modules
        at org.alfresco.repo.module.ModuleComponentHelper.startModules(ModuleComponentHelper.java:240)
…
Caused by: org.alfresco.error.AlfrescoRuntimeException: Registry root not present:
   Store: system://system
   Path:  /sys:system-registry
        at org.alfresco.repo.admin.registry.RegistryServiceImpl.getRegistryRootNodeRef(RegistryServiceImpl.java:137)
        at org.alfresco.repo.admin.registry.RegistryServiceImpl.getPath(RegistryServiceImpl.java:184)
…‍‍‍‍‍‍‍‍‍‍

Is this registry stored in the database like any other Alfresco content?  If so, how could it have disappeared and how can I restore it?
If it's not in the database, where/what is it?

[derek]

Hi,

The storage area is in a system folder within the repository itself.  It should have been added there by a patch.

Caused by: org.alfresco.error.AlfrescoRuntimeException: Registry root not present:
   Store: system://system
   Path:  /sys:system-registry

What is the result of

select id, applied_to_schema, applied_on_date, applied_to_server, was_executed, succeeded, report from alf_applied_patch where id = 'patch.systemRegistryBootstrap';‍

Regards

[stk137]

…
What is the result of

select id, applied_to_schema, applied_on_date, applied_to_server, was_executed, succeeded, report from alf_applied_patch where id = 'patch.systemRegistryBootstrap';‍

…

well this happened again, I forget what happened the first time.  It was a local dev database, so I probabaly trashed and restarted.
This time it happened after a bad backup/restoration sequence - restored database and restored/updated alfresco then restored alf_data.  It was ok after the alfresco update before I restored alf_data.
So I am assuming if I restore the database and alf_data first and then start/update alfresco, I'll be ok.  But I'm curious if there was any other options, especially since I don't know what caused it the first time.

here's the query results

+——————————-+——————-+———————+———————————+————–+———–+————————————————————————————————-+
| id                            | applied_to_schema | applied_on_date     | applied_to_server               | was_executed | succeeded | report                                                                                          |
+——————————-+——————-+———————+———————————+————–+———–+————————————————————————————————-+
| patch.systemRegistryBootstrap |                21 | 2007-09-21 14:58:22 | 2.1.0 (482) - Community Network |              |           | Imported view into bootstrap location: / (system://system/3b22bf56-7902-11db-8697-e79e4834e0e9) | 
+——————————-+——————-+———————+———————————+————–+———–+————————————————————————————————-+
1 row in set (0.00 sec)‍‍‍‍‍‍‍