Svchost Issue - user profile service - Server 2022 high memory usage

Question

Recently I have install 3 windows server 2022 with mssql 2019.

Every two days the system stuck, and I find user profile service consume all the free memory.

it's not happens on servers without sql.

Btw: I'm not sure if it have something to do but we are backing up these servers with Veeam Application Aware

I will glad to get any advices,

Thanks in Advance,

Answer 1

-- UPDATE Aug 07, 2023 --

KB5028171 did not solve the problem.

I have also currently disabled "application-aware-processing" from Veeam, but the memory keeps growing.

As SQL Server memory usage grows, so does UALSVC memory usage.

I noticed the VGAuth ID 1000 logs reported by @LAGHEZZA SPA LAGHEZZA SPA too, but they show up that way on all servers with vmtools.

Memory-leak happen only on Win2022 + SQL Server (+ Veeam).

I'm going crazy about this!

---

Hello guys,

in July 2023 patching day I see that KB5028171 (try) to resolve UALSVC memory leak:
"The update addresses a random issue that affects svchost.exe. There is significant memory growth in a system. This occurs when svchost.exe contains the User Access Logging Service (UALSVC)."

https://support.microsoft.com/en-us/topic/july-11-2023-kb5028171-os-build-20348-1850-65cc2bda-a4a5-450f-adcb-d57ff9eb9835

I performed the update and keep under monitoring.

Daniel

Answer 2

Not much to go on but it may be some account that logs on as a service or some task. Might take a closer look at services and or any scheduled tasks to see if some process is broken.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 3

In addition to Dave's answer: SQL Server is designed to grab as much memory it can get, and it will only release it, if Windows tells it to. That is, SQL Server likes to drag as much data as possible into memory and keep it cached there, so it can serve queries faster. But if there is memory pressure, because there are other processes that needs memory, SQL Server will yield memory.

it is not clear from your post, if you are seeing any real issue, or if your concern is only that SQL Server takes up a lot of memory. In the latter case, it is, as I said, perfectly normal.

If you want to make sure that there are free memory for other process, you can configure SQL Server for how much memory it can use:

EXEC sp_configure 'show advanced options', 1
RECONFIGURE
EXEC sp_configure 'max server memory', 100000
RECONFIGURE

In this example, SQL Server is limited to 100 GB. (That is, 100000 MB). What number you would actually pick depends on how much memory you have in the machine and how much you want leave to other processes. Also deduct some 10% for the OS to play with.

Answer 4

I would definitely recommend that those who have experienced this issue, opens a support case with Microsoft. Here in the forum, at best, we can find workaround, but I don't think we will be able to find the root cause. Not the least, as it seems to require skills with both Windows Server and SQL Server.

Answer 5

Hello,

I'm back with updates:

Below is Veeam's answer to the issue:

"Dear Team,

This case has been escalated to the Advanced Technical Support team.  My name is Dmitry. Usually, I'm writing that I'm a person who will help you resolve the issue, but, unfortunately, not in that case.

According to the case notes, you faced the known issue "User profile service memory leak during SQL log backup via VIX mode on Windows 2022 servers."

We had a few MS tickets opened regarding this, the latest one had the following number 2210230060000098.

The issue is coming from the MS side, they have an issue with the User profile service.

We got the following answer from MS support at the end of November 2022,

"

Unfortunately, I cannot share with you bug number, as this is only for internal use.

KB number in which this issue will be addressed is not known yet, as we do not know when the fix will be released. From what I have gathered it will be released at earlies in 2023, but cannot say for certain when.

"

We don't know what is the current state from the MS side. Please open a ticket with MS support to check it.

From my side, I could only advise a workaround to avoid using VIX (to create a network connection between guest proxy server or use persistent agent)."

It is very strange that Microsoft does not write about this "Bug" anywhere

Now all I need to do is to find a Microsoft representative who knows and would like to give me information on this "Bug".

Unfortunately for now my workarounds are one of two:

1. start backing up transaction logs without VEEAM
2. Install new Windows server 2019 instead 2022.

Thanks in Advance,

Ariel.