I think there may be a fundamental problem with the enteprise gateway. I have setup a brand new gateway and tried to create a datasource for the following URL's https://www.google.com.au/?q=1 ...
Not sure if this is the same issue, please forgive me if this is not the right place to post. We're getting the same error, but the scenario is a little different: we have a SQL Server database that is currently in process of moving from development to production, and is now in testing on the production instance of SQL Server, preparatory to go-live. It still exists on the development server too. The database name is the same on both servers, but the server names are quite different. In this case we're running against the default instance on both servers. It looks to me as if the only thing the cloud service looks at is the database name, ignoring the server/instance name. Can this be correct? If so, can the team fix things so that distinct database instances on distinct servers can be recognized as distinct data sources? Thanks.