Jun 01 2022 06:51 AM
Jun 01 2022 06:51 AM
Environment: VMware esxi vm running SharePoint server 2019 on Server 2019.
Issue: We had to reboot the server while working another issue. Since about that time the VM CPU usage has been way up. It was averaging 20ish % before reboot and now is at 70-80%.
We have rebooted the server for other maintenance this year without a problem. The only thing I can think of is that SQL server VM got cloned, so 2 were in production at same time. The clone has since been shutdown. Could SharePoint be running extra services or processes looking for cloned vm?
I'm new to SharePoint server so I'm new share what is 'normal'. The VM has 10gig memory allotted.
Thank you for the help.
Jun 02 2022 03:22 AM
@jcmfxt your issue requires bit more info:
The problem with SQL may be related.
It depends how you have configured the instance at the very beginning in SP:
If you used alias name than it should not be a problem, meaning you just swap the instance behind the alias at the moment of the SQL server clone and the rest is transparent for SharePoint.
If not than you have to check each SP service (MMS, Search, BDC etc...) and see where they are pointing to
Jun 02 2022 06:14 AM
Jun 02 2022 09:01 AM
Custom role means you are not taking benefits of the MinRole feature and you can decide every SP service startup on your own (as we are talking of a single server it's fine).
For checking the alias click on the server start and type "cliconfg.exe", the SQL Server Client Network Utility should pop up and you have the Alias tab to check whether an alias is present or not
You can match later the alias information with the Farm Information that you can find in the Servers in Farm tab in the Central Admin (/_admin/FarmServers.aspx)
To check the DB endpoint configured for the SP services, one option is to use the CA, click on "Manage Service Applications", select the SP Service then click on Properties. Another option is to use PowerShell
Jun 02 2022 10:06 AM
I ran the cliconfg and there wasn't any aliases. I went to service applications and there's not an SP listed.
Jun 03 2022 02:33 AM
the list you provided shows all the SP services configured in your farm (and relative proxy)
You have to click on each SP service (eg. App Management Service) and then select Properties on the top bar navigation. Do it only for the service (1st line) and not for the proxy (2nd line)
A pop up should appear showing the configuration of the service itself
From there you should be able to see the name of the Database and the SQL Instance.
Check if there is any discrepancies based on what you mention about the SQL Instance clone.
Side Note: You can also check if any SP major issue by analyzing the ULS logs. There is a diagnostic tool provided by MSFT for that: View diagnostic logs in SharePoint Server - SharePoint Server | Microsoft Docs
Jun 06 2022 08:23 AM
Jun 06 2022 09:00 AM
It seems you have multiple issues:
Jun 07 2022 06:48 AM
I was reading on another forum to reset Index?
Search Service Application
Jun 07 2022 07:37 AM
Yes this fix the issue usually 90% of time.
Remember that when you perform the index reset, no search result will appear for some time, SP takes time to index again all contents.
Depending on the volume of documents you have, you may schedule it during the week-end / outside business hours
Jun 09 2022 10:15 AM
Jun 10 2022 02:02 AM
Log into the SharePoint server
Open the SharePoint PowerShell Management Console
Try to Resume the search via PowerShell
$ssa = Get-SPEnterpriseSearchServiceApplication Resume-SPEnterpriseSearchServiceApplication $ssa