tracker issue : CF-3197134

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

wsconfig issues on IIS7 servers with more than 52 bindings on a single site

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/LowImpact

Reporter/Name(from Bugbase): Matt Frew / Matt Frew (MDFrew)

Created: 05/23/2012

Components: Installation/Config, Connector

Versions: 9.0.1

Failure Type: Non Functioning

Found In Build/Fixed In Build: 9.0.1 /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 0

Problem Description:
If you have an IIS server with more than 52 bindings on a single site, the wsconfig tool will not recognize the site.

Steps to Reproduce:
setup IIS7 site with more than 52 bindings on a single site.  Open wsconfig tool GUI, and try to add a mapping.

Additionally, if you already have several sites, with applicable bindings, and then exceed the 52 binding limit on any one of them, the GUI will not operate properly, and a wsconfig -list will reflect inaccurate output as well (in our case, we saw the final site listed 4 times).

Actual Result:
Any server with at least 1 site that has more than 52 bindings, the wsconfig tool does not properly list currently configured sites, and will be unable to add additional wsconfig mappings.

Expected Result:
Should list all sites, and be able to configure any sites - even those with more than 52 bidings

Any Workarounds:
remove bindings?

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

Watson Bug ID:	3197134

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: MDFrew
External Customer Email:  
External Test Config: My Hardware and Environment details:

5 total IIS 7 sites; 4 instances of ColdFusion.  all sites have wsconfig mappings.  When site 5 went over 52 bindings, we found ourselves having issues listing the currently configured sites, or configuring any more sites.

Attachments:

Comments:

After thinking about this more, it's also possible that the issue isn't with a certain number of bindings to a particular site, but the number of characters in said bindings. I haven't tested this, or confirmed the number of characters in our IIS bindings...
Comment by External U.
19269 | May 23, 2012 03:48:35 PM GMT
This is due to the large number of bindings on the site . This looks to be an issue with AppCmd which we use internally to get the sites info . Please refer to http://forums.iis.net/t/1164443.aspx?error+when+running+appcmd+list+site .
Comment by Asha K.
19270 | January 17, 2014 07:01:58 AM GMT
I've hit this too. I suspect if there's something with your current approach that's being blocked by shortcomings of a third party dependency, you need to find another way to sort it out.
Comment by External U.
19271 | September 03, 2014 03:48:27 AM GMT
Closing as deferred, since the bug is releated to a ThirdParty. We will be tracking this during a future release.
Comment by Immanuel N.
19272 | December 03, 2014 03:52:52 AM GMT