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

Resolved Unable to connect to Database

  1. Issue
0
Votes
Undo
  1. James Pendarvis
    James Pendarvis
  2. PowerBuilder
  3. Friday, 22 November 2019 15:25 PM UTC

I have approached this issue in the past without success. I am hoping that I can provide A LOT more information and someone can point me in the right direction.

I have a client/server application that has been upgraded to PowerBuilder 2017. I am wanting to take advantage of ADO.NET to connect to my database.

When I run the application through the IDE, I am able to connect successfully. I pull the connection string to format the executable string to match. 

When I deploy I get an error - DBMS ADO.NET is not supported in your current installation.

 

I have copied all DLL's to the folder that I am executing from.

I have created a "Data Link" using Microsoft OLE DB Provider for SQL Server and I am successful in attaching to the database. 

Microsoft .NET Framework's 3.5 and 4.7 have been installed. 

 

The Connection Info is as followed:

sqlca.database = database name

dbms=ADO.NET

dbparm=DataSource=ServerName, TrustedConnection=1,NameSpace='System.Data.SqlClient', Database=database name

Servername=

Path=D:\Update Files\****.exe

  1. ADO.NET
  2. Database
How do i can to use SqlCa with threads (sharedobje...
Scrolling with touchpad
Responses (3)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 22 November 2019 15:52 PM UTC
  2. PowerBuilder
  3. # 1

When running from the IDE, you're running as 32 bit.

If you're application is also deployed as 32 bit, maybe the configured profile for db connection is not 32 bit?

If you're deploying a 64 bit executable, then you'd have to install 64 bit db client and configure the 64 bit connection profile?

Hope any expert can shed some light if I'm wrong.

Comment
James Pendarvis
  1. James Pendarvis
  2. Friday, 22 November 2019 15:59 PM UTC
I have deployed both 32-bit and 64-bit runtime MSI files against the server hosting the application.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 22 November 2019 16:01 PM UTC
Though maybe a bit of a pain... run process monitor and see which file is not being found (probable problem).
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 22 November 2019 16:03 PM UTC
Process Monitor: https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

First filter by file access only and your executable name.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 22 November 2019 16:11 PM UTC
  2. PowerBuilder
  3. # 2

What do you mean when you say you get an error "when you deploy"?

Is that while you are deploying or after you've deployed and run the application using the EXE file?

HIH

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 22 November 2019 17:43 PM UTC
Any DLL not being found when running
  1. Helpful
James Pendarvis
  1. James Pendarvis
  2. Friday, 22 November 2019 18:16 PM UTC
I did not see anything, but I captured the report and sent it off to some other individuals to see there is something that they are seeing.

  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 23 November 2019 04:28 AM UTC
If you / they cannot find any files not being found, the next thing to look at is registry entry access in the logged file.
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 22 November 2019 17:14 PM UTC
  2. PowerBuilder
  3. # 3

Did you deploy PBADO170.DLL?

Comment
James Pendarvis
  1. James Pendarvis
  2. Friday, 22 November 2019 17:18 PM UTC
Yes, that is part of the runtime deployment script generated by PowerBuilder and I also have the DLL in the folder hosting the application.
  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.