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

Resolved Application Communication through DSN

  1. Issue
0
Votes
Undo
  1. Shijo Joseph
    Shijo Joseph
  2. PowerBuilder
  3. Thursday, 7 September 2023 07:56 AM UTC

Dear Team,

I am facing a critical issue with my power builder application. I am having a customized odbc driver which is communicating with my PB application. 

I am having another Visual Studio 2022 application which is communicate with my PB application with the help of the customized DSN. This is working fine when the  in the development. But it is not working while the VS application host in the IIS. When we debug the issue, the below line of code  gives the error.

 

This InvokeClassFunction is located in "C:\Program Files (x86)\Appeon\PowerBuilder 22.0\SDK\PBNI\include\pbni.h" file

Both the PB & VS applications are in 64 bit and the ODBC dll also built in the 64 bit.

 

Please treat it as urgent matter and guide me on this.

  1. 64-bit
  2. IIS
  3. ODBC
  4. Visual Studio
TFS MSSCCI 2013 error: Parameter is not valid
Stop Theme being applied to a window and all objec...
Responses (5)
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Friday, 22 September 2023 14:02 PM UTC
  2. PowerBuilder
  3. # 1

What about using a messaging product like MQ Series.  Both PB and VB can post/read to/from a message queue that you set up.  I have also used the database as the middleware for communication between apps.  

 

KR

Comment
There are no comments made yet.
Shijo Joseph
Shijo Joseph Accepted Answer Pending Moderation
  1. Tuesday, 12 September 2023 11:31 AM UTC
  2. PowerBuilder
  3. # 2

Hello Roland,

 

Thank you for query. CreateSession, FindGroup, ,FindClass, GetMethodID & InitCallInfo is working fine. Application crashes when triggering the "InvokeClassFunction". But this happends only when hosted in IIS. Its works fine in development environment

Comment
Load more comments
Shijo Joseph
  1. Shijo Joseph
  2. Friday, 22 September 2023 12:11 PM UTC


I tried to use this dll as ISAPI but am getting the error

HTTP Error 500.0 - Internal Server Error

Calling GetProcAddress on ISAPI filter "C:\PADDS\PADDS78\DatabaseViewer\padds_odbc.dll" failed



All the access is given for the IIS user to the folder
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Friday, 22 September 2023 17:20 PM UTC
An ISAPI DLL has functions it must expose which an ODBC driver wouldn't have. An ISAPI Extension requires these functions: GetExtensionVersion, HttpExtensionProc, TerminateExtension.
  1. Helpful
Shijo Joseph
  1. Shijo Joseph
  2. Tuesday, 26 September 2023 05:36 AM UTC
Hello Roland,

I came to a conclusion that communication happends when the web application runs in the "IISA EXpress" and facing the issue when runs the application "Local IIS"
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 8 September 2023 17:46 PM UTC
  2. PowerBuilder
  3. # 3

Maybe your PBNI C++ code is unable to find the PBD files. Are you sure the CreateSession, FindGroup, and FindClass calls worked?

Comment
There are no comments made yet.
Shijo Joseph
Shijo Joseph Accepted Answer Pending Moderation
  1. Friday, 8 September 2023 04:59 AM UTC
  2. PowerBuilder
  3. # 4

Hello @Armeen Mazda,

Thank You for your response. My applications and DSN are 64 bit.

 

Thanks

Shijo

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 8 September 2023 16:24 PM UTC
Sorry, don't have any other ideas to help you about this.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 7 September 2023 18:15 PM UTC
  2. PowerBuilder
  3. # 5

Is your app 32-bit?  32-bit app needs 32-bit DSN.

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.