none
FSLogix Eventually stops loading VHDs or Importing the Registry RRS feed

  • Question

  • We have run into an issue where a server in our multi Win 2016 RDS environment will stop loading VHDs with an "Error set to 121" in our FSLogix logs and give the user a temp profile. Or a user will login and not get a temp profile (the login simply hangs) and FSLogix reports that their Registry could not be imported "ImportProfileRegistry failure". The server never recovers and becomes unusable as an RDS server, since it cannot load Profiles.

    This has happened to every server in the environment at some point and we have rebuilt them all from scratch. It is very strange because it will not affect every server simultaneously. The VHD themselves are hosted on 2016 file server.

    Email support from FSLogix is frustratingly slow and unresponsive, and we have taken to basically weekly BMR's on at least one server. Has anyone run into any issue like this before with VHDs/RegImport? 

    Friday, November 22, 2019 3:42 PM

All replies

  • We have run into an issue where a server in our multi Win 2016 RDS environment will stop loading VHDs with an "Error set to 121" in our FSLogix logs and give the user a temp profile. Or a user will login and not get a temp profile (the login simply hangs) and FSLogix reports that their Registry could not be imported "ImportProfileRegistry failure". The server never recovers and becomes unusable as an RDS server, since it cannot load Profiles.

    This has happened to every server in the environment at some point and we have rebuilt them all from scratch. It is very strange because it will not affect every server simultaneously. The VHD themselves are hosted on 2016 file server.

    Email support from FSLogix is frustratingly slow and unresponsive, and we have taken to basically weekly BMR's on at least one server. Has anyone run into any issue like this before with VHDs/RegImport? 

    I would like to see some logs, or a manually initiated crash dump from a server showing this behavior.  A crash dump is likely the fastest way to diagnose, but some logs for context would help as well.  It sounds like a lock of some sort on the registry, and we would need to see why.  The 121 is a timeout acquiring a lock.  Does a reboot of the server clean it up?  Are there any other errors in the log before the load completes?  Are you configured to use Profiles, Office Containers or both?


    • Edited by Brian Mann1 Tuesday, November 26, 2019 1:16 AM
    Tuesday, November 26, 2019 1:16 AM