tracker issue : CF-3784829

select a category, or use search below
(searches all categories and all time range)
Title:

Conflicting connection information. When the instance name is specified, it is invalid to specify the port number.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Chris Walker / Chris Walker (Chris Walker)

Created: 07/03/2014

Components: Database

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final / CF10 u14

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 8.1/64bit

Vote Count: 1

Duplicate ID:	CF-3836721

Problem Description:When attempting to connect to a local MS SQL server the system reports it is not necessary to include the port number when using the instance name

Steps to Reproduce: Attempt to connect a local SQL repository to the coldFusion server with a named instance of the server and the port specified

Actual Result:Conflicting connection information. When the instance name is specified, it is invalid to specify the port number.

Expected Result:Success!

Any Workarounds: FULL STOP.  THIS IS DEAD IN THE WATER.  Seems not to happen on external databases where the server is a URI or an IP Address.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3784829

External Customer Info:
External Company:  
External Customer Name: AviationJunkie
External Customer Email:  
External Test Config: My Hardware and Environment details:  Microsoft Windows NT 6.2 (9200),  MS SQL 10.50.4000.0, COLDFUSION 11

Attachments:

  1. July 03, 2014 00:00:00: 1_Screen_capture.jpg

Comments:

I believe this issue stems from JDBC 5 SQL server drivers. According to Progress.com: Fixed in hot fix 5.0.1.000060. Refer to 000001201, "Connect for JDBC hot fix download and install instructions" for instructions on how to download and install the hot fix. This enhancement requires the hidden connection option "allowPortWithNamedInstance" to be set to "true" and the JDBC SQL Server driver version must be 5.0.1.000060 or higher to allow a successful connection.
Comment by External U.
11712 | July 03, 2014 05:56:21 AM GMT
Resolved: netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN
Comment by External U.
11713 | July 03, 2014 09:50:35 AM GMT
Just ran into this issue, today. Within the ColdFusion Admin, Data & Services > Datasources > Microsoft SQL Server. Click "Show Advanced Settings". In the "Connection String" box, enter "allowPortWithNamedInstance=true"
Comment by External U.
11714 | November 06, 2014 05:04:02 PM GMT
Regarding "Duplicate ID CF-3836721", #CF-3836721 is currently unviewable. Can #CF-3836721 please be made viewable? When I attempt to view #CF-3836721, it says "The information requested is not found". Thanks!, -Aaron
Comment by External U.
11715 | November 16, 2014 02:12:43 AM GMT
I experienced this on a move to CF11 and unlike the poster here it did work on CF10 with update 15 when I had an instance name and a port. When I moved to CF11, the same datasource would not verify and gave that error. I also applied CF11 update 4 and still got the error. As a workaround, simply removing the port on the datasource (on CF11) fixed the problem and the datasource verified. I also tried removing the port number in CF10 and it still worked.
Vote by External U.
11719 | February 24, 2015 12:17:05 PM GMT
When did the CF10 to CF11 upgrade on a similar server, I decided to remove the port number on CF10 before doing the upgrade. After the upgrade, the datasources were not working but I discovered that the conversion had put in a port of 0. When I removed that, it fixed the problem.
Comment by External U.
11716 | February 24, 2015 12:36:16 PM GMT
Thansk MdSheker, your solution worked. Within the ColdFusion Admin, Data & Services > Datasources > Microsoft SQL Server. Click "Show Advanced Settings". In the "Connection String" box, enter "allowPortWithNamedInstance=true"
Comment by External U.
11717 | March 26, 2015 11:42:11 AM GMT
Can anyone verify this works when using datasource.cfc? We create our data sources programmatically and I cannot get this to work using setMSSQL().
Comment by External U.
11718 | January 22, 2016 11:58:53 AM GMT