08-29-2009 10:22 AM
I've chased my tail for hours on this. Time to toss it over the fence ...
We have a new Windows 2008 server that we're setting up to host our v7.2.2 database with SQL 2005. After we did some tweaking, we did finally get two test clients to connect (using SQL Server Mgt Studio) to the new SQL Server registration on the W2008 machine. This part appears to work, except that the green light for the new SQLServer Reg does NOT light up in the clients ...
The v7.2.2 Connection Manager on the new machine uses SQL Client v9.0. SLX Admin opens on the server with a Datalink using this connection just fine.
HOWEVER, the other slx datalinks from other machines simply refuse to see the new server. There is nothing in the Server drop down in the datalink, and if I type in the server's name, the link doesn't see any databases either.
What am I missing? Raw sql connects (SQL Mgt Studio) from clients to the server with sysdba, but I can't get the SLX connector to work. I suspect some sort of OS security (one client is XP, the other is W2k Server), but I don't know what it would be. Anybody want to take a stab at this?
08-29-2009 03:49 PM
08-31-2009 09:08 AM
08-31-2009 09:35 AM
From my KB:
1 - OLE DB provider: 1706 UDP/TCP
Changed in openrda.ini or slxlocalservers.xml (6.2 and up)
2 - SalesLogix Server OLE DB port: 1707 UDP/TCP (always one greater than the OLE DB provider port, used for server lists, stored procedure calls)
3 - 51101 TCP (License Pinging, can be changed in the datalink manager but NOT recommended)
4 - Database Server: 1433/1434 (mssql default connect port, can be changed in the mssql client)
5 - Web Server OLE DB port 1025/other for inbound http, including groupmanager and mailmerge data (RDS and SOAP)
6 - Reports Server OLE DB port 1025/other for inbound http
7 - Attachments(Documents) /Library "Server": Attachments and library documents are reached through shared folders,.
NetBios by default uses:
135 TCP/UDP rpc
137 TCP DNS
445 TCP/UDP ds
Note: Ports 138 and 139 are used by SalesLogix to get attachments
also.. here's a sample script for managing Win2008 ports - NOTE: These are not teh correct ports but a sample script for managing the firewall:
1 - Start Notepad.
2 - Copy and paste the following code into Notepad:
@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer"
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection"
@echo Enabling conventional SQL Server Service Broker port 4022
netsh firewall set portopening TCP 4022 "SQL Service Broker"
@echo Enabling Transact-SQL Debugger/RPC port 135
netsh firewall set portopening TCP 135 "SQL Debugger/RPC"
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh firewall set portopening TCP 2383 "Analysis Services"
@echo Enabling SQL Server Browser Service port 2382
netsh firewall set portopening TCP 2382 "SQL Browser"
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh firewall set portopening TCP 80 "HTTP"
@echo Enabling SSL port 443
netsh firewall set portopening TCP 443 "SSL"
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh firewall set portopening UDP 1434 "SQL Browser"
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE
3 - Save the file as a .txt file by using the following name: OpenSqlServerPort.txt
4 - Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat
Before you run the OpenSqlServerPort.bat script, you must copy the script to the computer which has the firewall and then run the script on that computer.
To run the script, follow these steps:
A - Click Start, click Run, type cmd, and then click OK.
B - At the command prompt, use the cd command to navigate to the folder in which you saved the OpenSqlServerPort.bat file.
C - To run the OpenSqlServerPort.bat script, type OpenSqlServerPort.bat at the command prompt, and then press ENTER
08-31-2009 10:24 AM
08-31-2009 10:40 AM
I ran into this a few weeks ago. I tried it a few days later and the client saw & connectd to the server. So try rebooting the client, or at least restart the SLX services on the client.
08-31-2009 12:10 PM