move to a server: need ideas

[Bruce Riddle]

Greetings,

   My SQL has to be moved from Windows  Server 2012 and SQL 2012 to

Windows Server 2016 and SQL 2016.  I theory, all I had to do was

got in Route Not Read and just change the name of server.  Did not work.

Not so simple.   I get this:

PHINMS could not connect to database server at localhost:6087.

Either the database server is not running or an incorrect database

     host name and/or port number exists.  

 

hread-3|04/16|01:50:46|Error getting connection to jdbc:hsqldb:hsql://localhost:6087/phinms_core|

Thread-3|04/16|01:50:46||

Thread-3|04/16|01:50:46|ErrorMessage update successfully, table=ErrorMessage_sender|

Thread-3|04/16|01:50:46|No connection|

Thread-3|04/16|01:50:46|Waiting for records ...|

Thread-3|04/16|01:50:47|Error getting connection to jdbc:hsqldb:hsql://localhost:6087/phinms_core|

Thread-3|04/16|01:50:47||

Thread-3|04/16|01:50:47|ErrorMessage update successfully, table=ErrorMessage_sender|

Thread-3|04/16|01:50:47|No connection to database|

Thread-3|04/16|01:50:57|Connection established|

 

Any suggestions on what to try?   

Thanks.

Bruce 

[ph...@eskimo.com]

The error looks to be on the HSQLDB server that PHINMS installs and uses
as persistent cache. It may not be a MS SQL problem.

I was just caught in a similar situation trying to connect to the MS SQL
on my desktop from a server so I can test a new table configuration. It
kept failing to connect and SQL profiler showed me that it wasn't
receiving anything. I finally yanked out the workstation name and plugged
in the IP and it worked fine. What? It turns out that my workstation's
DNS is now mapped to an IPV6 address and it had never occurred to me to
set SQL up to listen to an IPV6 port as well as the IPV4 port. I'll have
to give up old habits.

Good luck with it.

> --
>
>
> ---
> You received this message because you are subscribed to the Google Groups
> "PHINMS User Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to phinms+un...@googlegroups.com. For more options, visit
> https://groups.google.com/d/optout.
>
>

[ph...@eskimo.com]

The error looks to be on the HSQLDB server that PHINMS installs and uses
as persistent cache. It may not be a MS SQL problem.

I was just caught in a similar situation trying to connect to the MS SQL
on my desktop from a server so I can test a new table configuration. It
kept failing to connect and SQL profiler showed me that it wasn't
receiving anything. I finally yanked out the workstation name and plugged
in the IP and it worked fine. What? It turns out that my workstation's
DNS is now mapped to an IPV6 address and it had never occurred to me to
set SQL up to listen to an IPV6 port as well as the IPV4 port. I'll have
to give up old habits.

Good luck with it.



On Mon, April 16, 2018 11:22 am, Bruce Riddle wrote: