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

Resolved SNC SQL Native Client Trace Option

  1. Issue
0
Votes
Undo
  1. Richard Hennessy
    Richard Hennessy
  2. PowerBuilder
  3. Thursday, 22 March 2018 20:56 PM UTC

Hi,

Using PowerBuilder 2017 R2

 

I am connecting to SQL Server 2012 using 2012 Native Client and DBMS=SNC SQL Native Client(OLE DB).

 

All works as expected but when I put Trace to start tracing using

DBMS=Trace SNC SQL Native Client(OLE DB)

when I try and connect I get the following error message.

DBMS SQL NATIVE CLIENT(OLE DB) is not supported in your current installation

 

This occurs when in PowerBuilder and also when I run the 64-bit and 32-bit executables generated from my PowerBuilder application.

My application can also connect to Oracle databases using DBMS=ORA Oracle and database trace works fine in here.

 

Does anyone know what I am doing wrong?

Thanks in advance.

Richard

  1. Client
PowerBuilder service application (Windows service)
powerscript editor error messages - not getting th...
Responses (3)
Alfredo Aldama
Alfredo Aldama Accepted Answer Pending Moderation
  1. Friday, 23 March 2018 00:03 AM UTC
  2. PowerBuilder
  3. # 1

Hi,

En teoria para 32 bits debe de funcionar el Trace, ya que este está soportado en el "Runtime Packager", sin embargo para 64 este no esta soportado., Ejecuta el runtime packager de la version de powerbuilder donde te ocurrio el error. Observa  si la opcion OLE DB database driver  está en gris o en negro.

Saludos !

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 23 March 2018 13:23 PM UTC
  2. PowerBuilder
  3. # 2

Hi Richard;

     FYI ...   This normally occurs when a PB App (or running from the IDE for that matter) is missing the DB Tracing support DLL - "PBTRAnnn.DLL" ( where nnn is your release number). In your case for PB 2017, that would be PBTRA170.DLL - which should be in the PB "Shared" folder. Also note that there is 32 bit and 64 bit version of that DLL. So you need to have the correct bitness DLL deployed with your PB App EXE's that matches its bitness for this feature to work.

Could this be your issue?

Regards ... Chris

Comment
Richard Hennessy
  1. Richard Hennessy
  2. Monday, 26 March 2018 13:53 PM UTC
Hi Chris,



The tracing DLL's (pbtra170.DLL) are in the expected 32/64-bit locatiosn and those 2 locatison are in my PATH. Similarly PBSNC170.DLL are in the correct locations also



 



 



C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbtra170.DLL

C:\Program Files (x86)\Appeon\Shared\PowerBuilder\x64\pbtra170.DLL

C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSNC170.DLL

C:\Program Files (x86)\Appeon\Shared\PowerBuilder\x64\PBSNC170.DLL



As per Alfredo, I do not see the 64-bit OLE DB driver which is expected also.





However, as I am using the SNC driver, of which both 32 and 64-bit variations are available so I would expect it to work. Does SNC also utilise OLE DB driver - maybe for tracing?



That said, right now I can't even DB trace in the Uuer Interface which is 32-bit. I can do DB Trace on both 32 and 64-bit for DBMS = ORA Oracle



Thanks,

Richard

  1. Helpful
There are no comments made yet.
Richard Hennessy
Richard Hennessy Accepted Answer Pending Moderation
  1. Wednesday, 28 March 2018 00:17 AM UTC
  2. PowerBuilder
  3. # 3

Please ignore this. My issue was I didn't have a space after "TRACE" when specifying the transaction object DBMS.

 

So I had 

DBMS=TraceSNC SQL Native Client(OLE DB)

 

instead of 

DBMS=Trace SNC SQL Native Client(OLE DB)

 

Funnily enough, tracing works in Oracle even when you don't have a space which was throwing me off.

 

Thanks for any assistance and apologies for wasting any time spent on this

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.