Skip to content

Commit 325d78f

Browse files
mnd999l-heemannrenetapopova
authored
Additional errors for 42NAC, 50N26, 51N7A (#398)
A few more error codes from cypher operations for scenarios around security graph initialization and seeding backups with metadata. --------- Co-authored-by: Lasse Heemann <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
1 parent 798f0d3 commit 325d78f

File tree

5 files changed

+110
-2
lines changed

5 files changed

+110
-2
lines changed

‎modules/ROOT/content-nav.adoc‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -371,6 +371,7 @@
371371
**** xref:errors/gql-errors/42NA9.adoc[]
372372
**** xref:errors/gql-errors/42NAA.adoc[]
373373
**** xref:errors/gql-errors/42NAB.adoc[]
374+
**** xref:errors/gql-errors/42NAC.adoc[]
374375
**** xref:errors/gql-errors/42NFC.adoc[]
375376
**** xref:errors/gql-errors/42NFD.adoc[]
376377
**** xref:errors/gql-errors/42NFE.adoc[]
@@ -396,6 +397,7 @@
396397
**** xref:errors/gql-errors/50N23.adoc[]
397398
**** xref:errors/gql-errors/50N24.adoc[]
398399
**** xref:errors/gql-errors/50N25.adoc[]
400+
**** xref:errors/gql-errors/50N26.adoc[]
399401
**** xref:errors/gql-errors/50N42.adoc[]
400402
*** xref:errors/gql-errors/index.adoc#system-configuration-or-operation-exceptions[System configuration or operation exceptions]
401403
**** xref:errors/gql-errors/51N00.adoc[]
@@ -473,6 +475,7 @@
473475
**** xref:errors/gql-errors/51N74.adoc[]
474476
**** xref:errors/gql-errors/51N76.adoc[]
475477
**** xref:errors/gql-errors/51N77.adoc[]
478+
**** xref:errors/gql-errors/51N7A.adoc[]
476479
*** xref:errors/gql-errors/index.adoc#procedure-exceptions[Procedure exceptions]
477480
**** xref:errors/gql-errors/52N01.adoc[]
478481
**** xref:errors/gql-errors/52N02.adoc[]

‎modules/ROOT/pages/errors/gql-errors/42NAC.adoc‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
:page-role: new-2025.11
2+
= 42NAC
3+
4+
== Status description
5+
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`.
6+
7+
== Explanation
8+
When using the `existingMetadata: use` option to restore a database from a backup, the backup metadata script must contain exactly one `CREATE DATABASE` statement.
9+
This statement must use the parameter `$database` to specify the name of the database being restored.
10+
If the metadata script is missing this statement or contains an invalid statement, the `CREATE DATABASE` operation will fail with this error.
11+
12+
== Example scenario
13+
For example, try to create a database using the following command:
14+
15+
[source,cypher]
16+
----
17+
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
18+
----
19+
20+
If the backup at `$uri` is missing the required `CREATE DATABASE` statement, an error will be thrown with GQLSTATUS 42NAC.
21+
22+
== Possible solutions
23+
24+
To resolve this issue, use another backup with a valid metadata script.
25+
26+
ifndef::backend-pdf[]
27+
[discrete.glossary]
28+
== Glossary
29+
30+
include::partial$glossary.adoc[]
31+
endif::[]

‎modules/ROOT/pages/errors/gql-errors/50N26.adoc‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
:page-role: new-2025.11
2+
= 50N26
3+
4+
== Status description
5+
error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.
6+
7+
== Explanation
8+
When using the `existingMetadata: true` option to restore a database from a backup, the backup metadata script must contain valid Cypher statements.
9+
If the metadata script contains invalid syntax, the restore operation will fail with this error.
10+
11+
== Example scenario
12+
For example, try to create a database using the following command:
13+
14+
[source,cypher]
15+
----
16+
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
17+
----
18+
19+
If the backup at `$uri` contains invalid Cypher syntax in its metadata script, an error will be thrown with GQLSTATUS 50N26.
20+
21+
== Possible solutions
22+
23+
To resolve this issue, use another backup with a valid metadata script.
24+
25+
ifndef::backend-pdf[]
26+
[discrete.glossary]
27+
== Glossary
28+
29+
include::partial$glossary.adoc[]
30+
endif::[]

‎modules/ROOT/pages/errors/gql-errors/51N7A.adoc‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
:page-role: new-2025.11
2+
= 51N7A
3+
4+
== Status description
5+
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.
6+
7+
== Explanation
8+
When initializing the Neo4j DBMS for the first time, the system attempts to determine a default admin user.
9+
This user is responsible for performing administrative tasks on the database.
10+
If no valid admin user candidate can be found, the system will throw this error.
11+
12+
== Example scenario
13+
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:
14+
15+
[source]
16+
----
17+
neo4j-admin dbms set-default-admin user-that-does-not-exist
18+
----
19+
20+
== Possible solutions
21+
22+
To resolve this issue, run `neo4j-admin dbms set-default-admin` again with a user that does exist in the system.
23+
24+
ifndef::backend-pdf[]
25+
[discrete.glossary]
26+
== Glossary
27+
28+
include::partial$glossary.adoc[]
29+
endif::[]

‎modules/ROOT/pages/errors/gql-errors/index.adoc‎

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1518,6 +1518,11 @@ Status description:: error: syntax error or access rule violation - incorrectly
15181518

15191519
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.
15201520

1521+
[role=label--new-2025.11]
1522+
=== xref:errors/gql-errors/42NAC.adoc[42NAC]
1523+
1524+
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`.
1525+
15211526
=== xref:errors/gql-errors/42NFC.adoc[42NFC]
15221527

15231528
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.
@@ -1622,6 +1627,11 @@ Status description:: error: general processing exception - sharded properties tr
16221627

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

1630+
[role=label--new-2025.11]
1631+
=== xref:errors/gql-errors/50N26.adoc[50N26]
1632+
1633+
Status description:: error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.
1634+
16251635
=== xref:errors/gql-errors/50N42.adoc[50N42]
16261636

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

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

1951+
[role=label--new-2025.11]
1952+
=== xref:errors/gql-errors/51N7A.adoc[51N7A]
1953+
1954+
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.
1955+
19411956

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

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

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

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

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

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

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

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

0 commit comments

Comments
 (0)