Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Error -xtk-170030 empty value is not valid as a key for element srcSchema of document type Source schema of entities (xtk:srcShema) while editing any schema

Avatar

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
alwaysDigital
Level 1

13-09-2018

Dear All,

I am getting error while editing any schema or creating new schema in sandbox environment. I see one of our out of box schema(nms:seedMember) got corrupted and when I try to regenerate the same, getting xtk/170030 error so basically this error is not allowing me to do any modification in any of the schema. Kindly help me if you have encountered similar issue.

Attaching screenshot of error for your reference.

SeedADD.JPG

Error_while_editing_schema.JPG

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 50
Employee
Adhiyan
Employee

Likes

239 likes

Total Posts

342 posts

Correct Reply

124 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile

Avatar
Boost 50
Employee
Adhiyan
Employee

Likes

239 likes

Total Posts

342 posts

Correct Reply

124 solutions
Top badges earned
Boost 50
Boost 5
Boost 3
Boost 25
Boost 100
View profile
Adhiyan
Employee

13-09-2018

Hello ,

There is one schema in your system which does not have the correct definition or missing values in the <srcSchema tag.

Check for schemas by last modified and see which schemas were created just before you started to have the issue. Then check which schema does not have a correct definition of the srcSchema tag. That is causing issues.

When you create a new schema , all schemas are regenerated to generate new links which can be created by the new schema and hence it does allow to create anything if even one schema is logically wrong.

Regards,
Adhiyan

Answers (3)

Answers (3)

Avatar

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
alwaysDigital
Level 1

02-10-2018

Hi Adhiyan,

We have found the issues and yes it was related to incorrect schema configuration. Thanks a lot!

Cheers,

Always Digital.

Avatar

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
alwaysDigital
Level 1

13-09-2018

Hi Adhiyan,

Thanks for your response. I checked all schema with last modified field. I found some custom schema which showed date near to date when I saw issue. So cleaned up all but still issues remains same.

I have asked Adobe support to restore nms:seedMember once and see how it goes.

Let me know if you find any other approach to dig in and fix this. Thanks a lot.

Avatar

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
alwaysDigital
Level 1

Likes

2 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 1
Affirm 1
View profile
alwaysDigital
Level 1

13-09-2018

Server Details>

Server_Details.JPG