Expand my Community achievements bar.

SOLVED

[Error] :1:62: Document is invalid: no grammar found.

Avatar

Level 1
The prod environment contains the following errors in startuplogs. It doesnt have a time frame to trace hence it is very difficult to identify the root cause. Did a grep of the error content in my local instance but no luck

[Error] :1:65: Document root element "getUploadTaskStatusReturn", must match DOCTYPE root "null". [Error] :1:62: Document is invalid: no grammar found. [Error] :1:62: Document root element "getJobLogDetailsReturn", must match DOCTYPE root "null". [Error] :1:65: Document is invalid: no grammar found. [Error] :1:65: Document root element "getAssociatedAssetsReturn", must match DOCTYPE root "null". [Error] :1:57: Document is invalid: no grammar found. [Error] :1:57: Document root element "deleteAssetReturn", must match DOCTYPE root "null". [Error] :1:55: Document is invalid: no grammar found. [Error] :1:55: Document root element "getAssetsReturn", must match DOCTYPE root "null". [Error] :1:55: Document is invalid: no grammar found. [Error] :1:55: Document root element "getAssetsReturn", must match DOCTYPE root "null". [Error] :1:55: Document is invalid: no grammar found. [Error] :1:55: Document root element "getAssetsReturn", must match DOCTYPE root "null". [Error] :1:65: Document is invalid: no grammar found. [Error] :1:65: Document root element "getAssociatedAssetsReturn", must match DOCTYPE root "null". [Error] :1:65: Document is invalid: no grammar found. [Error] :1:65: Document root element "getAssociatedAssetsReturn", must match DOCTYPE root "null". [Error] :1:57: Document is invalid: no grammar found. [Error] :1:57: Document root element "deleteAssetReturn", must match DOCTYPE root "null". [Error] :1:56: Document is invalid: no grammar found. [Error] :1:56: Document root element "uploadPostReturn", must match DOCTYPE root "null". [Error] :1:56: Document is invalid: no grammar found. [Error] :1:56: Document root element "uploadPostReturn", must match DOCTYPE root "null". [Error] :1:56: Document is invalid: no grammar found. [Error] :1:56: Document root element "uploadPostReturn", must match DOCTYPE root "null". [Error] :1:65: Document is invalid: no grammar found. [Error] :1:65: Document root element "getUploadTaskStatusReturn", must match DOCTYPE root "null". [Error] :1:62: Document is invalid: no grammar found. [Error] :1:62: Document root element "getJobLogDetailsReturn", must match DOCTYPE root "null".

Has anybody seen this issue before ?
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Sudarshan , Few Questions:

  • Which version of AEM are you using?
  • Are you using Dynamic Media/Scene7?
  • What runmode are you running your AEM?

Seems to be error related to Scene7. Can you check if you any empty or erroneous Scene7 Configurations or custom services/components.

 

https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/developing/ref/...

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

@Sudarshan , Few Questions:

  • Which version of AEM are you using?
  • Are you using Dynamic Media/Scene7?
  • What runmode are you running your AEM?

Seems to be error related to Scene7. Can you check if you any empty or erroneous Scene7 Configurations or custom services/components.

 

https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/developing/ref/...

Avatar

Level 1

@Shashi_Mulugu Thanks for the help. Seems the error logs are related to scene7 API.

Which version of AEM are you using? AEM 6.5

Are you using Dynamic Media/Scene7? Yes

What run mode are you running AEM? We do have have scene7_dynamicmedia runmode enabled and Dynamic Media configured.

 

Doing a global search revealed that all the error proned html files are there in this location /content/help/en/experience-manager/6-3/sites/developing/using/reference-materials/javadoc/com/scene7/ipsapi/*.html

 

Can you help on how to resolve the same? 

Avatar

Level 1

@Shashi_Mulugu There is only one config in place, and the configurations look good. There are no empty configs as such. We have custom service/ components. Kindly suggest proceeding further