Share via


Error trying to use On-Premise Gateway

Question

Thursday, April 27, 2017 2:29 PM

When I try to connect to an external database, I'm getting the following error...

Failed to create connection for connection id '/subscriptions/f83428d1-7298-4a6b-99c2-c3b3d45c2404/resourceGroups/Piv_Integration/providers/Microsoft.Web/connections/sql'. Connection gateway operation failed with code 'DM_GWPipeline_Client_GatewayUnreachable'.

All replies (7)

Thursday, April 27, 2017 11:23 PM

Hi,

Can you look at the On premise Data Gateway logs at below location 

C:\Users\PBIEgwService\AppData\Local\Microsoft\on-premises data gateway\Gateway*.log

Have you created OPDG in azure after installation it on on-premise server . I think the problem you are facing is more related to connecting to the OPDG. 

List us the steps you are following and hopefully we can help you in better way.

Thanks

Abhishek 

If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply


Friday, April 28, 2017 12:53 PM

The log is repeating the same information...

DM.EnterpriseGateway Information: 0 : 2017-04-28T12:46:38.4154074Z DM.EnterpriseGateway 3819552b-019d-4b23-86dd-c0ac9560c4cb 22490359-7271-4dd7-a084-be9d59a3596e MGPP 00000000-0000-0000-0000-000000000000 E8162E5D [DM.Pipeline.Common] Pool cleaner connections removed: 0, count: 0, buckets: 0

The OPDG was created and it has a status of 'Configured' for Logic Apps. I followed the directions from https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-gateway


Friday, April 28, 2017 5:40 PM

Anyone have any ideas?


Saturday, April 29, 2017 9:47 AM

Hi Joe,

Since you're short of ideas found this link with some options to troubleshoot this kind of error. It is not specific to Logic apps, but might help.

I would suggest confirming that the service is running and maybe restarting the service as first steps. I know, feels like support talking, but actually helped me a couple of times, specially if you running this on a VM that goes into saved state on a regular basis.

Hope this helps, Wagner.


Thursday, May 4, 2017 1:25 AM

Hi Joe,

Did any of the suggestions helped?

Cheers, Wagner.


Thursday, May 4, 2017 1:42 AM

Hi,

Silly question but is your logic app and OPDG is in the same region . I do not see any exception in your  OPDG  logs .Information is more  about cleaning connection pool 

Thanks

Abhishek

If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply


Monday, May 15, 2017 5:04 PM

Previously, you had to use the same region for both your gateway resource and logic app in the Azure portal. But with the  on-premises data gateway now generally available, you can use different locations for your gateway resource and logic app. During gateway installation, you can now also select the location for the gateway cloud service that you use to route queries and results between your logic app and your on-premises data source.

Note: Your gateway resource location must now match the gateway cloud service location that you select during gateway installation. Otherwise, you won't see your installed gateways in the Installation list.

If you already installed a gateway, but want to use a gateway in a different location, you can use the latest installer to set up a new gateway in the location that you want, but you can't change the location for an existing gateway.

For any other details that might help you, check out these articles:

Install the on-premises data gateway for Azure Logic Apps

Access data on premises from Azure Logic Apps

Esther Fan | Azure Logic Apps | If a post answers your question, please mark it as the answer. Thanks!