Problem setting up ColdFusion on Windows 7 and IIS 7.5

Discussion in 'Third-party applications' started by DancesWithFascists, Aug 17, 2012.

  1. Using Windows 7 version 6.1 Build 7601 Service Pack 1 on a Dell N5110 Laptop running an Intel Core i5-2430M CPU @ 2.4 GHz and 6 GB RAM, 64-bit OS.

    Under Control Panel > Programs > Turn Windows Features On and Off > Internet Information Services I have turned on all the features and subfeatures EXCEPT for FTP Server. Internet Information Services Hostable Web Core is also turned ON though it's unclear whether it's necessary or not.

    Installed ColdFusion version 10 after enabling IIS as described above.

    Used instructions at http://learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis/ to set up and test tracing, working around all the ambiguities and errors there until tracing actually worked as described for a 404.2 error on a .asp file. THEN reset the trace to work on all 500 errors for ISAPI Extension and WWW Server.

    Ran the Web Server Configuration Tool for ColdFusion as described at http://help.adobe.com/en_US/ColdFus...Sc3ff6d0ea77859461172e0811cdec18a15-7ffb.html to configure IIS for ColdFusion in Windows. Then these parts of the configuration were possible to verify at C:\ColdFusion10\config\wsconfig :
    Verify your IIS configuration

    Verify that the following folder was created: cf_root/config/wsconfig/number.

    To set the connectionpooltimeout and reuseconnectioncount click on Advanced Setting tab. The option to enable buffering and verbose debugging is available on the same page.

    Configuring IIS:

    Creates a folder 1 in cfroot\config\wsconfig, that contains all connector-related files.

    Creates a virtual directory Jakarta in cfroot\config\wsconfig (in IIS).

    Adds an entry, tomcat, under the ISAPI FILTERS. This points to cfroot\config\wsconfig\1\isapi_redirect.dll.


    Some of the parts of the verification process were skipped, for the reasons described :

    Adds an entry, tomcat, to cfroot\config\wsconfig\1\isapi_redirect.dll with permission allowed under ISAPI and CGI Restrictions. It is applicable for global sites in IIS manager.

    No kind of 'entry' is possible for the specified .dll at that location under its Properties, nor can permissions be allowed under Properties for anything remotely resembling 'ISAPI and CGI Restrictions'. There is nothing resembling "Global Sites" in IIS manager either where this information might be found.

    Adds the following isapi handlers: cfcHandler, cfmHandler, cfmlHandler, cfrHandler, and cfswfHandler.

    The logical place for these "handlers" would be in IIS but there is no description provided for where they might be found and searching around provides no clues so this is impossible to verify as well.

    For debugging issues, set the log level to debug, in the isapi_redirect.properties file present in the cfroot\config\wsconfig\1\ directory.

    This was done and these are the contents of that file:

    extension_uri= /jakarta/isapi_redirect.dll
    log_file= C:\ColdFusion10\config\wsconfig\1\isapi_redirect.log
    log_level= debug
    worker_file= C:\ColdFusion10\config\wsconfig\1\workers.properties
    worker_mount_file= C:\ColdFusion10\config\wsconfig\1\uriworkermap.properties
    iis_buffer_enable= true

    To disable webserver buffer, change the is_buffer_enable to false in the cfroot\config\wsconfig\1\isapi_redirect.properties file. Disable webserver buffer if you want cfflush to work over an IIS connector. If your application does not use cfflush, set it to true for increase in the performance.

    This was left on 'true' as shown in the file contents above.


    THIS IS THE ERROR NOW OBTAINED at http://127.0.0.1/CFIDE/administrator/index.cfm:
    Server Error in Application "DEFAULT WEB SITE"

    Internet Information Services 7.5
    Error Summary
    HTTP Error 500.0 - Internal Server Error
    The page cannot be displayed because an internal server error has occurred.

    Detailed Error Information
    Module IsapiModule
    Notification ExecuteRequestHandler
    Handler cfmHandler
    Error Code 0x800700c1
    Requested URL http://127.0.0.1:80/CFIDE/administrator/index.cfm
    Physical Path C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\index.cfm
    Logon Method Anonymous
    Logon User Anonymous
    Failed Request Tracing Log Directory
    C:\inetpub\logs\FailedReqLogFiles



    The supplied path C:\inetpub\logs\FailedReqLogFiles is a nonresponsive link but there are .xml files created in that subdirectory such as C:\inetpub\logs\FailedReqLogFiles\W3SVC1\fr000015.xml which contains this information:
    Request Diagnostics for http://127.0.0.1:80/CFIDE/administrator/index.cfm

    STATUS_CODE 500, 46 ms, GET (2012-8-16, 16:59:5:778)

    -Request Summary
    Site 1
    Process 8472
    Failure Reason STATUS_CODE
    Trigger Status 500
    Final Status 500
    Time Taken 46 msec
    Url http://127.0.0.1:80/CFIDE/administrator/index.cfm
    App Pool DefaultAppPool
    Authentication anonymous
    User from token NT AUTHORITY\IUSR
    Activity ID {00000000-0000-0000-6F00-0080000000FB}

    No. EventName Details Time
    1. i GENERAL_REQUEST_START

    SiteId="1", AppPoolId="DefaultAppPool", ConnId="1610612845", RawConnId="0", RequestURL="http://127.0.0.1:80/CFIDE/administrator/index.cfm", RequestVerb="GET"

    16:59:05.778
    2. — GENERAL_SET_REQUEST_HEADER

    HeaderName="AspFilterSessionId", HeaderValue="", Replace="true"

    16:59:05.778
    3. i GENERAL_ENDPOINT_INFORMATION

    RemoteAddress="127.0.0.1", RemotePort="50289", LocalAddress="127.0.0.1", LocalPort="80"

    16:59:05.778
    4. i GENERAL_REQUEST_HEADERS

    Headers="Cache-Control: max-age=0
    Connection: keep-alive
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    Accept-Encoding: gzip, deflate
    Accept-Language: en-us,en;q=0.5
    Host: 127.0.0.1
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
    DNT: 1
    "

    16:59:05.778
    5. i GENERAL_GET_URL_METADATA

    PhysicalPath="", AccessPerms="517"

    16:59:05.778
    6. i HANDLER_CHANGED

    OldHandlerName="", NewHandlerName="cfmHandler", NewHandlerModules="IsapiModule", NewHandlerScriptProcessor="C:\ColdFusion10\config\wsconfig\1\isapi_redirect.dll", NewHandlerType=""

    16:59:05.778
    7. i USER_SET

    AuthType="", UserName="", SupportsIsInRole="true"

    16:59:05.778
    8. i GENERAL_SEND_CUSTOM_ERROR

    HttpStatus="500", HttpSubStatus="0", FileNameOrURL="500.htm"

    16:59:05.824
    9. i GENERAL_FLUSH_RESPONSE_START 16:59:05.824
    10. i GENERAL_RESPONSE_HEADERS

    Headers="Cache-Control: private
    Content-Type: text/html; charset=utf-8
    Server: Microsoft-IIS/7.5
    X-Powered-By: ASP.NET
    "

    16:59:05.824
    11. — GENERAL_RESPONSE_ENTITY_BUFFER

    <!--- some text removed to meet arbitrary 10K character limit posting here --->

    Server Error in Application "DEFAULT WEB SITE"
    Internet Information Services 7.5

    Error Summary
    HTTP Error 500.0 - Internal Server Error
    The page cannot be displayed because an internal server error has occurred.


    Detailed Error Information

    ModuleIsapiModule
    NotificationExecuteRequestHandler
    HandlercfmHandler
    Error Code0x800700c1


    Requested URLhttp://127.0.0.1:80/CFIDE/administrator/index.cfm
    Physical PathC:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\index.cfm
    Logon MethodAnonymous
    Logon UserAnonymous
    Failed Request Tracing Log Directory<a href="file://C:\inetpub\logs\FailedReqLogFiles">C:\inetpub\logs\FailedReqLogFiles</a>


    Most likely causes:
    IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.


    Things you can try:
    Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click <a href="http://go.microsoft.com/fwlink/?LinkID=66439">here</a>.


    Links and More Information
    This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
    <a href="http://go.microsoft.com/fwlink/?LinkID=62293&amp;IIS70Error=500,0,0x800700c1,7601">View more information &raquo;</a>
    Microsoft Knowledge Base Articles:
    294807

    "

    16:59:05.824
    12. i GENERAL_FLUSH_RESPONSE_END

    BytesSent="6414", ErrorCode="The operation completed successfully.
    (0x0)"

    16:59:05.824
    13. i GENERAL_REQUEST_END

    BytesSent="6414", BytesReceived="348", HttpStatus="500", HttpSubStatus="0"

    16:59:05.824
    +Expand All

    Errors & Warnings
    No. Severity Event Module Name


    There is nothing under Errors & Warnings. Dead Stop. Nothing Else To Do except Ask For Help. Hoping someone here can provide some guidance.

    TIA
     
  2. curtis

    curtis Winhost Staff

    We don't offer coldfusion here at Winhost so none of on the staff would have any experience with it. Not sure if our customers have experience in coldfusion either.

    You may want to ask adobe or search on the web for coldfusion resource sites.
     
    Last edited by a moderator: Oct 14, 2015
  3. Well the problem seems to be more about getting IIS to work right, with ColdFusion just incidentally the thing for IIS to choke on in this case. Isn't there a way to get IIS to divulge WHY it is throwing a 500 error? The standard instructions for tracing work but not completely, revealing no meaningful diagnostic information.
     
  4. Elshadriel

    Elshadriel Winhost Staff

    You can try enabling Detailed Errors using IIS7 Manager.
     

Share This Page