The SharePoint health analyzer has detected some critical issues that require your Attention....

Question

Currently, SharePoint 2019 running on on-premises 2019.

The central admin page health analyzer has detected some critical issue that require your attention.

when i click to view this issue.

1. InfoPath forms services forms cannot be filled out in a web browser because no state service connection is configured - i do not need this feature and how to hide/remove the warning in my CA?
2. The Net.Pipe listener adapter isn't available- i tried to restart the services and is up and running but my health analyzer still detect error. failing services SPTimerService and i perform restart the services still the same issue.
3. Some content databases are growing too large - i understand the recommand size is 200GB and i already over the limit.
4. How do i remove/hide these error from CA?

Appreciate if someone can assist and provide workaround/solution?

Answer 1

Hi @jason tan,

Thank you for posting in this community.

1.I know you don't need InfoPath forms services, but InfoPath forms services will not be supported until after July 14, 2024, when support will end.

(Reference: Support update for InfoPath Forms Services in Microsoft 365)

We don't have a way to shut down this service at the moment. I note that this error message is just a warning, and if you don't use InfoPath forms services and it doesn't affect you much, you can choose to ignore it and not worry about it.

If you really need to hide this information, you can try to configure a state service to solve this problem.

2.Maybe you have already tried this, but you can follow the steps below to start the Net.Pipe Listener Adapter service on the server again:

Then click on the problem in the Review problems and solutions page to go to the problem details page, and then re-analyze the problem to see if it still exists.

3.You can create new content databases and move certain site collections to new content databases to alleviate the problem of some content databases being too large.

However, we recommend a maximum of 500 content databases in a farm.

Before you create a new content database, I recommend that you be clear about the limitations of content databases.

In this article are the steps to create a new content database: Add content databases in SharePoint Server.

In this post are the steps to move a site collection to a new content database: Move site collections between databases in SharePoint Server.

This message: "Some content databases are growing too large." is a reminder that some of your content databases are over 100GB and most likely have not reached the 200GB limit. You can follow the steps below to resolve this issue.

In short, you don't have to worry too much about the information in your SharePoint health analyzer. As long as your SharePoint is doing its business and these issues don't affect you too much, you can choose to ignore them. Relax!

---

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.

Answer 2

Hi @jason tan,

Thank you for your reply.

You can follow these articles to resolve your problem.

1. The Net.Pipe Listener Adapter isn't available (SharePoint Server)
2. One of the cache hosts in the cluster is down (SharePoint Server)
3. One or more services have started or stopped unexpectedly (SharePoint Server)

---

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.