Apologies for the slight delay in getting back to you here, it’s been fairly busy on Community today.
You mentioned that you’re running Roon in a VM, are you able to run Roon on the PC’s native OS? Does the “All-in-one” version of Roon work as expected on the VM?
Since you are using a Windows PC, I would verify that both Roon.exe and RAATServer.exe have been added as exceptions to your Windows firewall.
You can use these instructions to add the exceptions and the executables themselves would be located in your Database Location/Application folder path.
I would also add these exceptions to any Antivirus or other Firewall blocking applications you may have.
Hi @noris, Thanks for getting back to me, it’s much appreciated!
I should mention that I’ve been running Roon like this for several years with no trouble.
Roon is running in a Windows 10 VM. The host is running Windows Server, which I think is not appropriate for Roon Server. That’s the only reason I ended up running it in a VM. It always worked fine.
What do you mean by all-in-one? Do you mean trying to run Roon control on the VM? If so, I am unable to, because being a VM it doesn’t support the OpenGL drivers required.
On the firewall rules, I did try completely turning off all Windows firewalls as a test, and it made no difference.
Something must have changed. The question is what. I had uploaded some new music onto the server, and thought some of the files might be named a bit strangely, so I’ve tried removing the files, but it hasn’t fixed it. The only other thing I can imagine is that a Windows update might have messed things up. Both the VM host and the VM guest have had a few security intelligence updates for Windows defender, but that’s all.
Looks like the server stayed up for a bit shortly after my previous post (although still not working). I saved the log from its longest period of uptime. It contains some errors such as these:
11/12 08:50:37 Error: Error in thread pool work item: Sooloos.SynchronizationContextThreadException: In Broker:Media —> System.NullReferenceException: Object reference not set to an instance of an object.
at Sooloos.Broker.ImageCollection.<>c__DisplayClass39_1.b__1()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass48_0.b__0()
— End of inner exception stack trace —
at Sooloos.SynchronizationContextThread.SendSafe(Action handler)
at Sooloos.Broker.ImageCollection.<>c__DisplayClass39_0.b__0(CallingThread cx)
at Sooloos.CallingThread.<>c__DisplayClass10_0.b__0(Object )
11/12 08:50:37 Error: Error in thread pool work item: Sooloos.SynchronizationContextThreadException: In Broker:Media —> System.NullReferenceException: Object reference not set to an instance of an object.
at Sooloos.Broker.ImageCollection.<>c__DisplayClass39_1.b__1()
at Sooloos.SynchronizationContextThread.<>c__DisplayClass48_0.b__0()
— End of inner exception stack trace —
at Sooloos.SynchronizationContextThread.SendSafe(Action handler)
at Sooloos.Broker.ImageCollection.<>c__DisplayClass39_0.b__0(CallingThread cx)
at Sooloos.CallingThread.<>c__DisplayClass10_0.b__0(Object )
@support what would you recommend at this point. I have a backup of my database, which I assume is intact (seems to be dated 10th November). Should I uninstall and reinstall Roon?
Actually it turned out that whilst it came back and seemed operational, it was only able to play my music from Qobuz. The path to the music directories was wrong (and I have many because I use this in lieu of “folders”).
I started updating the music directories to point to the correct share, and part-way through this, Roon Server crashed, and now won’t come up again.
I may repeat the reinstall. Is it possible my Roon library is just too big now?
Thanks for keeping me posted on the updates. I spoke to our technical team regarding the issues you posted earlier this morning and this initially sounded like it could be a permissions issue since we haven’t changed anything in regards to the app recently, but from what you have recently noted it appears like it might be media related.
Can you clarify on what folder exactly this is? Have you been able to narrow down the issue to just one file/album? If so, can I please request that you share a copy of the affected album/file via private message?
Also, just so you are aware, you should be able to run RoonServer on Windows Server, even if it has no OpenGL support. One thing to keep in mind here though is that “teredo tunneling pseudo interface” can sometimes cause networking issues and if you are not using this it is suggested to disable this feature, as mentioned in our Networking Best Practices Guide.
I’m not seeing anything jump out at me from the snippets you posted. Can you send me a full copy of your Roon logs by using these instructions and send it as a shared Dropbox / Google Drive link?
I can take a look, but this also could end up being an issue related to the VM environment you have set up, so for better long-term stability I would suggest taking a look at running RoonServer on the native OS instead of in a VM.
I’m down to 2 albums that might have caused the issue. I think I’m just going to do without them. They’ve been in my library since April, and Roon was running fine, but I don’t think my database backups were working. Now I’ve deleted them, I am able to backup my database fine again.
I only really wanted to send the logs because I thought perhaps they would tell us which file was causing the crash. Roon has been up for about 9 hours now.
@noris I will think about running Roon on a native machine, but to be clear, is Windows Server 2019 now considered a “supported platform” for Roon? I think this might be a red herring though, and being able to snapshot a machine is really useful!
Thank you for narrowing the issue down to the two albums. It is possible that this issue is media-related, would you by any chance still have additional copies of these albums and can forward them to me for QA to review (and hopefully determine why they were causing such issues in your setup)?Or at least if you can let me know the names of the affected albums, I can see if there have been similar reports.
Roon supports Windows 7 and later. While we don’t specifically mention Windows Server 2019 in our Minimum Requirements, I have seen reports of users running Roon on this OS with no issues.
If the VM is working fine for you, great. I am just mentioning this because if you end up having VM-specific issues in the future related to something your environment, this is not something that we can perform extensive troubleshooting on.
I deleted the files but they were Thievery Corporation albums, It Takes A Thief and Abductions And Reconstructions.
I’m going to stick with the VM for now I think. Not to get into too much of a debate, but I would have thought VMs would be easier to troubleshoot as their hardware drivers will all be fairly standard.
I’ve got my music back anyway, which is a huge relief.
Thanks for letting me know the names of those files. I don’t see any other reports concerning these specific files, but in either case glad to hear the system is stable since removing them.
I’m going to go ahead and close out this thread, hope you have a continued enjoyable Roon experience and do consider moving Roon out of the VM if there are other issues in the future
