Forum Discussion

StevenR's avatar
StevenR
Brass Contributor
Oct 23, 2020

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...
brmmmm78's avatar
brmmmm78
Copper Contributor
Feb 23, 2021

dmidec 

 

It does seem to be working, however we did not disable UAC V on the entire server.

 

We did not install our sage200 client using the click once installer, but instead have a single installation location for all users. This meant that in theory we only need to create a "Sage200Desktop.exe.manifest" file and set the correct "requestedExecutionLevel", but found that Sage had already generated one but renamed it to "Sage200desktop.manifest.manifest" (this is from memory so it might be named something else). We simply renamed this file and restarted the WVD host, its worked ever since.

 

We are are not sure why Sage had chosen to rename the manifest file, but so far we have not noticed any unexpected behavior.

dmidec's avatar
dmidec
Copper Contributor
Feb 23, 2021

brmmmm78 Ah, that's useful. We too are running using the RDS installation method, so I'll look for the file!

  • nigelwebster's avatar
    nigelwebster
    Copper Contributor
    May 11, 2021

    dmidec 

     

    We have been following this forum and also the suggestions made within to get sage 200 working with FSLogix and WVD

     

    Our FSLOGIX is in azure premium storage and we have 2 servers that never have this issue. we have tried with and without UAC virtualisation and still receive the error writing the user.config file. as others have mentioned we see the folder structure be created for the user but just not the file. I could delete the file on 2 other servers and it immediately recreates it and runs with no issue yet other servers always present this error. 

     

    I am looking at this manifest file and have as instructed renamed the file and copied the entire install directory to a local drive c:\program files (x86)\sage200\   

     

    I run the Sage200desktop.exe application from here and still it will write this user.config file 

     

    I have edited the manifest file as follows

     

    <requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
    <!--
    UAC Manifest Options
    If you want to change the Windows User Account Control level replace the
    requestedExecutionLevel node with one of the following.

    <requestedExecutionLevel level="asInvoker" uiAccess="false" />
    <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
    <requestedExecutionLevel level="highestAvailable" uiAccess="false" />

    If you want to utilize File and Registry Virtualization for backward
    compatibility then delete the requestedExecutionLevel node.
    -->
    <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
    </requestedPrivileges>

     

    I presume the <!-- is the beginning of a comment-out statement and that I merely needed to take one of these statements and place it at the bottom. 

     

    Others have stated when you use require administrator that it changes the icon but I'm not seeing this behavior. 

     

    I am unsure if it is in fact even referring to the manifest file at all. 

     

    I'm puzzled as to why on some of my WVD servers I have no issue and yet others i always get the problem. 

     

    I have checked the .net versions and they are all correct. I have checked c++ and they also are correct

    the version of windows is all the same and yet some machines refuse to write to this location at all.

     

    Any clarity of any sort as to the specifics around the manifest file would be appreciated

     

  • dmidec's avatar
    dmidec
    Copper Contributor
    Mar 24, 2021
    I couldn't get UAC Virtualization to disable. There's a manifest file created when you install the per user client, called Sage200desktop.manifest.manifest which you just need to rename as above and stick it next to the Sage200Desktop.exe file. When setting this to 'RequireAdministrator' the Sage 200 icon would change to show the UAC badge but it wouldn't disable UAC Virtualization when run in 'AsInvolker'.

    The issue is very rare, so we're just living with it for now.
  • StevenR's avatar
    StevenR
    Brass Contributor
    Mar 24, 2021
    See following from further up, let us know if it fixes your issue too.
    --------------------------------
    brmmmm78 replied to StevenR
    ‎Feb 08 2021 12:55 AM - edited ‎Feb 08 2021 12:58 AM

    StevenR we think we have found a solution, it seems the problem is related to the UAC virtualization. If you disable the UAC virtualization and restart the host it seems to work.
  • KevHal's avatar
    KevHal
    Iron Contributor
    Mar 24, 2021
    Just dealing with this for a customer now. WVD, FSLogix and Sage 200. Getting intermittent error of ", Failed to save settings: Unable to Save config file c:\Users\%username%\AppData\Local\Sage_UK_Limited\Sage200Deesktop.exe_Strongname_.....\19.0.00\user.config"
    Stack: at system.Configuration.ClientSettingsStore.write

    Any type of solution for this?