Skip to main content
P
patrickp41016649
New Participant
June 20, 2017
Question

CF 2016 IIS Site Administrator Returns Blank Page

  • June 20, 2017
  • 1 reply
  • 2454 views

The core server localhost:8500/CFIDE/administrator brings up a page just fine.

localhost:8250/CFIDE/ brings up a directory search, but adding administrator to the end produces a blank page with no HTML at all. administrator/index.cfm does the same. However, putting an index.cfm in the root of the IIS site directory and navigating to localhost:8250/ opens that cfm file just fine. I must be missing some property setting/permission, but I've followed the two following guides to the letter.

http://wwwimages.adobe.com/content/dam/acom/en/products/coldfusion/pdfs/coldfusion-2016-lockdown-guide.pdf

ColdFusion Help | Web Server Management

Environment: Windows Server 2012 R2. The only installs on it are IIS and CF 2016, all developer settings, using coldfusion internal server..

What are my likely failure points?

This topic has been closed for replies.

1 reply

Priyank Shrivastava.
Community Manager
Priyank Shrivastava.Community Manager
Community Manager
June 20, 2017

Hi,

Are these new instances or you are running web server8250 port from the web server. Please share these details.

Thanks,

Priyank

Thanks,Priyank Shrivastava
P
patrickp41016649Author
New Participant
June 20, 2017

Hello Priyank,

In the Enterprise Manager we have the cfusion instance running on 8499 (the guides prescribed not using the default 8500 anymore). Then we have "ServerRemReview" running on 8500.

In IIS, "RemReview" is bound to port 8250. I ran wsconfig and set the connector with the following settings:

AppServer Host: localhost

AppServer Instance: ServerRemReview

Web Server: IIS

IIS Website: RemReview

Everything else was left in its defaults.

I apologize if I missed something basic. I'm the newbie in the team trying to wrap my head around this. We're trying to migrate from CF 9 to CF 2016, so I've gotten a lot of conflicting information on how it should be set up.

Priyank Shrivastava.
Community Manager
Priyank Shrivastava.Community Manager
Community Manager
June 21, 2017

Hi,

Seems like ColdFusion 9 and ColdFusion 2016 connectors are mixed in IIS. First, remove the ColdFusion 2016 connector and then remove the ColdFusion 9 connector.

Once you remove the connector, please check the Handler Mappings for the individual website and make sure there are no leftover handlers for ColdFusion. Then create the connector with ColdFusion 2016.

Please check this blog. Removing Corrupt Connector Dependencies from IIS | Adobe ColdFusion Blog

Thanks,

Priyank

Thanks,Priyank Shrivastava
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices