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

Resolved testing data source failed

  1. Issue
0
Votes
Undo
  1. Ganne Gannene
    Ganne Gannene
  2. PowerServer 2020 or older (Obsolete)
  3. Thursday, 1 March 2018 17:01 PM UTC

Hi to all.

I have this error when connecting to test db profile from powerserver toolkit configuration:

testing data source failed
error code 12506
the input function type is invalid.

 

I'm using ms sql. With PB2017 db profile it works fine

I'm using Appeon PowerServer 2017 Build 1689.00

My application worked fine but today give me this error. And now I can not deploy on powerserver web.

Have you got any suggestion?

Thank you.

 

  1. Data
problem with powerserver and 30 days license
Appeon Plugin in Chorme, FireFox
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 March 2018 14:51 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Ganne;

   SS 2017 is working great for me with PB 2017 and PS 2017 - However, I do have the same issue as you but have a workaround, as follows:

PS Toolkit Configuration ....

 

PS ToolKit ADD Source ...

Looks like the SA / MySQL Native driver ADD Source issue might also apply to SQL Server as well.

 

AEM Data Source ...

 

PS Toolkit using PS Server Data Source mapping to SS ...

 

    So in summary, this looks like a PS ToolKit bug like for SA & MySQL.

My suggestion for a "workaround is to add the Data Source in PowerServer's AEM console and then return to PB's PS Toolkit to complete the Data Source mapping using the PS's DataSource mapped DB connection vs trying to add it from the PS toolkit.

 

HTH

Regards ... Chris

Comment
Ganne Gannene
  1. Ganne Gannene
  2. Friday, 2 March 2018 16:15 PM UTC
Hi Chris,



       I try it, but I have same problem. Deploy fail with "Failed to generate DWSQL", but the problem is that transaction object is not connected during deploy.

  1. Helpful
Govinda Lopez @Appeon
  1. Govinda Lopez @Appeon
  2. Saturday, 3 March 2018 01:46 AM UTC
Hi Ganne,



 



Please open a support ticket : https://www.appeon.com/standardsupport/newbug 



 



As Armeen said, this might require remote assistance.



 



Regards,

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 March 2018 21:13 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Ganne;

  We have had a similar issue with SQL Anywhere. The issue revolves around the native driver vs the ODBC. I wonder if you could check / try ...

  • Continue to use the Native MySQL driver for PowerServer
  • In the toolkit configuration though, set your DB profile to use the ODBC driver for MySQL.

Using the ODBC driver in the Toolkit for deployment should not hurt using the native driver in PS at run-time.

Please let us know if that workaround works for you.

Regards ... Chris

 

Comment
Ganne Gannene
  1. Ganne Gannene
  2. Friday, 2 March 2018 06:57 AM UTC
Sorry Chris, I'm using microsoft Sql server 2014, not mysql. ODBC driver in the toolkit for deployment not works with it.

  1. Helpful
Ganne Gannene
  1. Ganne Gannene
  2. Friday, 2 March 2018 08:04 AM UTC




this is error.



But in pb database profile snc sql native client works fine, and in localhost/aem data source test is ok.



Where is the problem?



I have people stopped working because of this error



I don't know what to look

  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 March 2018 17:40 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Please open a support ticket.  This will most likely require us to collect more information than you provided and possibly troubleshoot remotely.

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.