Sometimes for security reasons the traffic on 1433 or 1432 SQL Server ports is blocked. In this case the custom port is used to connect the Server Instance. When using the SIte Admin for SharePoint to discover the SharePoint Farm that used Custom SQL Server Port for the database, you will received following error:
(Error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Source: Microsoft OLE DB Provider for SQL Server SQLSTATE: 08001 Native error: 17 Server: Error state: 1 Error severity: 16 Strings: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. )
Despite the necessary permission had been granted for the account to access to SharePoint Content Database.
When opening up the QsSPDiscovery.log, there is error:
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: SPSProductVersion, value: 184557544
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: Host, value: SHAREPOINTSERVER
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: ConfigDBVersion, value: N/A
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: ConfigDBServer, value: SQLSERVER\INSTANCE
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: ConfigDBName, value: SPS01_Config_db
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: ServerComment, value: HR SSL Portal
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: SchemaVersion, value: 6.0.2.6568
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: RegSuccess, value: TRUE
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: Port, value: 80
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: operatingSystem, value: Windows Server 2003
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: operatingSystemVersion, value: 5.2
1/12/2008 5:42:58 PM (GMT+10:00) 4672 3464 field name: operatingSystemServicePack, val
SQL Server that host SharePoint Content Database does not use the default port
WORKAROUND :
In order to enable the connection from client machine (where the SiteAdmin Console is installed), the aliases should be specified. You need to have the SQL Server Client Tool installed.
1. Go to Start | Run, type "cliconfg" & click OK
2. In the General Tab, select the protocol TCP/IP to enabled the protocols
3. Select Alias Tab, click Add...
4. On the Add Network Library Configuration,
- the Server alias field, type in SQLSERVER\INSTANCE
- Network libraries, select TCP/IP
- On the Connection Parameters, enter the SQLSERVER\INSTANCE in the Server name field, uncheck the dynamically determine port.
- At the Port Number field, specified the custom port used
5. Click OK to save the settings
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center