1. Miguel Alzate
  2. PowerServer Mobile (Obsolete)
  3. Monday, 20 January 2020 17:47 PM UTC

Hi, all

Getting this error in deployment log of mobile app: "Failed to generate DWSQL". All DWs show blank when running app.

Tested DB connection in PSToolkit DB profile: error when specifying SQL Native Client but OK with ODBC.

I'm using PB2019 Build 2082 (Universal Edition) and PS2019 Build 2151. Error does not occur when deplying with PB2017 R3 Build 1858 (Universal Edition) and PS2017 R3 Build 1858 (PB Edition).

Searched the whole net for a solution but none worked. Help, please!

 

Accepted Answer
Miguel Alzate Accepted Answer Pending Moderation
  1. Friday, 24 January 2020 19:48 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # Permalink

Hi,

Finally, a system restore resolved the problem. Now, the Toolkit can view the database even using the 64-bit native SQL client. An automatic Windows update had, somehow (?), unconfigured the system.

Thanks all for your help!

Comment
  1. Armeen Mazda @Appeon
  2. Friday, 24 January 2020 19:51 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Slawomir Lewinski Accepted Answer Pending Moderation
  1. Tuesday, 6 September 2022 12:56 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 1

Hi, 

I have exactly same problem with PS2019 toolkit R3. Any solution ?

 

Sławomir  

Comment
  1. Andreas Mykonios
  2. Tuesday, 6 September 2022 13:19 PM UTC
Hi.

It's not a good idea to post a question like that in such an old question. Especially in one that is marked as solved.

I guess that solution provided here isn't helpful in your case. Then you should create a new question.

Andreas.
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 January 2020 00:59 AM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 2

Hi Miguel,

Firstly, please go to Toolkit > Configure > Application profile configuration > DB Settings to check and make sure the database type being used is checked and test connection is OK. Then, try the solution below:

Step 1: Full build your PowerBuilder application.

Step 2: Go to \%Toolkit%\Project\your_application\release or debug\dwsql\dwsql.log to get the last record, empty compiled this DataWindow in PowerBuilder (Add a character and delete this character in the edit source of PB)

Step 3: Deploy your application again.


If still this issue, please try to use the attached PBL to compile a new eondwsql190.exe via PB 2019 on this machine, and then replace the file 'Eondwsql190.exe' located in C:\Program Files (x86)\Appeon\PowerServer 2019\Toolkit.

Regards,
ZhaoKai

Attachments (1)
Comment
  1. Miguel Alzate
  2. Wednesday, 22 January 2020 13:40 PM UTC
Hi, ZhaoKai.



I did exactly as you indicated, including the last option (i.e. compile Eondwsql190.exe). Error persists.



In Database Type Profile Configuration dialog box of Toolkit, the Test Connection is successful whith ODBC Interface but fails wjth Native Interface (MSSQLServer Database Type). 64-bit SQL Native Client is installed on the machine. I was told to install the 32-bit client but, when doing so, a paltform incompatibility error message appears. How could I install 32-bit SQL client on 64-bit Windows 7 Professional?
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 21 January 2020 00:32 AM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 3

Hi Miguel,

Toolkit provides two options to connect to SQL Server, for applications deployment, ODBC interface and native interface, the options are the same. It is used to parse the SQL of the DataWindow, and it does not relate to the database or the driver for running the application.

Therefore, please use the ODBC interface to deploy applications.


Regards,
ZhaoKai

Comment
  1. Miguel Alzate
  2. Tuesday, 21 January 2020 11:39 AM UTC
Hi ZhaoKai,



I am, in effect, using ODBC in Toolkit and the connection test is successful. However, deployment still throws the "Failed to generate DWSQL" message and DWs show balnk when running then app.

  1. Helpful
  1. Armeen Mazda @Appeon
  2. Tuesday, 21 January 2020 18:10 PM UTC
Please provide screenshots of how you configured the application that is having the deployment errors.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 19:00 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 4

Hi Miguel;

  Native should work as well (just not ODBC in PS) ...

SS2019 example:

Note: You will need the 32bit SS drivers for the PS Toolkit!

Regards ... Chris

Comment
  1. Miguel Alzate
  2. Monday, 20 January 2020 19:05 PM UTC
Is the attached screen PSToolkit 2019's?
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 20 January 2020 19:08 PM UTC
Yep! ;-)
  1. Helpful
  1. Miguel Alzate
  2. Monday, 20 January 2020 19:30 PM UTC
Thanks, Chris. Gonna try 32-bit SQL client.
  1. Helpful
There are no comments made yet.
Miguel Alzate Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 18:51 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 5

Configure connection with ODBC interface:

Test successful

Configure with native interface (to the same DB):

Test failure:

 

Comment
  1. Miguel Alzate
  2. Monday, 20 January 2020 20:39 PM UTC
Yes, Armeen. I can connect from Powerbuilder and from Powerserver. The problem is with Toolkit.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Tuesday, 21 January 2020 00:17 AM UTC
It's a config issue. Besides looking over the settings, make sure you have 32-bit client. The PowerServer Toolkit is 32-bit.
  1. Helpful
  1. Miguel Alzate
  2. Tuesday, 21 January 2020 11:43 AM UTC
I'm tryng to install the 32-bit SQL client on Windows 7 Professional (where PB and PS reside) but getting platform incompatibility message. Do you know a way to work around this SQL Native Client "bitage" incompatibility?
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 18:36 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 6

Mike is exactly right.  This error message is related to improper configuration of the PowerServer Toolkit since you are getting deployment-related error.  Since your app did not deploy properly so it is definitely not going to run properly, but that doesn't mean you have a runtime issue.

Comment
  1. Miguel Alzate
  2. Monday, 20 January 2020 18:43 PM UTC
You're also right, Armeen. It´s a deploy, not a run issue.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 20 January 2020 19:05 PM UTC
Remember ... you'll need the SS 32bit drivers installed for the PB IDE and the PS Toolkit. However, you'll need the 64bit SS Drivers for PS itself.
  1. Helpful
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 18:17 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 7

make sure you configured your database in the powerserver TOOLkit db type profiles, not just the data source profiles

Comment
  1. Miguel Alzate
  2. Monday, 20 January 2020 18:33 PM UTC
DB type profile in PStoolkit is properly configured, for sure, Mike. In fact, as I mentioned, it connects well for ODBC interface but not so for SQL Native Client.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 20 January 2020 18:36 PM UTC
What database are you using?
  1. Helpful
  1. Miguel Alzate
  2. Monday, 20 January 2020 18:40 PM UTC
SQL Server 2008 R2.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 18:04 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 8

Hi Miguel;

  You can use ODBC in the PS App's "Profile" to connect to SS for DW SQL verification. However in PowerServer  itself, ODBC will not work (although it pings OK). You must create the SS Data Source as "native" in PS.

HTH

Regards .... Chris

Comment
  1. Miguel Alzate
  2. Monday, 20 January 2020 18:38 PM UTC


Hi, Chris. PowerServer connects fine to database with MS SQL Server Native Driver. In PStoolkit SQL verification, ODBC does fine but SQL Native Client doesn´t.
  1. Helpful
  1. Miguel Alzate
  2. Monday, 20 January 2020 18:39 PM UTC
In any case, the error occurs when deploying.
  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.