I've had *.taf mapped to ISAPI as per the instructions for some time now. I currently have it mapped in the main webserver group and the individual site but assume one would be enough.
Enable 32bit is false and the pools recycled. And iis_terascript.dll is allowed in the ISAPI and CGI restrictions list. Current error message is: HTTP Error 500.0 - Internal Server Error There is a problem with the resource you are looking for, so it cannot be displayed. Most likely causes: The path to the ISAPI Filter is incorrect. 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. Wayne On 27 Mar 2014, at 1:12 am, Robert Shubert <[email protected]> wrote: > Yes, that should be disabled. You don’t want to serve *.dll > > What does need to be in that list is one for *.taf which maps to the > IsapiModule. You use the Add Module Mapping… button to add it. > > After changing the Enable 32-bit Applications you need to restart the pools > (called recycling) or IIS. > > You should also see the entry in ISAPI and CGI Restrictions (server level) > for the iis_terascript.dll set to Allowed. > > Robert > > > > From: Wayne Irvine [mailto:[email protected]] > Sent: Wednesday, March 26, 2014 1:07 AM > To: [email protected] > Subject: Re: TeraScript-Talk: WS12 and IIS on AWS > > > On 26 Mar 2014, at 3:48 pm, Wayne Irvine <[email protected]> wrote: > Did you set the Enable 32-bit Applications to True? Since you are using TS 7, > a 64-bit App, you should leave that set to False. > > > Changed to false in all Applications Pools. No difference. > > I went into have a look at Handler Mappings and noticed this: > <image001.png> > > Should ISAPI be disabled? I double clicked and changed permissions to Execute > which enabled it. This changed the error message to: > > HTTP Error 500.0 - Internal Server Error > There is a problem with the resource you are looking for, so it cannot be > displayed. > Most likely causes: > · The path to the ISAPI Filter is incorrect. > · 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. > Things you can try: > · Ensure that the path to the ISAPI DLL is correct. > · 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. > · 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 here. > > > > > Wayne Irvine > w: http://www.byteserve.com.au/ > p: +61 2 9960 6099 > m: 0409 960 609 > > > To unsubscribe from this list, please send an email to > [email protected] with "unsubscribe terascript-talk" in the body. > > To unsubscribe from this list, please send an email to > [email protected] with "unsubscribe terascript-talk" in the body. Wayne Irvine w: http://www.byteserve.com.au/ p: +61 2 9960 6099 m: 0409 960 609 ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe terascript-talk" in the body.
