• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Can't connect using ODBC for the PowerServer application

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

Resolved Can't connect using ODBC for the PowerServer application

  1. How-to
0
Votes
Undo
  1. Olaf Brungot
    Olaf Brungot
  2. PowerServer
  3. Monday, 13 June 2022 12:01 PM UTC

I can't get the PowerServer application to connect to the database while running.

The PowerBuilder application is 32-bit and uses a 32-bit ODBC (SA17). It connects and runs as usual when running as a PowerBuilder app.
This is with a .ini file for the 32-bit connection.

I've set up a connection profile for the WebAPI (64-bit ODBC SA17), which connects fine from Database Configuration

Running the solution as a PowerServer application I do get this error from.

The .ini file at the deployed PowerServer have been tested with both the 32-bit odbc as used in PowerBuilder, but also with the 64-bit odbc set up in Database Configuration for the WebAPi.

The content of the .ini file is as simple as can be

[PowerServerTest]
DBMS=ODBC
Database=
UserId=
DatabasePassword=
Logpassword=
Servername=
Logid=
DbParm=Connectstring='DSN=PowerServerTest'
Prompt=0

I've tried to follow the documentation, but I can't find the missing steps here.

 

 

 

PowerServer 2021 - Issues with Oracle StoredProced...
PowerServer 2021 Build Error - Duplicate Objects
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 13 June 2022 14:09 PM UTC
  2. PowerServer
  3. # Permalink

Are you using SQL Anywhere 16 or newer?  

Did you map your transaction objects to the connection cache?

Please read and follow this section of the DB guide: https://docs.appeon.com/ps2022/Setting_up_static_database_connection_for_the_app_runtime.html

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 13 June 2022 17:06 PM UTC
Hi Armeen .. that looks like Olaf's issue ... the TO is *not* mapped in PS Project (see his above screen capture of his DB test).
  1. Helpful
Olaf Brungot
  1. Olaf Brungot
  2. Tuesday, 14 June 2022 06:03 AM UTC
Thanks, I'll look into it. I am using SQL Anywhere 17.
  1. Helpful
Olaf Brungot
  1. Olaf Brungot
  2. Tuesday, 14 June 2022 06:22 AM UTC
That seemed to solve the issue. I am still not able to run the application successful as a PowerServer application, but I'm one step further. Thanks :)
  1. Helpful
There are no comments made yet.
Responses (3)
Ronnie Po
Ronnie Po Accepted Answer Pending Moderation
  1. Monday, 13 June 2022 17:54 PM UTC
  2. PowerServer
  3. # 1

Is the database server running on the same computer as the WebAPI server? If so, you'll have to set up your ODBC DSN as follows. Do NOT choose the Action "Connect to running database on this computer." Host can also be the IP address or computer name.

Comment
Olaf Brungot
  1. Olaf Brungot
  2. Tuesday, 14 June 2022 06:11 AM UTC
No the database is running on an another computer.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 13 June 2022 12:06 PM UTC
  2. PowerServer
  3. # 2

Hi,

Do you have the same connection profile setup also for windows ODBC 64 bit administrator?

regards

Comment
Olaf Brungot
  1. Olaf Brungot
  2. Monday, 13 June 2022 13:09 PM UTC
Yes. Same database and same username/password for both ODBC
  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.