We’re upgrading to Data Services 3.2 from DI 11.7.
Also we’re moving from Oracle Local Repositories to Local Repositories in SQL Server 2005 cluster (on an instance).
Management Console gives the error:
There’s nothing wrong with TCP/IP.
However, Management Console can’t connect on port 1434 (the SQL Server service port for the ‘sql2005’ instance). This port is dynamic, so will change if we restart our SQL Server cluster. We can connect on another port number (3419), which seems very odd. I don’t really want to have to reconfigure Mgmt Console every time we restart the SQL Server cluster.
Any idea why DS3.2 Mgmt Console won’t connect to that 1434 port number? Anyone point me towards places to look? Or am I not giving enough detail?
My guess is that few people (here on these forums) have changed the port, nor are people using Named Instances of SQL Server, so you may be forging new ground here.
Maybe try creating a formal ODBC connection in control panel (on the job server) to the repo database, and then use that connection instead in the DS admin configuration… it might insulate DS from that complexity?