1. backya arun
  2. PowerBuilder
  3. Tuesday, 24 March 2020 06:41 AM UTC

Hi

I have migrated PB 8 to PB 19.. Application is opening in our environment..

In client environment i'm getting this error 'SQL native client is not installed'..

DBMS:SQL server 2008R2

Interface: SNC SQL Native Client(OLE DB)

client DBMS:SQL server 2016

I have downloaded SQLNCLI11.msi and copied the installed files in client machine

(client doesn't agree to install msi)

Can you please help me regarding this???

 

regards,

Backya

 

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 24 March 2020 08:30 AM UTC
  2. PowerBuilder
  3. # 1

Hi Arun,

Please first read this and make sure you have the correct driver for SQL Server:

https://docs.appeon.com/appeon_online_help/pb2019/connecting_to_your_database/ch10s07.html

It says you need the v 10 driver, but I think the v 11 should be okay or even more compatible. Since you say that all is working fine on your developer machine:

You're getting the error "SQL native client is not installed ..", because indeed, it's not been installed.

"Client doesn't agree to install MSI?" Haha, we have a customer who would "only allow installs using MSI" anything else they don't like. But I know ... "customer is king", regretfully.

Plan A: Try to get someone (preferably of his own staff) to talk some sense into this customers head. 

Plan B: If you are allowed to "import reg files", I guess one of your options might be to:

1) create a clean windows install on maybe a virtual machine, update all windows updates and then export the registry to "before.reg". (If you don't do the windows updates first you will get lots of differences with the registry exported in step 3) ).

2) install your of SNC sql server by using the MSI (as soon as possible, to avoid many registry differences in step 3)

3) export the registry to "after.reg".  

4) compare all the differences in the registry files of "before" and "after.reg", using a tool like "araxis merge", "Meld", "windiff", etc. This will allow you to get all the registry entries that normally would have been done by the MSI installer.

There's also tools like the "Wix installer tool" to generate all the differences between the before and after registry (I think "heat.exe" should be able to do it), but let's keep it simple.

5) save those differences as "reg_entries_needed_for_SNC.reg".

6) Now you can copy "all the files" and run the registry to get a - hopefully valid - install of SNC SQL server client.

 

Good Luck!

 

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 24 March 2020 09:38 AM UTC
  2. PowerBuilder
  3. # 2

I often see requirement for EITHER no install allowed (like you) OR only "official" install via MSI (like Miguel).

You may experience ADO.NET connection requires less installation than SQL Native Client.

/Michael

Comment
  1. Miguel Leeuwe
  2. Tuesday, 24 March 2020 09:53 AM UTC
Yes, but I think in another recent post he had some error messages which he then avoided by using the SNC client instead of the ADO .Net

Maybe the solution would be to solve those issues and not switching to SNC.

:)
  1. Helpful
  1. backya arun
  2. Tuesday, 24 March 2020 11:55 AM UTC
I have solved that exception issue by changing ADO.Net to SNC... In SNC i need to install msi in client machine and client is not agreed to that ..Any other way???
  1. Helpful
  1. Miguel Leeuwe
  2. Tuesday, 24 March 2020 12:17 PM UTC
The only thing I can think of is what I've said in my previous answer: copying files and importing registry entries that a normal install would have given you.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Tuesday, 24 March 2020 13:40 PM UTC
  2. PowerBuilder
  3. # 3

Since its SQL 2008, one could use OLE DB instead of SNC.  No need to install any drivers at client places.  

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.