DS 4.0: Configure a new Data Services Repository Error

I am trying to set up a DS repository within the CMC and I am getting the following error:

“There is a problem to connect to repository: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect”

All repositories reside in the same SQL Server DB. I have tried different logins even SA.

Any assistance would be greatly appreciated.

Thanks,

Victor
DS40RepoError.jpg


vmontana (BOB member since 2006-08-25)

problem is not with the login, you are giving the Instance name along with the hostname,you need to give only the hostname (WIN-KJV0O1TB3TL) not (WIN-KJV0O1TB3TL\BOE140)


manoj_d (BOB member since 2009-01-02)

I have tired that but it’s not the case. I have also tried creating an ODBC DSN vs using OLEDB but still not working.

Thanks,

Victor


vmontana (BOB member since 2006-08-25)

you don’t need ODBC DSN or OLEDB for DS repo, if you are not able to test the connection using DSN then the problem is network related not DS

the repo test connection in CMC is using JDBC so its not using the client installation

from the error message either the hostname is not correct or the port number is not correct. is SQL Server using Dynamic Ports ? go to the server and from Server Configuration check what is the port used by SQL Server, enter that port in the connection details

check if you are able to ping the Server machine using hostname


manoj_d (BOB member since 2009-01-02)

I installed MYSQL and after modifying the repository creation scripts I was able to create a local repository and connect to it via the CMC. I have yet to apply any patches maybe after that the connection to SQL Server will work. The CMC is running on SQL Server. For now I am able to login via DS Designer and run jobs.


vmontana (BOB member since 2006-08-25)

I had the same issue using SQL Server 2008 R2 Express Edition. I resolved the issue by enabling TCP/IP in the SQL Server Configuration Manager, it is off by default:

[list]Launch the SQL Server Configuration Manager
Expand “SQL Server Network Configuration”
Select “Protocols for MSSQLSERVER
Edit the properties of “TCP/IP” and set “Enabled” to “Yes”
Restart SQL Server[/list]


RichRod :us: (BOB member since 2007-02-28)

I have resolved the issue.

It turns out on the boxes that have firewall enabled the sql server instance gets a dynamic port allocated instead of default of 1433. This could happen because of some other reason too.

One needs to remove the dynamic port that has a value “0” to fixed port 1433 to get this work.

The instructions at this link clarify and resolve the issue

http://msdn.microsoft.com/en-us/library/ms177440.aspx

Enjoy


srinathpedi (BOB member since 2007-09-25)

Thanks srinathpedi this was exactly what I was looking for, TCPIP being switched off in SQL Server.


jardinsa :australia: (BOB member since 2006-10-26)

Apologies for the thread resurrection.

If you have an SQL Server repository with dynamic ports enabled on the SQL Server Instance then is there a comprehensive way to register it without fixing the port?

I have worked around it by using the currently allocated dynamic port, but why does it need the port anyway? I can connect to the repository using Data Services Repository Manager without providing it - why does CMC need it to register it? If the SQL Server instance is restarted and the dynamic port changes does CMC actually care?

(BODS4.2SP07 running on Windows Server 2012).


DanDensley :uk: (BOB member since 2009-05-12)