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

Resolved SnapDevelop SQL Server DB connection

  1. How-to
0
Votes
Undo
  1. Matthew Balent
    Matthew Balent
  2. Beta Testing
  3. Friday, 18 December 2020 16:09 PM UTC

I'm unable to set up a new database connection to my local instance of SQL Server from within SnapDevelop 2019 R3 Beta.  I only get the following message: 

"A network-related or instance-specific error occurred while establishing a connection to SQL server. The server was not found or was not accessible.  Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.)"

 

I am able to establish connections through PowerBuilder as well as Visual Studio.

 

Ideas?

- Matt Balent

  1. SnapDevelop
PB2019 R3 beta
PowerClient R3(Beta2) failing to split PBDs
Responses (2)
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 December 2020 16:27 PM UTC
  2. Beta Testing
  3. # 1

Hi Matthew,

 

You might want to make sure that your TCP/IP protocol is enabled in the SQL Server Configuration manager and that they point to the Default port 1433. Also, you might need the named pipes enabled too. You may find instructions on how to do this here: https://www.blackbaud.com/files/support/infinityinstaller/content/installermaster/tkenablenamedpipesandtcpipconnections.htm

 

Please do let us know if this worked for you.

 

 

Regards,

Comment
mike S
  1. mike S
  2. Friday, 18 December 2020 17:42 PM UTC
TCP/IP makes sense. named pipes does not as it is legacy and is NOT used for internet traffic. It probably should never be used if at all possible for any type of application. if named pipes IS required, then that may be a problem
  1. Helpful
Govinda Lopez @Appeon
  1. Govinda Lopez @Appeon
  2. Friday, 18 December 2020 18:01 PM UTC
Named pipes can be good for local machine communication (https://stackoverflow.com/questions/175579/what-are-named-pipes). Some prefer to use them over TCP/IP for other reasons too ( https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2016/ms187892(v=sql.130) ). A good evaluation before implementing one or the other approach is always considered a good practice. But, I mentioned it in this post just in case they needed the configuration too. I'll let the reader decide which one is better. :)
  1. Helpful
mike S
  1. mike S
  2. Friday, 18 December 2020 19:02 PM UTC
this thread makes it sound like you have to have named pipes configured for snap develop to work.

fwiw, local machine communication is what shared memory protocol is for. using named pipes for that is possible, but slower
  1. Helpful
There are no comments made yet.
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Friday, 18 December 2020 17:01 PM UTC
  2. Beta Testing
  3. # 2

That did it for me.  Had to enable both TCP and Named Pipes.

Comment
Govinda Lopez @Appeon
  1. Govinda Lopez @Appeon
  2. Friday, 18 December 2020 17:37 PM UTC
Great to know! I just want to add that for some setups they might also need to add a rule to their Firewall to enable communications through port 1433 which is the default SQL Server port.



I'm adding this comment hoping that it might help anyone else experiencing this problem.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 18 December 2020 18:15 PM UTC
Thanks for sharing the solution Matt!
  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.