• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Powerserver - SQL Anywhere 17 Connection cannot be established on live program

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

Resolved Powerserver - SQL Anywhere 17 Connection cannot be established on live program

  1. How-to
0
Votes
Undo
  1. Sven Fischer
    Sven Fischer
  2. PowerServer
  3. Friday, 21 July 2023 13:54 PM UTC

Hi, 

 

I'm currently testing the Trial Version of Powerbuilder 2022 with Powerserver to evaluate this.

My trouble is how to establish the connection with sqlca to the database

 

I'm currently using SQL Anywhere 17 32/64 Bit ODBC

 

I've tried dozens of different settings without any success and it responds that it doesn't find the driver or database name when trying to connect.

 

Starting the program without PowerServer was never a problem, just with using PowerServer.
I'm not sure what to enter in the first screenshot to the right at Source-> Driver... tried SQL Anywhere 17, SqlAnywhere, etc.
Also using cache names, or using dbparm without cache names in the configuration. 


 

 

  1. PowerServer
  2. SQL Anywhere
PowerServer 2022 and Oracle 10g
Alternatives for AppeonDotNetComponent
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 21 July 2023 14:25 PM UTC
  2. PowerServer
  3. # 1

Hi Sven;

  Note that PowerServer runs as a 64 bit App and thus, you need to be using the SA's 64 bit ODBC client within a 64bit DSN.  HTH

Regards ... Chris

Comment
There are no comments made yet.
Francisco Martinez @Appeon
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Friday, 21 July 2023 14:10 PM UTC
  2. PowerServer
  3. # 2

Hi Sven,

Please review this documentation page to make sure you're following the appropriate steps for your situation: https://docs.appeon.com/ps2022/Configuring_in_PowerBuilder_IDE_for_app_runtime.html

 

Regards,
Francisco

Comment
Sven Fischer
  1. Sven Fischer
  2. Tuesday, 1 August 2023 07:06 AM UTC
Hi Francisco,







I did everything according to the documentation. What I noticed is when I run the C# Solution via PowerSnap I get the following Error:





An unhandled exception of type 'System.Net.Sockets.SocketException' occurred in System.Net.Sockets.dll:

'Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.'

(Translated: Access to the socket is due to access privileges unauthorized)



Do you have any idea what could cause this?
  1. Helpful
There are no comments made yet.
Sven Fischer
Sven Fischer Accepted Answer Pending Moderation
  1. Tuesday, 1 August 2023 07:05 AM UTC
  2. PowerServer
  3. # 3

I did everything according to the documentation. What I noticed is when I run the C# Solution via PowerSnap I get the following Error:


An unhandled exception of type 'System.Net.Sockets.SocketException' occurred in System.Net.Sockets.dll:
'Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.' 
(Translated: Access to the socket is due to access privileges unauthorized)

Do you have any idea what could cause this?

Comment
Francisco Martinez @Appeon
  1. Francisco Martinez @Appeon
  2. Tuesday, 1 August 2023 14:11 PM UTC
Most likely the port you chose for the PowerServer API is already in use by another application/service. Please use a port that's not in use for the Web API
  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.