Forum Discussion
Strange Gateway issue
Here is how the issue occurs:
Have multiple CSV files in a folder. Link your gateway to the folder. At this point everything is happy.
Create a new query that does a merge on 2 or more of those CSV files. Now gateway is unhappy.
Update gateway to link to each file directly, gateway is happy again.
Its not a solution, but its a work around for right now.
Here is how the issue occurs:
Have multiple CSV files in a folder. Link your gateway to the folder. At this point everything is happy.
Create a new query that does a merge on 2 or more of those CSV files. Now gateway is unhappy.
Update gateway to link to each file directly, gateway is happy again.
Its not a solution, but its a work around for right now.
We ran into this same issue with a Windows 10 upgrade on the machine that houses our enterprise gateway this week. Prior to the upgrade, our organization used multiple models connected to various folders with CSV files in them and then merged them together in queries. We were able to schedule refreshes from these locations without a problem After the windows update, the gateway would not show as available for these models that contained merged queries.
Each indivisual source folder would be available to schedule refreshes in the gateway.
Each individual file would be available to schedule refreshes in the gateway.
But when a file was used in a merged query, the only way to have the gateway available to schedule refreshes was to directly link to each source file as a different connection in the gateway.
Please correct this! Our gateway is now filled with connections to individual files rather than the containing folders or sharepoint locations.