Hey all! This just started randomly today - trying to update two REs and then it sits on "Unpacking" for ages and then gives a File System Error. Any clues? Thanks!
Windows 10.
Reason Companion unable to update REs
If there's enough free space it could be a bad sector on the HDD/SSD. Does it still occur after a full power cycle?
-
TheGrandmother
- Posts: 3
- Joined: 01 Sep 2021
Howdy!
Does it only happen when updating REs? Did you have Reason on whilst you were downloading the update?
My spider sense tells me that you Reason was running and had a lock on the RE files and companion failed to deal with that in a sensible way.
Does it only happen when updating REs? Did you have Reason on whilst you were downloading the update?
My spider sense tells me that you Reason was running and had a lock on the RE files and companion failed to deal with that in a sensible way.
This has just started happening on my system as well. However, all cases of the problem have eventually resolved themselves during further attempts while I have been writing this, except for updating Fritz to hi-res.
In case others experiencing it want to compare notes, it has happened in all of the following ways:
- While Reason is running and while it's not running.
- When aiming to download a new Rack Extension, upgrade an existing one, or upgrading to high-res.
- When attempting to download using Authorizer prior to using the Companion to actually install, and when attempting without the Authorizer step.
- Temporarily with some Rack Extensions but persistently without resolution with others (ie there are some I have not been able to download or update at all despite trying multiple times in multiple ways).
It has involved the following REs:
- Pipeline Pressure Control, ZPlane Morphing Filter, Fritz*, SMFX Dual Saturator - initially unable to download, then was later able.
- * But Fritz is unable to upgrade to hi-res.
- Launcheon - initial trouble updating, then later updated automatically.
In all cases of a problem it's been at the "Unpacking" stage, which has stalled and then resulted in a "File System Error".
Three other possibly key points:
- My PC is powerful but old.
- I use the Mklink approach to store Rack Extensions on a non-C drive on my PC.
- I recently upgraded Reason to 12.5d29, the new VST3-capable version, and the problem seems to have occurred only since then.
In case others experiencing it want to compare notes, it has happened in all of the following ways:
- While Reason is running and while it's not running.
- When aiming to download a new Rack Extension, upgrade an existing one, or upgrading to high-res.
- When attempting to download using Authorizer prior to using the Companion to actually install, and when attempting without the Authorizer step.
- Temporarily with some Rack Extensions but persistently without resolution with others (ie there are some I have not been able to download or update at all despite trying multiple times in multiple ways).
It has involved the following REs:
- Pipeline Pressure Control, ZPlane Morphing Filter, Fritz*, SMFX Dual Saturator - initially unable to download, then was later able.
- * But Fritz is unable to upgrade to hi-res.
- Launcheon - initial trouble updating, then later updated automatically.
In all cases of a problem it's been at the "Unpacking" stage, which has stalled and then resulted in a "File System Error".
Three other possibly key points:
- My PC is powerful but old.
- I use the Mklink approach to store Rack Extensions on a non-C drive on my PC.
- I recently upgraded Reason to 12.5d29, the new VST3-capable version, and the problem seems to have occurred only since then.
-
TheGrandmother
- Posts: 3
- Joined: 01 Sep 2021
Hmmmm.... Okay this super strange and incredibly annoying. v1.9.9 should specifically address a bunch of random file system related errors. But Windows filesystems are annoying and the code for handling RE downloads is complicated.
I am still 8% certain that Reason is leaving lockfiles laying around for some reason. One thing that you could try to do is to simply just remove the RE folder from the RackExtensions folder and re download it again.
There isn't really anything I can do without logs and there aren't anything in our Error monitoring systems that is helpfull.
Could you all who have experienced this create support tickets about this, add the logs which live in C:\Users\<username>\AppData\Roaming\Reason+ Companion\logs (both the main and renderer logs) and attach a link to this thread.
Lots of thanks for all the feedback!
I am still 8% certain that Reason is leaving lockfiles laying around for some reason. One thing that you could try to do is to simply just remove the RE folder from the RackExtensions folder and re download it again.
There isn't really anything I can do without logs and there aren't anything in our Error monitoring systems that is helpfull.
Could you all who have experienced this create support tickets about this, add the logs which live in C:\Users\<username>\AppData\Roaming\Reason+ Companion\logs (both the main and renderer logs) and attach a link to this thread.
Lots of thanks for all the feedback!
One more thing:
I also have "moved" the Packs-Folder via mklink to another location (already months ago, same time as I moved the RackExtensions-folder) > Installing new soundpacks works without any problems!
Packs-Folder: Moved from its default location on C: to >> L:\Reason\Packs
RackExtensions-Folder: Moved from its default location on C: to >> L:\Reason\RackExtensions
Matthias
I also have "moved" the Packs-Folder via mklink to another location (already months ago, same time as I moved the RackExtensions-folder) > Installing new soundpacks works without any problems!
Packs-Folder: Moved from its default location on C: to >> L:\Reason\Packs
RackExtensions-Folder: Moved from its default location on C: to >> L:\Reason\RackExtensions
Matthias
-
pluckshimmer
- Posts: 2
- Joined: 21 Dec 2022
... same probs here!
i did a complete uninstall and reinstall of all reason-stuff... also checked win with chkdsk, winupdate, dism, sfc... no errors in my system-health!
did a ticket ... now waiting...
i did a complete uninstall and reinstall of all reason-stuff... also checked win with chkdsk, winupdate, dism, sfc... no errors in my system-health!
did a ticket ... now waiting...
After going to C:\Users\[User]\AppData\Roaming\Propellerhead Software\Downloads, deleting the PART file for Fritz, then uninstalling Fritz using the Companion, then re-installing using ONLY the Authorizer, Fritz was successfully installed in hi-res. I don't necessarily recommend doing this, because I don't know if any aspect of this approach was the solution, since all other instances of this problem with other devices seem to have eventually resolved themselves randomly anyway.
All instances of this problem for me are resolved (for now, at least), as I have just mentioned in a reply to my own first post on this topic, but I just thought I'd mention anyway that my system doesn't have a "Reason+ Companion" folder in the location you have mentioned here. (I do have Reason+). The closest thing to it is the general Reason logs folder at C:\Users\[username]\AppData\Roaming\Propellerhead Software\Reason\Logs.TheGrandmother wrote: ↑21 Dec 2022Could you all who have experienced this create support tickets about this, add the logs which live in C:\Users\<username>\AppData\Roaming\Reason+ Companion\logs (both the main and renderer logs) and attach a link to this thread.
Lots of thanks for all the feedback!
I encountered this on updating the Receive Notes RE to version 1.3.0 via R+ Companion.
Using Authorizer (via Sync All from the website) the RE got updated without any trouble. As I have not updated R12 to 12.5 yet, I suppose it only has to do with the recent update from R+ Companion.
I've also relocated the RE and R+ packs folder to another HDD using the mklink trick.
Using Authorizer (via Sync All from the website) the RE got updated without any trouble. As I have not updated R12 to 12.5 yet, I suppose it only has to do with the recent update from R+ Companion.
I've also relocated the RE and R+ packs folder to another HDD using the mklink trick.
-
pluckshimmer
- Posts: 2
- Joined: 21 Dec 2022
... i found a "dirty" solution:
while companion has downloaded the two problem-files and hangs for some seconds, i copied the two downloaded tmp-files to another tmp location, unpacked them with 7z , renamed the folders and copied them to the rackextension folder. you can find the right foldernames in the log-file in "C:\Users\"YOURNAME"\AppData\Roaming\Reason+ Companion\logs\main.log"
works for me at the moment and i can open my songs again.
while companion has downloaded the two problem-files and hangs for some seconds, i copied the two downloaded tmp-files to another tmp location, unpacked them with 7z , renamed the folders and copied them to the rackextension folder. you can find the right foldernames in the log-file in "C:\Users\"YOURNAME"\AppData\Roaming\Reason+ Companion\logs\main.log"
works for me at the moment and i can open my songs again.
-
TheGrandmother
- Posts: 3
- Joined: 01 Sep 2021
Hoowdy!
We have identified the problem and it is silly. We will release a fixed version soon but in the meantime you can use version 1.9.8
https://s3-eu-north-1.amazonaws.com/ph- ... .8-win.exe
We changed the companion to use the systems tempfolder when downloading to prevent some other bugs, but it turns out that we were doing some moving of files and on windows that creates links and cannot be done across devices. I thought that I had changed the moves to copy the files instead but I had forgotten a place >.<
We have identified the problem and it is silly. We will release a fixed version soon but in the meantime you can use version 1.9.8
https://s3-eu-north-1.amazonaws.com/ph- ... .8-win.exe
We changed the companion to use the systems tempfolder when downloading to prevent some other bugs, but it turns out that we were doing some moving of files and on windows that creates links and cannot be done across devices. I thought that I had changed the moves to copy the files instead but I had forgotten a place >.<
Thank you very much!
On this topic, since several people have brought up creating symlinks for REs and moving REs to another location... Any chance that might ever be a natively supported option?
-
- Information
-
Who is online
Users browsing this forum: nebraskafire, spacepluk and 14 guests
Share and download patches!
Join ReasonTalk on Slack!