Personal Gateway Custom Connector Error

[hstiles]

Hi,

Can anybody point me in a direction for resolving our issue.

We have a custom connector which works fine through desktop.

We have setup personal gateway (as only personal gateway is supported for custom connectors at the moment)

Gateway works ok with SQL connections.

However with our custom connector, which has 'Basic' authentication we continually receive this message.

'Your data source can't be refreshed because the credentials are invalid. Please update your credentials and try again'

Once we have updated our credentials we recieve this error:

Your data source can't be refreshed because the credentials are invalid. Please update your credentials and try again.

Failed to update data source credentials: Credentials are required to connect to the XXXXXX source. (Source at {"baseUrl":"{\"baseUrl\":\"http:\\\/\\\/V-XXXX-B\\\/XXXX\\\/cmst-bor\"}"}.)Hide details
Activity ID: 9940b337-5ff3-4cd6-a733-1726be7cd6a4
Request ID: 1019f7ba-e9d9-d317-eb32-440606136d1b
Status code: 400
Time: Wed Jun 27 2018 14:24:46 GMT+0100 (British Summer Time)
Version: 13.0.5702.156
Cluster URI: https://wabi-uk-south-redirect.analysis.windows.net

Any ideas?

HS

[ankly1993]

Personal gateway is 64bit - If your machine is 32bit, you will not be able to install the personal gateway. Your operating system needs to be 64bit. You will need to install a 64bit version of Windows (Live Net Tv for PC), or install the personal gateway on a 64bit machine.

[hstiles]

A quick update in case anyone else has this problem.

We think we found the problem which is the base URL, the base URL path seems to be created with double encoding (see my post below) so to 'work around' this issue we hardoded the url in the .mez file for now, which works with 'Basic' authentication.

This approacj does present a future problem if you need to be more flexible and point at different URL's.

We think this is a bug.

[tictactic]

A lot of issues can surface when the gateway version is out of date. It is a good general practice to make sure you are on the latest version. If you haven't updated the gateway for a month or longer, you may want to consider installing the latest version of (iMessage for Windows) the gateway and see if you can reproduce the issue.

[hstiles]

Thanks for the reply.

We are using the latest release of the Gateway.

Howard