CPI Connectivity to Microsft SQL Server using Open Connectors

[shreya91]

Hi Experts,

I am working on building an integration from SAP C4C to Microsoft SQL system hosted on Azure platform via CPI.

Since we do not have a JDBC adapter to post data to a database, I tried using Open Connectors as an alternative route. Below is the approach followed.

Step1: A database is already present in MS SQL with a Table created.

Step 2: Build an Iflow from CPI to connect to SQL. For this, I created a trial CPI subaccount for Europe Region to use Open connector for MSSQL & subscribed to the Open Connectors Service. All the necessary details such as Hostname, Port, Database name, Username and password were available for adding in the MSSQL Connectors Authenticate instance section.

Step 3: Launch the Open Connector Service & Create an Instance connection. But I am unable to connect to the SQL system and the error is as below-
"Failed to authenticate with provider during provisioning. Please check your credentials or instance configuration"

The firewall rules have been created within Client Network using the SAP recommended Port, Protocol & IP Ranges.
I have tried to connect using separately the host name as well as the IP but both connection failed with same error. Inside the client network I could reach the concerned Host & IP using ping, telnet & tracert from command prompt.

Please help me with some inputs on how to have a connection eshtablished from CPI to Microsoft Azure MSSQL system.

[ankit_mishra09]

Hi Shreya,

Were you able to resolve this error? If so, what were the steps & how was this resolved? I'm getting the same error while creating an instance for Snowflake DB.

Error: "Failed to authenticate with provider during provisioning. Please check your credentials or instance configuration"

[Dushyant]

Hello Ankit, I am too getting same error. Were you able to resolve this ?

[ankit_mishra09]

Hi Dushyant,

For Snowflake there were multiple steps done.

1. The user provided must have necessary roles/access to the DB/SCHME/WAREHOUSE/etc. This was taken care by Snowflake team.

2. While adding the instance in Open Connector I had additionally added the table names which were to be accessed under optional parameters. As per discussion with Snowflake team while creating the instance it was taking too long to access the whole data & thus the request to create instance was getting timed out.

So, please check above two steps, it worked for me.

Thanks

Ankit