Skip to content

Commit bae9c27

Browse files
committed
1015644: Add Troubleshooting page for document fails to load with 404 error
1 parent 8ff1738 commit bae9c27

5 files changed

Lines changed: 90 additions & 0 deletions

File tree

Document-Processing-toc.html

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3853,6 +3853,11 @@
38533853
<li><a href="/document-processing/word/word-processor/react/how-to/customize-ribbon">Customize Ribbon</a></li>
38543854
</ul>
38553855
</li>
3856+
<li>Troubleshooting
3857+
<ul>
3858+
<li><a href="/document-processing/word/word-processor/react/troubleshooting/document-loading-issue-with-404-error">Document Loading Issue with 404 Error</a></li>
3859+
</ul>
3860+
</li>
38563861
<li>FAQ
38573862
<ul>
38583863
<li><a href="/document-processing/word/word-processor/react/faq/unsupported-file-format">Unsupported Warning Message When Opening a Document</a></li>
@@ -4128,6 +4133,11 @@
41284133
<li><a href="/document-processing/word/word-processor/javascript-es5/how-to/customize-ribbon">Customize Ribbon</a></li>
41294134
</ul>
41304135
</li>
4136+
<li>Troubleshooting
4137+
<ul>
4138+
<li><a href="/document-processing/word/word-processor/javascript-es5/troubleshooting/document-loading-issue-with-404-error">Document Loading Issue with 404 Error</a></li>
4139+
</ul>
4140+
</li>
41314141
<li>FAQ
41324142
<ul>
41334143
<li><a href="/document-processing/word/word-processor/javascript-es5/faq/unsupported-file-format">Unsupported Warning Message When Opening a Document</a></li>

Document-Processing/Word/Word-Processor/javascript-es5/ej2-javascript-document-editor-toc.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,11 @@
127127
<li><a href="/document-processing/word/word-processor/javascript-es5/how-to/customize-ribbon">Customize Ribbon</a></li>
128128
</ul>
129129
</li>
130+
<li>Troubleshooting
131+
<ul>
132+
<li><a href="/document-processing/word/word-processor/javascript-es5/troubleshooting/document-loading-issue-with-404-error">Document Loading Issue with 404 Error</a></li>
133+
</ul>
134+
</li>
130135
<li>FAQ
131136
<ul>
132137
<li><a href="/document-processing/word/word-processor/javascript-es5/faq/unsupported-file-format">Unsupported Warning Message When Opening a Document</a></li>
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
layout: post
3+
title: Document loading issue in JavaScript(ES5) DOCX editor | Syncfusion
4+
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.
5+
control: document loading issue with 404 error
6+
platform: document-processing
7+
documentation: ug
8+
domainurl: ##DomainURL##
9+
---
10+
11+
# Document loading issue with 404 error in JavaScript(ES5) DOCX editor
12+
13+
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.
14+
15+
## Reasons
16+
17+
The 404 error may occur due to the following reasons:
18+
19+
- **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.
20+
- **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.
21+
- **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/`).
22+
23+
## Solution
24+
25+
1. Update the application to use the new hosted Document Editor Web Service URL introduced in v31.x.x. For example:
26+
27+
```javascript
28+
container.serviceUrl = 'https://document.syncfusion.com/web-services/docx-editor/api/documenteditor/';
29+
```
30+
31+
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.
32+
33+
> 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.
34+
35+
---

Document-Processing/Word/Word-Processor/react/document-editor-toc.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,11 @@
126126
<li><a href="/document-processing/word/word-processor/react/how-to/customize-ribbon">Customize Ribbon</a></li>
127127
</ul>
128128
</li>
129+
<li>Troubleshooting
130+
<ul>
131+
<li><a href="/document-processing/word/word-processor/react/troubleshooting/document-loading-issue-with-404-error">Document Loading Issue with 404 Error</a></li>
132+
</ul>
133+
</li>
129134
<li>FAQ
130135
<ul>
131136
<li><a href="/document-processing/word/word-processor/react/faq/unsupported-file-format">Unsupported Warning Message When Opening a Document</a></li>
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
layout: post
3+
title: Document loading issue in React DOCX editor component | Syncfusion
4+
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.
5+
control: document loading issue with 404 error
6+
platform: document-processing
7+
documentation: ug
8+
domainurl: ##DomainURL##
9+
---
10+
11+
# Document loading issue with 404 error in React DOCX editor component
12+
13+
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.
14+
15+
## Reasons
16+
17+
The 404 error may occur due to the following reasons:
18+
19+
- **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.
20+
- **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.
21+
- **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/`).
22+
23+
## Solution
24+
25+
1. Update the application to use the new hosted Document Editor Web Service URL introduced in v31.x.x. For example:
26+
27+
```javascript
28+
container.serviceUrl = 'https://document.syncfusion.com/web-services/docx-editor/api/documenteditor/';
29+
```
30+
31+
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.
32+
33+
> 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.
34+
35+
---

0 commit comments

Comments
 (0)