Problem connecting to MSSQL

3 replies [Last post]
emile
User offline. Last seen 1 week 3 days ago. Offline
Joined: 11/08/2007

Problems connecting to MSSQL. The Remote Player Host keeps saying that it is unable to connect to the SQL

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connection. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

I have enabled Local connections with Named pipes, but this does not seem to have made a scott of difference. I am going to continue to poke away at this until I can make sense of it, but any help would be grateful.

Thanks.

mtrix
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 25/08/2009
actually its the problem

actually its the problem when you use database with default instance, this means you dont have to use MYSERVER\THISINSTANCE, just MYSERVER in config file.

emile
User offline. Last seen 1 week 3 days ago. Offline
Joined: 11/08/2007
Solution found...

User resolved issue by following MSSQL configuration steps on this page:

http://www.datamasker.com/SSE2005_NetworkCfg.htm

Here's a quick summary of the actions you need to take. The first three actions have a separate page which provides more details and some screen shots of the procedure.

 

  1. [Link] Enable the TCP/IP protocol using the Surface Area Configuration Utility
  2. [Link] Make sure the TCP/IP protocol is enabled in the SQL Server Configuration Utility
  3. [Link] Make sure the SQL Server browser is started. Note this step is optional. It is possible to set the SQL Server instance to use a fixed IP address - but this is non-standard for named instances. See sqlexpress's WebLog for details.
  4. Make sure SQL Server and SQL Server Browser are exempted by the firewall on the server machine. This is done by putting sqlservr.exe and sqlbrowser.exe as an exception in the windows firewall.
  5. Note: In order to get things to work. You might need to completely reboot the server machine after making the changes. There have been reports (thanks P.C.) that starting and stopping the SQL Server and Browser software is not enough.
emile
User offline. Last seen 1 week 3 days ago. Offline
Joined: 11/08/2007
Problem connecting to MSSQL

You can find more details on the error you're seeing by looking at the log files in the folder "C:\Program Files\Media Bonza\Broadcast Power\2.5". All log files have the word "log" in their names.

From what you are describing, it seems BP2X cannot connect to the SQL server instance.

I suggest you read the following thread on our forums first: http://www.bp2x.com/node/11

I recommend that you then try to connect to the SQL instance from a command prompt to confirm that it is functional and working and then apply the same settings to the connection string in the config files "RemotePlayerHost.exe.config" and "WinUI.exe.config".

Try the following command, changing the parameters to match your system's.

osql -U sa -P password -S 127.0.0.1\sql1

If you manage to get the above command to work in DOS, there should be no reason why the remote player won't connect to it unless the config parameters are wrong.

Also, please check that the TCP/IP connectivity to SQL is enabled and not blocked by your firewall.

Best regards,

Emile Bassil