When trying to select a DB data path in the configuration wizard, the error message appears: "Enumerable available media failed for Server 'servername'."

Version 1


    When trying to select a DB data path in the configuration wizard, the below error message appears:

    "Enumerable available media failed for Server 'servername'."

    For example, when attempting to pick a "Location" after clicking "Re-Create and Load HEAT Application":



    Using SQL authentication for the DB causes the "NT AUTHORITY\ANONYMOUS LOGON" account to be used to access the actual backup/data folders on the SQL server. This error indicates that is not authorized in the customer's system.

    Because this is imposed by the means through which SQL authenticated accounts access a Windows filesystem, one of two resolutions must be taken. Either the use of an appropriate domain account would need to be employed (and that account granted appropriate DBO permissions on the HEAT databases, as well as granted permissions to the specified folder), or the anonymous access must be granted. 

    Granting anonymous access may require alteration of many server configurations. Although this is ultimately an environmental factor needing resolution, a recent StackOverflow article provides the following details, to give a sense of what may need checked:

    This may be caused by what's called a "double-hop" issue, which is where the server is not being trusted to pass the client's credentials on to another box (hop 1 is the credentials to the IIS box, hop 2 is from the IIS box to the SQL Server).

    "When you're logged directly into the server, the second hop doesn't need to take place since it's just passing credentials directly from the client machine (the IIS server in this scenario) directly to the SQL Server. Likewise, if the SQL Server lived on the IIS box, you wouldn't have this error either, since the client would only be making the one request to a box that could share the credentials with both IIS and SQL Server.

    There are quite a few steps required to get the delegation to work, such as trusting the servers for delegation, creating SPNs and making sure that other proper permissions are given to the account that IIS is using to run the web site. There is a technet article that can help take you through a lot of the required steps here: http://blogs.technet.com/b/taraj/archive/2009/01/29/checklist-for-double-hop-issues-iis-and-sql-server.aspx"