Intermitent issues writing files to Local_Username redirection.xml

Occasional Contributor

having an issue with Sage 200 trying to write a file into FSLogix profile disk so moved file using redirection.xml to local_username\appdata\local\ and it has successfully writes the folder structure there however intermittently it will fail on one file stopping the program open, logging users off and onto a different VM intermittently works, not sure if its an FSLogix issue or a WVD issue as dont have the issue on standard rdp with old UPD's or on on prem windows 10 machines. anyone seen similar

3 Replies

@StevenR we are also experiencing the same issue, we are using WVD and FSLogix but not the redirections.xml. We have found that the issue moves between users after reboots and after using process monitor we established the issue arises when Sage/.NET attempts to rename/merge the user.config. This stackoverflow displays the same issues but using Citrix:


His work around was to not use FSLogix, but this is far from ideal. Hope you find the extra information useful (or at least interesting).


This article suggests a development solution, which I am going to forward to our Sage support tomorrow. Fingers crossed they can ask Sage to implement a fix.







Hi @brmmmm78  , well all the redirections didn't help basically "clickonce" installers are not supported on VDI's/Roaming profiles and since Sage use that then there in lies the issue, Unless Sage are prepared to change to another type of installer this issue wont go away.


Basically FSLogix's uses a driver to obscure the path of where config file actually exists and whether you exclude from the disk or not .net still needs to run through that driver, Perhaps FSLogix may improve that driver over time but right now its doesn't work 100% of the time.


However I would be very interested to here how you get on with your Sage support, as for now I have had to move the sage user away from WVD for now and hope this is resolved later on. Hope you have more luck

Hi @StevenR, Im not going to hold my breath with Sage, but our accounts team is quite small so we are just join to create a host-pool with a single host and disable FXLogix for the sage users. Not ideal but a solution for the time being.


Thanks for the info and good luck to you also.