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

Resolved MsSQL Server Instance Data Cache Fail during test - PowerServer

  1. Issue
0
Votes
Undo
  1. Andres Slachevsky
    Andres Slachevsky
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 18 June 2018 14:52 PM UTC

We are finishing the Test of our PowerServer 2016 PB12.5.2 Application

in the development Server we have the Data Cache Host set as :Kraken and it work perfect

now we need to set the production server 

the host is sqlprod\prod and it fail with this error:

Testing Data Source sia_db failed: Error relacionado con la red o específico de la instancia mientras se establecía una conexión con el servidor SQL Server. No se encontró el servidor o éste no estaba accesible. Compruebe que el nombre de la instancia es correcto y que SQL Server está configurado para admitir conexiones remotas. (provider: TCP Provider, error: 0 - No se puede establecer una conexión ya que el equipo de destino denegó expresamente dicha conexión.)

i did try to use 

sqlprod or the IP and it does not solve the problem

  1. PowerServer
PowerServer as a Service on the Cloud
show document on the web
Responses (5)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 18 June 2018 15:22 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Andres;

  Can you connect to the production SS via iSQL or SS Management Studio OK?

Regards ... Chris

Comment
Andres Slachevsky
  1. Andres Slachevsky
  2. Tuesday, 19 June 2018 11:44 AM UTC
I Can coonect to SQL SERVER using a PB Application in the same machine.



 

  1. Helpful
There are no comments made yet.
Alfredo Aldama
Alfredo Aldama Accepted Answer Pending Moderation
  1. Monday, 18 June 2018 16:38 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2
Hi Andrés, Estas son las recomendaciones del fabricante https://blogs.technet.microsoft.com/mdegre/2011/06/03/solucionar-problemas-de-conectividad-del-sql-server/ De lado de appeon-powerbuilder, revisa que tienes bien configurado el objeto de conexión SQLCA, cuando se hace la migración es un paso más, sin embargo si es diferente a tu ambiente de producción deberás de crear un nuevo alias en tu Server para la conexión, tu código deberá de coincidir con ese alias Saludos!
Comment
Andres Slachevsky
  1. Andres Slachevsky
  2. Tuesday, 19 June 2018 11:45 AM UTC
Hola Alfredo,



no tengo problemas para conectarme desde PowerBuilder



Ni para conectarme a un servidor que no tenga la \ 



por ejemplo el servidor de desarrollo se llama kraken y si puedo conectarme, pero el servidor de produccion que se llama sqlprod\prod tiene problemas 

  1. Helpful
Alfredo Aldama
  1. Alfredo Aldama
  2. Tuesday, 19 June 2018 12:49 PM UTC
Puedes poner Screenshots? Si es así comparte donde tienes configurado el objeto de conexión y el código donde haces la conexión podría ayudar a entender porque en ambiente de desarrollo si te conectas con ambas herramientas y en producción no.

Saludos
  1. Helpful
There are no comments made yet.
Appeon Support Team
Appeon Support Team Accepted Answer Pending Moderation
  1. Tuesday, 19 June 2018 00:38 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Andres,

Please refer to article below to solve the issue.
https://support.appeon.com/index.php?/Knowledgebase/Article/View/48/11/cannot-connect-to-the-sql-server

Regards,
ZhaoKa

Comment
Andres Slachevsky
  1. Andres Slachevsky
  2. Tuesday, 19 June 2018 12:04 PM UTC
The configuration on both server are the same



the connection thru ODBC or PB application works



the Only difference between the 2 server is that the development server have no \ on it

  1. Helpful
There are no comments made yet.
Andres Slachevsky
Andres Slachevsky Accepted Answer Pending Moderation
  1. Tuesday, 19 June 2018 11:48 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hello,

i did try using the IP or the SQLPROD wihout the \prod

if i run a PB Application in the server it works.

and using de development server it also connect to the DataServer

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 19 June 2018 13:25 PM UTC
Hi Andres;



   Sounds like you might have a firewall / proxy issue if PowerServer is not located on the same machine as SS.



Regards ... Chris

  1. Helpful
There are no comments made yet.
Andres Slachevsky
Andres Slachevsky Accepted Answer Pending Moderation
  1. Tuesday, 19 June 2018 13:59 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

Thanks to all.

was a problem with a Network setting.

We check with the network admin and the DB admin and they solve the problem 

Comment
Olan Knight
  1. Olan Knight
  2. Tuesday, 19 June 2018 18:54 PM UTC
What network setting was changed to resolve the issue?



TIA,

Olan

  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.