Forum Discussion
Intermitent issues writing files to Local_Username redirection.xml
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
27 Replies
Hi all, I thought that I would just resurrect this to see how others are getting on with Sage 200 in AVD. We are still suffering strange and intermittent issues with general reliability problems. Have resorted currently to re-imaging all hosts every day which does seem to help but just interested to hear how others' experiences are.
Charlie155 We too are facing similar issue after moving sage 200 to AVD. Have dropped in Sage200Desktop.manifest file this morning having previously tried it with it being called Sage200Desktop.exe.manifest. Which having looked at the per user installation didn't look correct. To add we have not edited this manifest file just yet, waiting for anymore errors to appear.
- To confirm so far so good with Sage200Desktop.manifest, no errors since.
- Hi all, yes if you disable UAC Virtualisation, then this resolves the issues, have been running Sage 200 since early February with this setting disabled and the issues previously experienced have not re-occurred. thanks
We are using the local Program Files (not click-to-run) version and have updated the manifest file but are still experiencing the issue for some users.
It's really odd - is anyone else continuing to have problems?
- I actually reduced my user count limit to 2 per host and haven't seen the issue since. Speaking with our Sage support vendor, they mentioned something about this, so it lines up I guess.
accounts2021 Hi, unfortunately I haven't I hit a brick wall of support from vendor as Sage do not support VDI environments, however that appears to be more of an issue with using "ClickOnce" installers as thats a limitation of that and until that changes.
What I haven't tested mostly due to time, is mounting the FSLogix accounts in Azure Files rather than direct on a fileserver in azure.
With another WVD deployment I ran into performance issues/limitations of locating them on a fileserver then the bottleneck of access becomes the singulare fileserver, whereas if they were in Azure Files it is far higher and the bottleneck becomes the higher spec'd WVD that is trying to connect to it.
I have another project to deploy and will be using this method instead hopefully with better results.
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:
https://stackoverflow.com/questions/64356026/applicationsettingsbase-save-unable-to-save-config-to-file
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.
https://stackoverflow.com/questions/20946627/how-to-work-around-localfilesettingsprovider-requiring-full-control-ownerrights
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
