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

Resolved .NET web service fails to connect to database

  1. Advice
0
Votes
Undo
  1. Harald Høgestøl
    Harald Høgestøl
  2. PowerBuilder
  3. Thursday, 24 October 2024 14:13 PM UTC

Hi,

I have a .NET web service built with PB 2017 R3 that fails to connect to an ASE 16 database.

Web server: Windows Server 2019 / IIS 10 / ASE 15.7 DB client

DB server: ASE 16

Webserver is set up with:
- PB 2017 R3 runtime files (32 and 64 bit) and .NET runtime files. All three packages are created with PB runtime packager.
- The PBDotnet4AppPool is set up with .NET CLR version v4.0.30319, Classic mode, 32-bit apps enabled.

The webserver was booted after the install.

 

The message returned when the web service calls sqlca.connect is 4002: Login failed

Auditing on the db server shows that password is incorrect (network password sybase encryption, 4067.14.1), I have also tried without encryption, same result.

To verify correct setup of sqlca I put all settings into a logfile before connecting (servername, database, logid, logpass and dbparm). 

The logfile looks like this:

2024-10-24 15:31:13 Connecting to ProsaTst/prosa_test LogId: ims_interface_user/****** DBMS: ASE Adaptive Server Enterprise DBParm: Release='15',AppName = 'IMS interface'
2024-10-24 15:31:13 4002: Login failed.

If I connect with InteractiveSQL from the webserver with exact same credentials (cut and paste form the logfile) it connects successfully.

I also tried to install the PB 2017 R3 IDE on the webserver, and connected to the same database from the IDE with the exact same credentials (cut and paste form the logfile) and it connects successfully.

I can't figure out why the webservice db connect fails. Does anybody have a clue?

  1. Database
  2. Web Service
Ghostscript problem with Pwerbuilder 2019 on Win11
Connecting to MSOLEDBSQL using access token, issue...
Responses (4)
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Friday, 25 October 2024 10:13 AM UTC
  2. PowerBuilder
  3. # 1

Hi Harald,

did you also use AppName='IMS interface' when you connect via PowerBuilder IDE ( Database Painter or via ISQL?

Does connecting with AppName='IMS interface' work with that AppName from PB IDE and isql?

If yes, consider that IIS and the WebService Worker are running under other identities than your personal or admin windows account so that the environment can differ from you account settings.

hth

Arnd

Comment
There are no comments made yet.
Harald Høgestøl
Harald Høgestøl Accepted Answer Pending Moderation
  1. Friday, 25 October 2024 06:41 AM UTC
  2. PowerBuilder
  3. # 2

Btw,

I am aware that this method is obsolete, but it will be decommissioned next year and I don't want to re write the whole thing.

 

Comment
There are no comments made yet.
Harald Høgestøl
Harald Høgestøl Accepted Answer Pending Moderation
  1. Friday, 25 October 2024 06:36 AM UTC
  2. PowerBuilder
  3. # 3

Hi Chris,

 

Sorry for being unclear. It was originally made with PB 12.5, I have migrated it to 2017. It generates fine with no error messages and I can also deploy it to the web server with no errors.

It is a .Net Web service that is being accessed with Soap calls. The problem I have is on the server side, not the caller side.

When the web service is activated it is supposed connect to a ASE 16 database and insert some data, but the connection attempt fails.

Hope that makes sense.

 

Harald

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 October 2024 15:49 PM UTC
  2. PowerBuilder
  3. # 4

Hi Harald;

  I am confused as PB 2017 has no Web API creation capabilities. You would need to use the new SnapDevelop tool (that comes with PB 2021 & higher) to create such a WebAPI in C#.

  Are yo referring to a .NET WebAPI object (DLL) that was built using another tool that you are then trying to call from your PB App?

Regards .. Chris

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 25 October 2024 03:38 AM UTC
PB 2017 still had the legacy SOAP stuff Sybase introduced in PB 11. It was removed in PB 2022. https://www.appeon.com/developers/obsolete-and-discontinued-features-in-powerbuilder-2022.html
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.