Skip to content
3 changes: 3 additions & 0 deletions modules/ROOT/content-nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -371,6 +371,7 @@
**** xref:errors/gql-errors/42NA9.adoc[]
**** xref:errors/gql-errors/42NAA.adoc[]
**** xref:errors/gql-errors/42NAB.adoc[]
**** xref:errors/gql-errors/42NAC.adoc[]
**** xref:errors/gql-errors/42NFC.adoc[]
**** xref:errors/gql-errors/42NFD.adoc[]
**** xref:errors/gql-errors/42NFE.adoc[]
Expand All @@ -396,6 +397,7 @@
**** xref:errors/gql-errors/50N23.adoc[]
**** xref:errors/gql-errors/50N24.adoc[]
**** xref:errors/gql-errors/50N25.adoc[]
**** xref:errors/gql-errors/50N26.adoc[]
**** xref:errors/gql-errors/50N42.adoc[]
*** xref:errors/gql-errors/index.adoc#system-configuration-or-operation-exceptions[System configuration or operation exceptions]
**** xref:errors/gql-errors/51N00.adoc[]
Expand Down Expand Up @@ -473,6 +475,7 @@
**** xref:errors/gql-errors/51N74.adoc[]
**** xref:errors/gql-errors/51N76.adoc[]
**** xref:errors/gql-errors/51N77.adoc[]
**** xref:errors/gql-errors/51N7A.adoc[]
*** xref:errors/gql-errors/index.adoc#procedure-exceptions[Procedure exceptions]
**** xref:errors/gql-errors/52N01.adoc[]
**** xref:errors/gql-errors/52N02.adoc[]
Expand Down
31 changes: 31 additions & 0 deletions modules/ROOT/pages/errors/gql-errors/42NAC.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
:page-role: new-2025.11
= 42NAC

== Status description
error: syntax error or access rule violation - invalid `CREATE DATABASE` statement. The backup metadata script contains an invalid or missing `CREATE DATABASE` statement. The metadata script must contain exactly one `CREATE DATABASE` statement and it must use the parameter `$database`.

== Explanation
When using the `existingMetadata: use` option to restore a database from a backup, the backup metadata script must contain exactly one `CREATE DATABASE` statement.
This statement must use the parameter `$database` to specify the name of the database being restored.
If the metadata script is missing this statement or contains an invalid statement, the `CREATE DATABASE` operation will fail with this error.

== Example scenario
For example, try to create a database using the following command:

[source,cypher]
----
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
----

If the backup at `$uri` is missing the required `CREATE DATABASE` statement, an error will be thrown with GQLSTATUS 42NAC.

== Possible solutions

To resolve this issue, use another backup with a valid metadata script.

ifndef::backend-pdf[]
[discrete.glossary]
== Glossary

include::partial$glossary.adoc[]
endif::[]
30 changes: 30 additions & 0 deletions modules/ROOT/pages/errors/gql-errors/50N26.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
:page-role: new-2025.11
= 50N26

== Status description
error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.

== Explanation
When using the `existingMetadata: true` option to restore a database from a backup, the backup metadata script must contain valid Cypher statements.
If the metadata script contains invalid syntax, the restore operation will fail with this error.

== Example scenario
For example, try to create a database using the following command:

[source,cypher]
----
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
----

If the backup at `$uri` contains invalid Cypher syntax in its metadata script, an error will be thrown with GQLSTATUS 50N26.

== Possible solutions

To resolve this issue, use another backup with a valid metadata script.

ifndef::backend-pdf[]
[discrete.glossary]
== Glossary

include::partial$glossary.adoc[]
endif::[]
29 changes: 29 additions & 0 deletions modules/ROOT/pages/errors/gql-errors/51N7A.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
:page-role: new-2025.11
= 51N7A

== Status description
error: system configuration or operation exception - no admin user candidate. No admin user candidate is found. Use `neo4j-admin dbms set-default-admin` to select a valid admin.

== Explanation
When initializing the Neo4j DBMS for the first time, the system attempts to determine a default admin user.
This user is responsible for performing administrative tasks on the database.
If no valid admin user candidate can be found, the system will throw this error.

== Example scenario
For example, before the database starts up for the first time, execute the following command to set a default admin user that does not exist:

[source]
----
neo4j-admin dbms set-default-admin user-that-does-not-exist
----

== Possible solutions

To resolve this issue, run `neo4j-admin dbms set-default-admin` again with a user that does exist in the system.

ifndef::backend-pdf[]
[discrete.glossary]
== Glossary

include::partial$glossary.adoc[]
endif::[]
19 changes: 17 additions & 2 deletions modules/ROOT/pages/errors/gql-errors/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -1518,6 +1518,11 @@ Status description:: error: syntax error or access rule violation - incorrectly

Status description:: error: syntax error or access rule violation - not supported standalone call. `WHERE` is not supported in a standalone call. Use `CALL ... YIELD ... WHERE ... RETURN ...` instead.

[role=label--new-2025.11]
=== xref:errors/gql-errors/42NAC.adoc[42NAC]

Status description:: error: syntax error or access rule violation - invalid `CREATE DATABASE` statement. The backup metadata script contains an invalid or missing `CREATE DATABASE` statement. The metadata script must contain exactly one `CREATE DATABASE` statement and it must use the parameter `$database`.

=== xref:errors/gql-errors/42NFC.adoc[42NFC]

Status description:: error: syntax error or access rule violation - auth info validation error. Authentication and/or authorization could not be validated. See security logs for details.
Expand Down Expand Up @@ -1622,6 +1627,11 @@ Status description:: error: general processing exception - sharded properties tr

Status description:: error: general processing exception - sharded properties transaction handling client error. Unexpected exception while getting transaction state.

[role=label--new-2025.11]
=== xref:errors/gql-errors/50N26.adoc[50N26]

Status description:: error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.

=== xref:errors/gql-errors/50N42.adoc[50N42]

Status description:: error: general processing exception - unexpected error. Unexpected error has occurred. See debug log for details.
Expand Down Expand Up @@ -1938,6 +1948,11 @@ Status description:: error: system configuration or operation exception - upgrad

Status description:: error: system configuration or operation exception - not supported in this store format. `{ <<feat>> }` is not supported in `{ <<storeFormat>> }` store format.

[role=label--new-2025.11]
=== xref:errors/gql-errors/51N7A.adoc[51N7A]

Status description:: error: system configuration or operation exception - no admin user candidate. No admin user candidate is found. Use `neo4j-admin dbms set-default-admin` to select a valid admin.


[[procedure-exceptions]]
== Procedure exceptions
Expand Down Expand Up @@ -1982,7 +1997,7 @@ Status description:: error: procedure exception - invalid address key. An addres

=== xref:errors/gql-errors/52N11.adoc[52N11]

Status description:: error: procedure exception - generic topology procedure error. An unexpected error has occurred: `{ <<msg>> }`
Status description:: error: procedure exception - generic topology procedure error. An unexpected error has occurred: `{ <<msg>> }`.

=== xref:errors/gql-errors/52N12.adoc[52N12]

Expand All @@ -2002,7 +2017,7 @@ Status description:: error: procedure exception - invalid procedure argument lis

=== xref:errors/gql-errors/52N17.adoc[52N17]

Status description:: error: procedure exception - quarantine change failed. Setting/removing the quarantine marker failed: `{ <<msg>> }`
Status description:: error: procedure exception - quarantine change failed. Setting/removing the quarantine marker failed: `{ <<msg>> }`.

=== xref:errors/gql-errors/52N18.adoc[52N18]

Expand Down