19
Views
3
Comments
Problem with accumulated files in the MachineKeys folder.
Application Type
Reactive, Service
Platform Version
11.29.0 (Build 43552)

Hi everyone,


I'm having a problem that I've researched and found isn't new – it seems like there have been previous cases on this subject. I've searched various sources and used AI to help me, but nothing has solved the problem yet.


The client's production servers are experiencing disk overflow issues (due to filling the C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder).


I investigated that part of the OutSystems Pool, files created by the IIS_OutSystems user, are the problem. Looking deeper, I investigated the use of the CryptoAPI component, mainly the ComputeHash action and two other actions found in system consumption.


I made adjustments to the CryptoAPI component (in the client's current version and then downloaded the latest version from Forge – this didn't solve the problem either – and I also changed some properties in the C# source code, forcing the files not to be written). After publishing and updating all the references, the problem persists, so I'm ruling out the possibility of a problem with the CryptoAPI.

In some cases, I started investigating whether it could be the .NET Framework, which here is using version 4.8.1.


I would like support from the community to know if anyone has faced this and what the workaround is. If the problem could be in some application call, if it could be some error in the Crypto component, or if it could be a version error in the .NET Framework.


Here is some data to help:

  • Platform Version: 11.29.0 (Build 43552)
  • .NET Framework 4.8.1 (Build 528449)
  • OS: Windows Server 2016 (on the old server) and Windows Server 2022 (in the new environments - the problem occurs on both servers)
  • Existing Applications: Traditional, Reactive & Mobile


NOTE: I have already consulted official Microsoft documentation, but I find only workarounds (scripts to stop the IIS service, delete older data, and restart the IIS service), nothing that actually solves the problem.


Thank you in advance!

2023-06-05 15-54-04
João Correia

It sounds like you've done a thorough investigation already. I haven't faced this issue before and can't help much but consider monitoring the folder size over time to try to identify any patterns that might help you find the cause.

2026-04-29 12-34-16
Edson Marques
 
MVP

So, I analyzed some logs, including process and IIS logs, and I see the calls where I believe the files are being created. I don't know if it's due to an application error or the .NET Framework. This case is really giving me a headache!

The flow is increasing by around 100 to 300 files per hour on each front-end (currently with 3 production front-end servers).

I'm still investigating.

LogIIS.jpg
2025-01-31 03-15-38
Irfan Ahamed Abdul Shukoor

Hi @Edson Marques 


Deleting is temporary solution. You can also create a microsoft support ticket with all the investigation records. They might guide/help you clearly in this case.

Thank You.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.