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

Resolved Datawindow working in Client server but not working in Docker

  1. How-to
0
Votes
Undo
  1. billy hugon
    billy hugon
  2. PowerServer
  3. Thursday, 30 May 2024 14:33 PM UTC

I have converted my application to run from Client Server to Docker (and IIS).  I have a datawindow that is working in Client Server but not Docker.  I didnt receive any errors when generating my project on this datawindow.  The database is SqlServer and below is my select statement being passed.

 

 

The error I'm getting is pretty undescriptive.

 

 

I do have retrieval arguments for this datawindow and are as follows:

 

 

 

 

 

 

 

 

 

will PowerServerLabel Merge statements run SQLs pa...
C# documentation for powerserver 22R3 to build out...
Accepted Answer
billy hugon
billy hugon Accepted Answer Pending Moderation
  1. Thursday, 30 May 2024 18:15 PM UTC
  2. PowerServer
  3. # Permalink

I found an issue that is causing the problem.  Not sure why.  As I said, it works in client server, but fires the error in cloud environment.

I changed modifying the SQL statement

From:

mod_string = "DataWindow.Table.Select='"  + is_original_select + where_clause + order_by_clause + "'"


rc = dw_data.Modify(mod_string)

To:

mod_string = "'" + is_original_select + where_clause + order_by_clause + "'"

dw_data.SetSQLSelect(mod_string)

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 30 May 2024 21:32 PM UTC
Glad to hear you resolved the issue, and thanks for posting the solution. Yes, just because something works in client/server doesn't mean it will work in PowerServer deployment. When you run into issues, we recommend using the debugger to step through the code and cross-reference with the unsupported features guide: https://docs.appeon.com/ps2022r3/unsupported_features_guide.html
  1. Helpful
billy hugon
  1. billy hugon
  2. Thursday, 30 May 2024 21:39 PM UTC
Thats the problem. Stepping through the debugger it worked. It only didnt work when I went through the deployment and loaded in docker which is a major main to have to debug like that
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 31 May 2024 15:35 PM UTC
Did you use the PowerServer debugger not the client/server debugger? Two different debuggers.

And follow-up question, when you run it on IIS on hour developer PC without docker there is no problem?
  1. Helpful
There are no comments made yet.
Responses (4)
billy hugon
billy hugon Accepted Answer Pending Moderation
  1. Thursday, 30 May 2024 16:50 PM UTC
  2. PowerServer
  3. # 1

Also, I'm running Version 2022 R3 Build 3289

Comment
There are no comments made yet.
billy hugon
billy hugon Accepted Answer Pending Moderation
  1. Thursday, 30 May 2024 15:52 PM UTC
  2. PowerServer
  3. # 2

It was running in client server for years.  I moved it to IIS first to get it working (yes Powerserver).  Then I converted it to run in a Docker container.  

This error is happening in IIS and Docker, so it must be something to do with the Powerserver conversion.

 

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 30 May 2024 15:40 PM UTC
  2. PowerServer
  3. # 3

What do you mean you converted it to use IIS?  Are you using PowerServer?  What version of PowerBuilder?  Which SQL Server driver are you using?

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.
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.