Export to Excel not completing on Windows 11 with playlist over 800 songs [Ticket In]

What’s happening?

· Export feature hangs

How can we help?

· Please see below

Other options

· Other

Describe the issue

Hello. Using Roon 2.0 (build 1490). I received a Roon tip about exporting to Excel. I tried it 3x times last night on a playlist with 800+ songs, even letting the last attempt run overnight and it never completes. I do have Excel installed on my Windows 11 machine.

Any suggestions?

Describe your network setup

AT&T BGW320-505 ONT
Firewalla Gold
Dell PowerConnect 2816 Switch
Cat6 from that switch to my office
TP-Link TL-SG1016D Swtich
Cat 6 to my laptop.

It just sits at this screen

I’d like to weigh in with the same issue. I’ve been using roon for years, and have frequently done excel exports of playlists. Now they just display the “working” icon and hang, similar to the parent message. The playlists vary from about 200 to slightly over 1000 songs, length doesn’t seem to matter. Rebooting the roon server doesn’t help.
My roon server: OS 1.0 build 259. On rock (Intel NUC/10i7FNH, 32GB, 1 TB SSD, this used to be a recommended system by roon for rock). Roon server software: 2.0 build 1490
My roon client: Windows 10, also 2.0 build 1490. (note the initial post was running windows 11)
roon library: Samba mount from raspberry pi 5 server running raspbian.
Network: all machine above on cat 6 ethernet
Likely not relevant, but music system is connected via USB from rock to Benchmark DAC.
Again, used to work, same hardware. I’ve recently had one or two successful exports, but 20 or so other attempts just hang. Have roon server logs mounted on windows, don’t see anything helpful in the logs, but I may not know enough about the roon server to be looking in the right place.

Hey @Jamie_Dewoody1 and @jim_hamilton,

Thanks for sharing your report of the export function not completing successfully! What were the specific names of the playlists you’ve attempted to export? While our team takes a closer look into things, we have a few follow-up questions:

  1. Are you able to successfully export via Folder or Sounddiz?
  2. What type of content are on the failed playlists? Local content, streaming content, or a mixed bag?
  3. Are you able to export a smaller playlist, lets say one under 100 tracks via excel successfully?

We’ll be on standby for your reply, thank you!

I appreciate the prompt customer support.
I have extensive experience with excel export, have not had reason to try the folder or sounddiz exports up to now. Per your questions:

  1. successfully exported a small “demojazz” playlist (9 hi-res tracks) via folder. Same playlist hangs on sounddiz export, similar to excel export attempts
  2. All the playlists are built from local files on my fileserver - local content, no streaming content
  3. the playlists range from 9 to about 1500 tracks. They all used to export fine, now every one I have tried has simply hung…The 9 track “demojazz” playlist that exported via the “folder” option still hangs on attempted excel export.
  4. specific names of playlists: no special characters if thats the concern. Names include: play1, play2, rock, jazz1, jazz2 - simple vanilla ascii text names.

Hi @jim_hamilton, @Jamie_Dewoody1

We’d like to reproduce this issue with a copy of your Roon database(s). At your convenience, please navigate to your Roon Database Location, zip up (compress) the “RoonServer” folder, and upload it here to our Database Uploader.

Thank you!

Benjamin,

Thank you for the reply.

  1. I can export to folder successfully. Export to Soundiiz does not work.
  2. All media is local .flac files.
  3. I tried my smallest playlist, which was 102 files and it did not complete.

I have uploaded the roonserver folder as requested. Since these uploads are pretty big, it would be a good idea to make uploads resumable. With typical home connections, they take hours. My first attempt failed at the 2/3 mark.
I do have one factoid, though its a shot in the dark and probably irrelevant. I had a number of .m3u playlists, some prior to roon. They were in my music directory: roon found them and played them fine. When roon introduced “playlist improvement” (a great feature), I integrated these m3u-derived playlists with roon playlists (by queuing up the playlists and then using roon to append them to existing playlists). A second comment is that, while I have used playlist export extensively, I hadn’t done so for a while until my recent attempts, so I can’t correlate the current problem with a specific roon build.

Hi @jim_hamilton,
You don’t need to upload the entire RoonServer folder. We only need the log folder inside of the RoonServer folder. That should upload fairly quickly.

good to know, but given the original, explicit instruction to upload the roonserver folder, I did so.

I took another look at @connor’s post. I was incorrect about what he was asking for. My apologies.

My exports also never complete.

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

Along with a couple of others, I reported a problem with excel export of roon playlists. Used to work for me, doesn’t now. At roon support request, I uploaded a large amount of information from my personal system to help debug. The original post was closed with no resolution given. (if roon wants to stick with a 14 day limit for replies to posts, at least support posts on possible bugs should be recorded somewhere. maybe there is a list of ‘known problems’ I haven’t seen).Anyways, I would appreciate an update. This is the original post:

Hi @jim_hamilton, I’ve reopened that topic and merged your new post.

Let’s see if @support can offer any more insight at this time.

Thanks @carl for reopening. I have a bit more information. In addition to being unable to do excel exports of playlists, I find I can no longer back up roon. These issues might be unrelated, but they have certain things in common:

  1. both worked flawlessly in my environment for years, and both failed recently (within last few weeks)
  2. both involve export of data from roon (In my case rock) to another machine
  3. neither seems to affect other roon operations: I can play, add music, edit metadata, create playlists, use ARC etc without error.
  4. neither restarting roon server or rebooting rock improves the problems.
  5. My last successful backup was Dec 15 2024. its accessible to the roon server and presumably could be used for a restore.

also possibly relevant, backups and playlist export in my case are done to separate machines: I backup onto my linux fileserver (samba and nfs, samba for roon). The playlist export is done to the desktop of my windows client (aside: would be nice to choose the export location instead of desktop only).
For completeness, a quick description of my setup. 3 machines: the rock server (intel NUC, see my original message for details), windows 10 client machine (dell laptop), fileserver containing all music files, backups, etc (pi 5 running raspbian). The networking is all cabled cat 6, a single subnet. no changes to the hardware setup since backups and playlist export were working. A simple ping test from the fileserver to the roon server looks good: 53 packets transmitted, 53 received, 0% packet loss, time 53233ms, rtt min/avg/max/mdev = 0.244/0.483/0.583/0.113 ms

Finally, since I have the roon server files mounted on my windows box, I did a tail on the active log while trying a backup. I’ll append a bit of that, showing a connection error on backup, even though roon plays normally. short excerpt:
*******Get-Content RoonServer_log.txt -Wait -Tail 30
02/03 19:02:22 Info: [7] [stats] 19399mb Virtual, 7110mb Physical, 3811mb Managed, 478 Handles, 69 Threads
02/03 19:02:31 Trace: [.NET ThreadPool Worker] [push2] exception thrown. restarting connection (Unable to connect to the remote server)
02/03 19:02:31 Trace: [.NET ThreadPool Worker] [push2] retrying connection in 49277ms
02/03 19:02:37 Info: [7] [stats] 19399mb Virtual, 7110mb Physical, 3811mb Managed, 478 Handles, 68 Threads
02/03 19:02:52 Info: [7] [stats] 19399mb Virtual, 7110mb Physical, 3813mb Managed, 476 Handles, 67 Threads
02/03 19:03:07 Info: [7] [stats] 19391mb Virtual, 7110mb Physical, 3813mb Managed, 478 Handles, 64 Threads
02/03 19:03:21 Debug: [.NET ThreadPool Worker] [easyhttp] [3755] GET to https://api.roonlabs.net/push-manager/1/connect returned after 441 ms, status code: 200, request body size: 0 B
02/03 19:03:21 Debug: [.NET ThreadPool Worker] [push2] push connector url received from push manager: ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
02/03 19:03:21 Trace: [.NET ThreadPool Worker] [push2] connecting to push2 connector at ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
02/03 19:03:22 Info: [7] [stats] 19391mb Virtual, 7110mb Physical, 3810mb Managed, 478 Handles, 67 Threads
02/03 19:03:31 Trace: [.NET ThreadPool Worker] [push2] exception thrown. restarting connection (Unable to connect to the remote server)
02/03 19:03:31 Trace: [.NET ThreadPool Worker] [push2] retrying connection in 61507ms
02/03 19:03:37 Info: [7] [stats] 19415mb Virtual, 7110mb Physical, 3811mb Managed, 478 Handles, 71 Threads
02/03 19:03:52 Info: [7] [stats] 19415mb Virtual, 7110mb Physical, 3813mb Managed, 476 Handles, 71 Threads
02/03 19:04:07 Info: [7] [stats] 19391mb Virtual, 7110mb Physical, 3813mb Managed, 478 Handles, 65 Threads
02/03 19:04:22 Info: [7] [stats] 19391mb Virtual, 7110mb Physical, 3099mb Managed, 476 Handles, 68 Threads
02/03 19:04:34 Debug: [.NET ThreadPool Worker] [easyhttp] [3756] GET to https://api.roonlabs.net/push-manager/1/connect returned after 910 ms, status code: 200, request body size: 0 B
02/03 19:04:34 Debug: [.NET ThreadPool Worker] [push2] push connector url received from push manager: ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
02/03 19:04:34 Trace: [.NET ThreadPool Worker] [push2] connecting to push2 connector at ws://push-connector-v2-1.prd-roonlabs-1.prd.roonlabs.net/
02/03 19:04:37 Info: [7] [stats] 19415mb Virtual, 7110mb Physical, 3099mb Managed, 481 Handles, 71 Threads
02/03 19:04:44 Trace: [.NET ThreadPool Worker] [push2] exception thrown. restarting connection (Unable to connect to the remote server)
02/03 19:04:44 Trace: [.NET ThreadPool Worker] [push2] retrying connection in 16107ms
02/03 19:04:52 Info: [7] [stats] 19415mb Virtual, 7110mb Physical, 3101mb Managed, 476 Handles, 69 Threads
02/03 19:05:01 Debug: [.NET ThreadPool Worker] [easyhttp] [3757] GET to https://api.roonlabs.net/push-manager/1/connect returned after 810 ms, status code: 200, request body size: 0 B
log excerpt:

Hi @jim_hamilton, @Jamie_Dewoody1,

Thank you for your longstanding patience here - we’ve reproduced the issue and identified the problem. There is a ticket with development in the pipeline for a fix. We’ll post here when it’s expected to merge into Early Access for testing and then to a public update.

Thank you!

Hi @Jamie_Dewoody1 ,

Not a problem, happy to help! Do note that it may take some time as this ticket makes its way through the development queue, your patience is greatly appreciated!

This is good and much appreciated. I’m an old software architect: I suspect this fix is not simple. I do feel that tracking IDs and somewhat regular updates for problems would provide a better user experience and instill confidence.

I used roon for years with no real issues, though of course with any complex software there are always different ideas about features and implementation. Lately though, I’ve had several problems I never had. On the off chance they are related to this problem, I’ll mention them.

  1. I’ve never had a problem with roon updates. For the most recent update, my android and windows clients updated smoothly as always, but my server won’t update. It appears stuck at Version 2.0 (build 1496) production. No error messages, I click on the “update” popup, and nothing happens. If I go to the OS “about” in the client the roon server says an update is available, shows the downloading message, then reports “there was an error checking for an update” (my roon configuration is documented in early messages in this thread: its a rock install on a intel NUC.)
  2. Backups (I have done these manually weekly for years) have suddenly stopped working. If I try a backup, after a minute or so I get “uh, oh, somethings not right”.
    yet playback has been flawless (from the same server where backups fail.)

Not meaning to complicate things, but it seems odd that this complex of 3 possibly related issues have occurred after years of problem-free use.