Skip to main content
Inspiring
September 30, 2021
Answered

Coldfusion 2021 hotfix 2 installation. Connector started all IIS looks good index.cfm not loading I

  • September 30, 2021
  • 2 replies
  • 334 views

Worked on and ensured both Server.xml and workers. properties file resolved.  pointed both to server Ip

for host. Continues to get Internal 500 when logging into site for index.cfm. I have tried different index.cfm

under our content folder under root. For some reason .cfm not rendering.

 

I intially removed /installed Connector. was getting errors now fixed.

Triplex check IIS setting ISAPI etc all look good.

If i click on recycle site, home page load with any content showing. Just some embedded links.

at a loss. Working on this last 2-3 days.

This is a fresh CF2021 install on Windows server 2019.

CF Admin working fine, mappings/DSN for both Oracle 19c and MySql 8 testing fine.

 

txs in advance

 

Jose

    This topic has been closed for replies.
    Correct answer josed56603254

    Team, this has been resolved.

    Found an issue with connector security where worker.properties file and server.xml file updated both

    to match with server IP. final Issue once Connector was validated was a permissions issue to

    one of our Tables dealing with specific piece of cf code/variable. Site is up and functional.

     

    Ty

    2 replies

    BKBK
    Community Expert
    Community Expert
    September 30, 2021
    quote

    ... Continues to get Internal 500 when logging into site for index.cfm....Triplex check IIS setting ISAPI etc all look good.


    By @josed56603254

     

    A status 500 error is an internal server error. It suggests that all is not well with the server. 

     

    I would therefore expect that the server would log a clue somewhere. Please check the following logs and let us know what you find:

    • /ColdFusion2021/{INSTANCENAME}/logs/coldfusion-error.log
    • /ColdFusion2021/{INSTANCENAME}/logs/coldfusion-out.log
    • /ColdFusion2021/config/wsconfig/N/isapi_redirect.log (The integer N is the so-called magic number corresponding to the instance)

     

    Second idea:

    Open the following file in a text editor, and ensure that the mappings are correct:

    • /ColdFusion2021/config/wsconfig/N/uriworkermap.properties

    [ the mappings should be something like:

    /cfformgateway/* = nameOfInstance

    /CFFormGateway/* = nameOfInstance

    /flex2gateway/* = nameOfInstance

    /flex2gateway = nameOfInstance

    /cffileservlet/* = nameOfInstance

    /CFFileServlet/* = nameOfInstance

    /cfform-internal/* = nameOfInstance

    /flashservices/gateway/* = nameOfInstance

    /flex-internal/* = nameOfInstance

    /rest/* = nameOfInstance

    /restapps/* = nameOfInstance

    /connector = nameOfInstance

    /*.mxml = nameOfInstance

    /*.as = nameOfInstance

    /*.cfm = nameOfInstance

    /*.CFM = nameOfInstance

    /*.Cfm = nameOfInstance

    /*.cfm/* = nameOfInstance

    /*.CFM/* = nameOfInstance

    /*.Cfm/* = nameOfInstance

    /*.swc = nameOfInstance

    /*.cfml = nameOfInstance

    /*.CFML = nameOfInstance

    /*.Cfml = nameOfInstance

    /*.cfml/* = nameOfInstance

    /*.CFML/* = nameOfInstance

    /*.Cfml/* = nameOfInstance

    /*.cfc = nameOfInstance

    /*.CFC = nameOfInstance

    /*.Cfc = nameOfInstance

    /*.cfc/* = nameOfInstance

    /*.CFC/* = nameOfInstance

    /*.Cfc/* = nameOfInstance

    /*.cfr = nameOfInstance

    /*.CFR = nameOfInstance

    /*.Cfr = nameOfInstance

    /*.cfswf = nameOfInstance

    /*.CFSWF = nameOfInstance

    /*.Cfswf = nameOfInstance

    /*.sws = nameOfInstance

    /*.jsp = nameOfInstance

    /*.hbmxml = nameOfInstance

    !/CFIDE/* = nameOfInstance

      

    where nameOfInstance is the name you've given the instance in /ColdFusion2021/config/wsconfig/N/worker.properties]

    josed56603254AuthorCorrect answer
    Inspiring
    October 4, 2021

    Team, this has been resolved.

    Found an issue with connector security where worker.properties file and server.xml file updated both

    to match with server IP. final Issue once Connector was validated was a permissions issue to

    one of our Tables dealing with specific piece of cf code/variable. Site is up and functional.

     

    Ty

    Priyank Shrivastava.
    Community Manager
    Community Manager
    September 30, 2021

    Hi Jose,

     

    If you are getting 500 error and if yo have tried everything. Please check this setting in your IIS and see if that makes any difference. 

    1. Launch IIS

    2. Go to Application Pool>Select Application which your site is using>Right Click on it and click on Advanced Setting/

    3. Check what is the value setup in "Enable 32-bit Application", if it is set to "TRUE", make it false and it will work. If this is not the case, then we need more details to understand if there is an issue with permission which is causing the problem.

     

     

    Thanks,Priyank Shrivastava
    Inspiring
    September 30, 2021

    Ty,

     

    Tried that no difference, and worked previously with CF support Vikram resolved Connector issue we 

    were having to anser reply to my post  from BKBK. Going through various CF logs and IIS and not

    seeing anything obvious. only able to load 1 apps section of website, which is strange. Need a 

    screen share to go over.

     

    ty jose