diff --git a/Document-Processing-toc.html b/Document-Processing-toc.html
index f2bb1774ff..864759eb7b 100644
--- a/Document-Processing-toc.html
+++ b/Document-Processing-toc.html
@@ -3853,6 +3853,11 @@
Customize Ribbon
+ Troubleshooting
+
+
FAQ
+ Troubleshooting
+
+
FAQ
- Unsupported Warning Message When Opening a Document
diff --git a/Document-Processing/Word/Word-Processor/javascript-es5/ej2-javascript-document-editor-toc.html b/Document-Processing/Word/Word-Processor/javascript-es5/ej2-javascript-document-editor-toc.html
index bc4f36194c..46a3893f7a 100644
--- a/Document-Processing/Word/Word-Processor/javascript-es5/ej2-javascript-document-editor-toc.html
+++ b/Document-Processing/Word/Word-Processor/javascript-es5/ej2-javascript-document-editor-toc.html
@@ -127,6 +127,11 @@
- Customize Ribbon
+Troubleshooting
+
+
FAQ
- Unsupported Warning Message When Opening a Document
diff --git a/Document-Processing/Word/Word-Processor/javascript-es5/troubleshooting/document-loading-issue-with-404-error.md b/Document-Processing/Word/Word-Processor/javascript-es5/troubleshooting/document-loading-issue-with-404-error.md
new file mode 100644
index 0000000000..f308c7a82c
--- /dev/null
+++ b/Document-Processing/Word/Word-Processor/javascript-es5/troubleshooting/document-loading-issue-with-404-error.md
@@ -0,0 +1,35 @@
+---
+layout: post
+title: Document loading issue in JavaScript(ES5) DOCX editor | Syncfusion
+description: Document loading may fail with a 404 error if the Document Editor cannot reach a valid service URL, which may be due to the below reasons.
+control: document loading issue with 404 error
+platform: document-processing
+documentation: ug
+domainurl: ##DomainURL##
+---
+
+# Document loading issue with 404 error in JavaScript(ES5) DOCX editor
+
+If document loading fails and you see a 404 error in the browser console, the Document Editor is unable to reach a valid Web Service endpoint.
+
+## Reasons
+
+The 404 error may occur due to the following reasons:
+
+- **The Web Service is not running or inactive** – When hosting your own ASP.NET Core Web API, the server may be stopped or not deployed correctly, causing required endpoints such as `/Import` or `/SpellCheck` to return 404.
+- **The configured `serviceUrl` is invalid** – Issues like a missing trailing slash (`/`), wrong port number, incorrect API route, or typos will cause the editor to call incorrect endpoints.
+- **The application is using an old or discontinued Document Editor service URL** – When using an old Document Editor service URL which no longer valid (`https://ej2services.syncfusion.com/production/web-services/api/documenteditor/`).
+
+## Solution
+
+1. Update the application to use the new hosted Document Editor Web Service URL introduced in v31.x.x. For example:
+
+ ```javascript
+ container.serviceUrl = 'https://document.syncfusion.com/web-services/docx-editor/api/documenteditor/';
+ ```
+
+2. If you are using your own hosted Web API, ensure that the Web Service is running, active, and the configured service URL is valid.
+
+> Note: The hosted Web API link is provided for demonstration and evaluation only. For production use, host your own web service with the required server configuration. See the GitHub Web Service example or use the Docker image for deployment guidance.
+
+---
\ No newline at end of file
diff --git a/Document-Processing/Word/Word-Processor/react/document-editor-toc.html b/Document-Processing/Word/Word-Processor/react/document-editor-toc.html
index 6b5ded5413..9ea98f94f4 100644
--- a/Document-Processing/Word/Word-Processor/react/document-editor-toc.html
+++ b/Document-Processing/Word/Word-Processor/react/document-editor-toc.html
@@ -126,6 +126,11 @@
- Customize Ribbon
+Troubleshooting
+
+
FAQ
- Unsupported Warning Message When Opening a Document
diff --git a/Document-Processing/Word/Word-Processor/react/troubleshooting/document-loading-issue-with-404-error.md b/Document-Processing/Word/Word-Processor/react/troubleshooting/document-loading-issue-with-404-error.md
new file mode 100644
index 0000000000..ea118ec845
--- /dev/null
+++ b/Document-Processing/Word/Word-Processor/react/troubleshooting/document-loading-issue-with-404-error.md
@@ -0,0 +1,35 @@
+---
+layout: post
+title: Document loading issue in React DOCX editor component | Syncfusion
+description: Document loading may fail with a 404 error if the Document Editor cannot reach a valid service URL, which may be due to the below reasons.
+control: document loading issue with 404 error
+platform: document-processing
+documentation: ug
+domainurl: ##DomainURL##
+---
+
+# Document loading issue with 404 error in React DOCX editor component
+
+If document loading fails and you see a 404 error in the browser console, the Document Editor is unable to reach a valid Web Service endpoint.
+
+## Reasons
+
+The 404 error may occur due to the following reasons:
+
+- **The Web Service is not running or inactive** – When hosting your own ASP.NET Core Web API, the server may be stopped or not deployed correctly, causing required endpoints such as `/Import` or `/SpellCheck` to return 404.
+- **The configured `serviceUrl` is invalid** – Issues like a missing trailing slash (`/`), wrong port number, incorrect API route, or typos will cause the editor to call incorrect endpoints.
+- **The application is using an old or discontinued Document Editor service URL** – When using an old Document Editor service URL which no longer valid (`https://ej2services.syncfusion.com/production/web-services/api/documenteditor/`).
+
+## Solution
+
+1. Update the application to use the new hosted Document Editor Web Service URL introduced in v31.x.x. For example:
+
+ ```javascript
+ container.serviceUrl = 'https://document.syncfusion.com/web-services/docx-editor/api/documenteditor/';
+ ```
+
+2. If you are using your own hosted Web API, ensure that the Web Service is running, active, and the configured service URL is valid.
+
+> Note: The hosted Web API link is provided for demonstration and evaluation only. For production use, host your own web service with the required server configuration. See the GitHub Web Service example or use the Docker image for deployment guidance.
+
+---
\ No newline at end of file