Sonic-pi cannot be loaded after installation

[spdqa]

Getting gets Critical Error - Could not boot Sonic Pi - Server.

Sonic Pi Boot Error Report

System Information

• Sonic Pi version: 3.1.0
• OS: Windows 10

GUI Log

C:\Users\xxxxxx.xxxxx\.sonic-pi\log\gui.log

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] -    port: 4558 [OK]
[GUI] - Server OSC listen port 4557
[GUI] -    port: 4557 [OK]
[GUI] - Server incoming OSC cues port 4559
[GUI] -    port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] -    port: 4556 [OK]
[GUI] - Server OSC out port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Scsynth send port 4556
[GUI] - Erlang router port 4560
[GUI] -    port: 4560 [OK]
[GUI] - OSC MIDI out port 4561
[GUI] -    port: 4561 [OK]
[GUI] - OSC MIDI in port 4562
[GUI] -    port: 4562 [OK]
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 10668
[GUI] - waiting for Sonic Pi Server to boot...
.
[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 No such file or directory @ rb_sysopen - H:/.sonic-pi/log//osc_cues.log
 ["C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `open'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'", "C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:106:in `block (2 levels) in included'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'", "C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'"]
[GUI] - UDP OSC Server no longer listening
...........................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...

Server Errors

C:\Users\xxxxxx.xxxxx\.sonic-pi\log\server-errors.log

Unable to create H:/.sonic-pi due to permissions errors
Unable to create H:/.sonic-pi/store/default/ due to permissions errors
Unable to create H:/.sonic-pi/log/ due to permissions errors
Unable to create H:/.sonic-pi/store/default/cached_samples due to permissions errors
Unable to open log file H:/.sonic-pi/log//debug.log
Unable to open process log file H:/.sonic-pi/log//processes.log

Server Output

C:\Users\xxxxxx.xxxxx\.sonic-pi\log\server-output.log

Sonic Pi server booting...
Using protocol: udp
Detecting port numbers...
Send port: 4558
Listen port: 4557
  - OK
Scsynth port: 4556
  - OK
Scsynth send port: 4556
  - OK
OSC cues port: 4559
  - OK
Erlang port: 4560
  - OK
OSC MIDI out port: 4561
  - OK
OSC MIDI in port: 4562
  - OK
Failed to start server: No such file or directory @ rb_sysopen - H:/.sonic-pi/log//osc_cues.log
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `open'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/runtime.rb:1288:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/ruby/lib/sonicpi/lang/sound.rb:106:in `block (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/ruby/bin/sonic-pi-server.rb:177:in `<main>'
Server is exiting.
Shutting down GUI...
Goodbye :-)

Scsynth Output

C:\Users\xxxxxx.xxxxx\.sonic-pi\log\scsynth.log

Process Log

C:\Users\xxxxxx.xxxxx\.sonic-pi\log\processes.log

[SunderB]

Hmm, its trying to make a directory at the root of your H drive, I'm not sure whether it should do that. I think it should only make a folder at C:\Users\User\.sonic-pi, but I may be wrong.
Maybe try the portable Windows version?

[SunderB]

Or, maybe check what the environment variable SONIC_PI_HOME is set to. You can do this by opening the Command Prompt (press Win+R, type cmd and press enter), and typing echo %SONIC_PI_ROOT%.

It should be empty or be set to your home folder. If it isn't, I think you can set it by typing this command into the Command Prompt: set "SONIC_PI_ROOT=[Your User Folder]", where [Your User Folder] is the path to your home folder.

[muskyhippo]

I have the same error, but my error indicates it is the F: drive instead of H:. It's really strange because I do have an F: drive, but it is an invalid drive because I am not currently connected to the network which gives me access to that drive. I tried setting the SONIC_PI_ROOT variable as described:
C:\Windows\system32>set "SONIC_PI_ROOT=C:\Users\musky\Documents"
C:\Windows\system32>echo %SONIC_PI_ROOT%
C:\Users\musky\Documents

but then it just hangs on the splash screen.
This is for version 3.1.0 portable of Sonic Pi. Does anyone know how to get past this issue?

[samaaron]

Hi @muskyhippo - sorry you’re having issues!

It’s hard to know what’s specifically going wrong with your setup without seeing a copy of your logs. Would it be possible to share them? They should appear after the splash screen has hung for a while or can be located within ~/.sonic-pi/logs wheee ~ should be your home dir or the directory pointed to by the sonic pi root variable.

[micahpaul]

Look in regedit to see if your HOMEDRIVE key is set to 'H:'

Mine was. I deleted the HOMEDRIVE reg key/value of 'H:', and voila! No more problem.

[micahpaul]

Turns out my network policy had an old script that refreshed HOMEDRIVE to H: on restart. So it would work until restart, then back to the same error.

The problem is that H: no longer exists in my network environment, and the admin who handled the config isn't available to fix it right now.

So here's another workaround:

1. Create a folder like c:\tmp
2. open a cmd prompt and run this command:
   subst h: c:\tmp

Now your H: should be mapped to c:\tmp. No more error!

[micahpaul]

@samaaron I think this issue comes of using the HOMEDRIVE variable in Windows without checking to see if it points to a valid location.

[samaaron]

We have completely overhauled the building and booting systems in the recently released v4 of Sonic Pi:

https://github.com/sonic-pi-net/sonic-pi/releases

Please give that a try and feel free to create a new issue if you're still having problems.