Roon Server fails to start with unhandled exception on Windows 11 (ref#7NBJRB)

Support
1

Hi! What’s not quite right with Roon?

· Roon is slow, freezing or won’t start

Roon is slow, freezing or won’t start

· Roon won’t start up at all

Tell us what's going on

· Roon Server fails to start correctly and creates many event view entries. Roon version 2.62 (build 1641), Windows 11 Pro (10.0.26200). I have tried re-installation (without uninstall), several machine reboots, disabling firewall to no avail.

Event viewer messages are of the form
Application: RAATServer.exe
CoreCLR Version: 6.0.3624.51421
.NET Version: 6.0.36
Description: The process was terminated due to an unhandled exception.
Exception Info: System.EntryPointNotFoundException: Unable to find an entry point named ‘RC__status_to_string’ in DLL ‘raatmanager’.
at Sooloos.RC.RC__status_to_string_(RC__Status status)
at Sooloos.RC.RC__status_to_string(RC__Status status)
at Sooloos.RAATServerApp.ev_go()
at System.Threading.Thread.StartCallback()

Many thanks
Stephen

Tell us about your home network

· EE Smarthub Pro 7, TPlink 8port Gigabit switch (unmanaged), VPN disabled.

2

Hello @Stephen_Watkins ,

Thanks for reaching out and letting us know about this error. Can you please use these instructions to access your Roon + RoonServer + RAATServer logs, upload them to the link below, and let us know once uploaded? Thank you.

https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external

4

Hi Noris.
The requested compressed log files have been uploaded.
Many thanks

5

Hi Noris.

I’ve actually managed to get things working again - I usually keep a connected external DAC powered down, but thought I would try powering it up to see what happened, and things have started as expected. One of the normal audio devices does seem to not be detected currently and that was the default but after transfering between zones it now appears to be working as normal. I’ll test over the next couple of days but hopefully this is now resolved.
Many thanks

6

@Stephen_Watkins ,

Thanks for sharing those details with us.

Let us know please your observations that will come in few days.

Thank you.

7

Hi @Stephen_Watkins,

This appears to be a temporary, edge-case race condition: RAAT tried to enumerate available local endpoints at startup while the system output wasn’t actually online. Keeping the external DAC powered resolved the issue because a valid audio device was available for system output.

This shouldn’t normally happen, and the team is investigating ways to prevent it. If you set the System Output to something that’s always available (like built-in computer speakers or a DAC that draws USB bus power) you shouldn’t encounter this issue in the meantime.

Also, ensure that RAATServer.exe is safelisted in the Microsoft Defender firewall.

Please let us know if this helps and thank you for your patience.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.