[Error] :1:62: Document is invalid: no grammar found. | Community
Skip to main content
June 5, 2020
Solved

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

  • June 5, 2020
  • 1 reply
  • 3026 views
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 ?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Shashi_Mulugu

@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/javadoc/com/scene7/ipsapi/package-summary.html

1 reply

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity AdvisorAccepted solution
Community Advisor
June 5, 2020

@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/javadoc/com/scene7/ipsapi/package-summary.html

SudarshanAuthor
June 9, 2020

@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?