Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved PD Web service call Error

  1. How-to
0
Votes
Undo
  1. Mangutha
    Mangutha
  2. PowerBuilder
  3. Tuesday, 4 February 2020 18:01 PM UTC

Built web service with below transaction Object on window 10 machine which has SQL native client 11 Installed 

SQLCA.SERVERNAME = 'XXXXXX'
SQLCA.DATABASE = 'DDDDDDDDDD'
SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"
SQLCA.LogPass = '********'
SQLCA.LogId = "UUUUUUU"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PROVIDER='SQLNCLI11',DATASOURCE='DDDDDDD',PROVIDERSTRING='database=VVVVVVVVVVV'"

 

Deployed to windows server which also has  SQL native client 11 Installed 

getting below 

<?xml version="1.0" encoding="UTF-8"?>
<string xmlns="http://tempurl.org">DBMS SNC SQL Native Client(OLE DB) is not supported in your current installation.</string>

How to iterate a json result with many records as ...
How to send Exe parameters using batch file ?
Responses (3)
Mangutha
Mangutha Accepted Answer Pending Moderation
  1. Wednesday, 5 February 2020 16:36 PM UTC
  2. PowerBuilder
  3. # 1

when created 'exe' sample application with same connection it is working fine

Comment
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Wednesday, 5 February 2020 15:27 PM UTC
  2. PowerBuilder
  3. # 2

Hi

This message ">DBMS SNC SQL Native Client(OLE DB) is not supported in your current installation" implies that you have not installed the PB runtime component for SQL Server Native Client. How have you installed the PB Runtime?

You could try creating a simple PB exe to test the environment?

Just a thought.

David

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 5 February 2020 19:31 PM UTC
Hi David;

Mangutha is working on a Web Service and thus, an EXE would not be relevant.

Regards ... Chris
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Friday, 7 February 2020 10:05 AM UTC
Fair enough, I was thinking that would at least prove the SQL transport layer.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 February 2020 21:09 PM UTC
  2. PowerBuilder
  3. # 3

Hi Mangutha;

  I perform this same SS type DB Connect in my Web Services ...

WS Code:

 

WS Run-time Log:

 

Note: I am using SS 2019.

HTH

Regards ... Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 4 February 2020 21:30 PM UTC
SS2012 DB Client should be basically the same. Note that my DBParm syntax is different than yours.

Since yours has a "provider=" - are trying to use SNC through ODBC vs a true native SS connection?
  1. Helpful
Mangutha
  1. Mangutha
  2. Tuesday, 4 February 2020 22:06 PM UTC
Even after changing no luck Chris same message

is there a way to tell which client it is trying to use and which one it is not finding?
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 5 February 2020 19:11 PM UTC
FYI: I do not have (or need) ...

ProviderString=

DataSource=
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.