• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Powerbuilder 2017 connecting to "MSS Microsoft SQL Server" issues

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

Resolved Powerbuilder 2017 connecting to "MSS Microsoft SQL Server" issues

  1. Issue
0
Votes
Undo
  1. David Beltz
    David Beltz
  2. PowerBuilder
  3. Friday, 8 December 2017 18:21 PM UTC

Hi All,

I just converted a power builder 9 app that connects to an "MSS Microsoft SQL Server" DB to power builder 2017 and now when i go to run the app it throws an error

"DBMS MSS Microsoft SQL Server is not supported in your current installation"

the app runs fine when i run it in PB9 i get no error or issues logging in.  

i have debugged the code side by side and the code is identical.

I am running it on a 64 bit windows 7 machine when i compile the app i compile in 32bit mode.  i am running the PB9 version on the same machine with no issues.

Any ideas?

thanks in advance

  1. Build
  2. SQL
  3. Server
Powerbuilder with Oracle 18c using ODBC
PowerBuilder 2017 R2 Web service Consuming Error
Responses (5)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Friday, 8 December 2017 18:51 PM UTC
  2. PowerBuilder
  3. # 1

Hi David,

PB 2017 uses the SQL Native Client (SNC).

Cheers,

Marco

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 8 December 2017 19:25 PM UTC
  2. PowerBuilder
  3. # 2

Hi David;

  That would be expected as the old PB "MSS" interface from the Sybase days is no longer supported or supplied with newer versions of PowerBuilder 10.5 and higher. Instead, you will have to change your Transaction Object, as follows:

// Old - remove

  • SQLCA.DBMS = "MSS" 

// Use instead ...

  • SQLCA.DBMS = "SNC"              // - OR -
  • SQLCA.DBMS = "ODBC"           // - OR -
  • SQLCA.DBMS = "OLE-DB"        // - OR -
  • SQLCA.DBMS = "ADO.NET"      // - OR -
  • SQLCA.DBMS = "JDBC" 

As Marco commented earlier - the equivalent of MSS is now SNC. Here is an example of my SS2017 connection code ...

// Profile SS 2017
SQLCA.DBMS = "SNC"
SQLCA.LogPass = <**********>
SQLCA.ServerName = "SS2017"
SQLCA.LogId = "Chris"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Database='Chris',Provider='SQLNCLI11',AppName='PB2017',Host='STD-CHRIS',TimeOut=5,TrustedConnection=1,TrimSpaces=1"

 

HTH

Regards ... Chris

 

Comment
There are no comments made yet.
Jon Stoller
Jon Stoller Accepted Answer Pending Moderation
  1. Friday, 8 December 2017 19:54 PM UTC
  2. PowerBuilder
  3. # 3
I had the same problem. I have it working now. I am connecting with "OLE Microsoft OLE DB" My connection string in the code is: pt_sqlca.dbparm = "PROVIDER='SQLOLEDB',DATASOURCE='" + pt_sqlca.Servername + "',PROVIDERSTRING='DATABASE="+pt_sqlca.Database+ "',PBTrimCharColumns='Yes'" connect using pt_sqlca;
Comment
There are no comments made yet.
David Beltz
David Beltz Accepted Answer Pending Moderation
  1. Monday, 11 December 2017 12:44 PM UTC
  2. PowerBuilder
  3. # 4

Thanks guys i will give these a shot!!

Really appreciate the help

Comment
There are no comments made yet.
Jessie Cesar
Jessie Cesar Accepted Answer Pending Moderation
  1. Thursday, 30 January 2020 04:32 AM UTC
  2. PowerBuilder
  3. # 5

All you have to do is to change the ntwdblib.dll compatible to the operating system that you are running. If it is 64 bit, change or add ntwdblib.dll in syswow64

Comment
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.