RPC connection error

Have you tried using gRPC instead of RPC? RPC over TCP/IP can have payload size limitations, which might cause issues in certain scenarios. It’s unusual that this behavior would only occur on Windows 11, but it’s worth considering whether the payload limits are being reached.

Some information about the RPC payload limit in this support article: Large-size metadata card configuration editing with TCP/IP protocol causes "Access is denied" error

We have tried gRPC and still get the error randomly.  Looking at our Metadata configuration for this class we up to 4 rules that can trigger depending on the properties that are filled out.  The main rule is only 59 KB.  Looking at all of our rules for metadata card configuration no matter what class is used comes to 288 KB.  I'm still wondering if it is something in our rules that can make this happen.  I do find it odd that it only happens on Windows 11 as well and with multiple users.  Its very hard to replicate the error to try troubleshooting since it is random. 

We tried having the user use the New client but it is limited features so it has degraded their performance when entering documents.  I might have them try again since new features seem to keep getting added each month.

Please try the new client again and see if that helps. New features are indeed added monthly and most of the high-priority ones are already included. You can check the progress here: Latest enhancements in the new M-Files Desktop

If this still keeps happening, it might be worth contacting your M-Files reseller and see if they have any thoughts. It would be also useful to get the full error stacks when this happens, in case they need to contact our Support team for further investigation.

We have the same problem as well. Using the new desktop client and Windows 11 24H2. 

qprod you are experiencing crashes with the new desktop experience?  I just started to revisit this yesterday since we had multiple users getting the RPC connection errors a lot with our smaller vault.  They just updated the client to March's update, so I don't know if that caused more issues with this.  One thing that I did was move one of the users to the new desktop experience and that seemed to have helped but they miss the preview window when dragging and dropping.  Reason why I bring up the smaller vault is it hardly has any metadata configurations.  I have heard that we experience more when there is a value list property that they try to fill out, then the metadata card freezes and they have to close out of M-Files which makes the MFstatus.exe stop running.  This causes the RPC connection error.  I have made a quick fix, so the user doesn't have to reboot by just having them start MFstatus.exe by placing that on their desktop.  I thought about making a script that will consistently watch if MFstatus.exe is running and if not start it again.

I have submitted a ticket to our vendor when we first started seeing this issue along with multiple logs, event viewers and trace logs but it seems M-Files support is unable to pinpoint the issue.  They keep pointing to our EDR software (we use CrowdStrike).  What I have noticed is Windows 10 never had this issue but with that no longer being supported by Microsoft we had to upgrade to Windows 11.  I have gone as far as wipe the machine and not load any of our security tools, but we still see the issue which would take out any of our EDR/MDR concerns.  

Preview when drag-dropping an existing file to M-Files is planned to be added to New Desktop during Q2. You can find the updated roadmap in Feature comparison between classic and new
M-Files Desktop.

Please see this support article for information about the MFStatus issue with the March release: MFStatus Crashes When Creating Documents in M‑Files Desktop (26.3.15818.7)

Preview when drag-dropping an existing file to M-Files is planned to be added to New Desktop during Q2. You can find the updated roadmap in Feature comparison between classic and new
M-Files Desktop.

Please see this support article for information about the MFStatus issue with the March release: MFStatus Crashes When Creating Documents in M‑Files Desktop (26.3.15818.7)

Are there any new updates regarding this error? We are receiving an increasing number of reports about this issue from clients.

M-Files Online 26.3 SR3 will be released today to address the issue (CE-3325). Release notes are already available.