All URLs Returning 404 Not Found on SharePoint Server 2019 Site Collection website

Question

Hi everyone,

I'm facing an issue with SharePoint Server where pages, lists, libraries, and site pages load correctly with read control, when accessed anonymously. However, when logged in as a user with full control, these same pages return a 404 Not Found error.but Previously those pages where working properly

Some example pages that encounter this issue include:

• /sites/Apps/AppCatalog/Forms/AllItems.aspx
• /_layouts/15/viewlsts.aspx?view=14
• /Lists/HealthProjects/AllItems.aspx

Any insights or solutions to resolve this issue would be greatly appreciated.

Thank you in advance for your help!

Answer 1

Hi @Arunachalam J，

I'm glad to hear you solve the problem ,if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

[All URLs Returning 404 Not Found on SharePoint Server 2019 Site Collection website]

Issue Symptom:

Full control user are unable to find site pages and return 404 error while anonymously and reader could access the page properly.

Solution:

The web services had been stopped. Restart the services fixed the issue.

---

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

Answer 2

Hi @Arunachalam J，

You could clear the local SharePoint config cache from all front end servers can resolve this issue

Try Below Steps

Stop the SharePoint Timer service on each of the servers within the SharePoint farm. Click Start -> go to Administrative Tools -> click Services -> Right-click SharePoint Timer Service -> click Stop.

Navigate to the folder: %SystemDrive%\ProgramData\Microsoft\SharePoint\Config You will find multiple folders with similarly-formatted names containing files similar such as a326e515-0047-4328-832c-02927b84d98c.

(these folders may be hidden. To enable view hidden folders, in File Explorer, click View and check the box for Hidden Items)

1. Open the relevant folder and delete all files EXCEPT the Cache.ini file. (DO NOT DELETE THIS FILE)
2. The folder should now only have the Cache.ini file.
3. Modify the Cache.ini file by right-clicking and selecting Open With > Notepad
4. Delete the contents of the Cache.ini file (example: 268861346) and replace it with 1.
5. Save and exit the Cache.ini file ( steps 4 - 8 should be executed for each of these folders.)
6. Once steps 4 - 8 are done for each GUID folder on a server, start the SharePoint Timer Service again. 10 Start the SharePoint Timer service on each of the servers within the SharePoint farm. Click Start -> go to Administrative Tools -> click Services -> Right-click SharePoint Timer Service -> click Start.
7. Perform IIS reset and try access you site collection and you not see 404 error.By clearing the local SharePoint config cache from all front end servers can resolve this issue Try Below Steps
   1. Stop the SharePoint Timer service on each of the servers within the SharePoint farm. Click Start -> go to Administrative Tools -> click Services -> Right-click SharePoint Timer Service -> click Stop.
   2. Navigate to the folder: %SystemDrive%\ProgramData\Microsoft\SharePoint\Config You will find multiple folders with similarly-formatted names containing files similar such as a326e515-0047-4328-832c-02927b84d98c.
   (these folders may be hidden. To enable view hidden folders, in File Explorer, click View and check the box for Hidden Items)
   1. Open the relevant folder and delete all files EXCEPT the Cache.ini file. (DO NOT DELETE THIS FILE)
   2. The folder should now only have the Cache.ini file.
   3. Modify the Cache.ini file by right-clicking and selecting Open With > Notepad
   4. Delete the contents of the Cache.ini file (example: 268861346) and replace it with 1.
   5. Save and exit the Cache.ini file ( steps 4 - 8 should be executed for each of these folders.)
   6. Once steps 4 - 8 are done for each GUID folder on a server, start the SharePoint Timer Service again. 10 Start the SharePoint Timer service on each of the servers within the SharePoint farm. Click Start -> go to Administrative Tools -> click Services -> Right-click SharePoint Timer Service -> click Start.
   7. Perform IIS reset and try access you site collection and you not see 404 error.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.