« Previous Next »

• 07-28-2008, 4:40 AM

  riggit Joined on 07-18-2008, 8:38 PM Posts 3

  Framework v1.1 Installation Reply Contact Hi people, I followed the article, http://learn.iis.net/themes/iis/pages/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008 about installing framework V1.1 but now get the error: Calling GetProcAddress on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll" failed I have set the filter to be "allowed" in the "ISAPI & CGI Restrictions" section.  Any ideas please? Cheers!

  Tags: error.NET 1.1

• 07-28-2008, 9:37 AM

  In reply to

  ma_khan Joined on 03-16-2008, 8:26 PM Posts 681

  Re: Framework v1.1 Installation Reply Contact Have you configured the Ignore section Handler in the correct machine.config file?? any other error message that you come across? Do you have ISAPI extension support installed from the windows setup?? Regards, MA Khan http://www.iisworkstation.com “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

• 07-29-2008, 4:51 AM

  In reply to

  riggit Joined on 07-18-2008, 8:38 PM Posts 3

  Re: Framework v1.1 Installation Reply Contact Hi there, Thanks for getting back to me. I followed the article I referred to which included the ignore section and enabling the ISAPI extension. When you say "correct machine.config" file, is there a choice, as the article only mentioned one specific file? Also, the article didn't mention using windows setup to enable ISAPI  extension support. Where is this? Surely ISAPI support is already enabled to allow the ISAPI for framework v2.0? One further thing: Other applications which are set to use a different (v2.0) app pool are also throwing the same error. More detail on the error............................... Detailed Error Information Module IIS Web Core Notification Unknown Handler StaticFile Error Code 0x8007007f Requested URL http://www.blahblahblah.co.uk:80/ Physical Path C:\inetpub\wwwroot\blah Logon Method Not yet determined Logon User Not yet determined Most likely causes: The ISAPI Filter has dependencies that are not available on the Web server. 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: Try running Reskit tool "depends" on the ISAPI DLL. 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

• 07-31-2008, 4:46 PM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 2,343	Re: Framework v1.1 Installation Reply Contact This is because aspnet_isapi.dll is not an ISAPI filter but an ISAPI extension - the asp.net ISAPI filter is aspnet_filter.dll - looks like somehow you have configured the ISAPI extension dll where the ISAPI filter dll should go. Anil Ruia Senior Software Design Engineer IIS Core Server

• 07-31-2008, 6:22 PM

  In reply to

  riggit Joined on 07-18-2008, 8:38 PM Posts 3	Re: Framework v1.1 Installation Reply Contact Hi anilr, Yes, thank you for replying! I realised my mistake, but forgot to update the forum.  It works fine now thanks.  Regards

• 09-03-2009, 2:56 PM

  In reply to

  smurtuza Joined on 11-26-2008, 9:51 PM Posts 5	Re: Framework v1.1 Installation Reply Contact Hello there, I'm end up getting the same error: Calling GetProcAddress on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.ll" failed. Only things I'm working on Windows Server 2008. Please help. Thanks.

• 09-03-2009, 4:01 PM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 2,343	Re: Framework v1.1 Installation Reply Contact The same cause and solution applies to you too. Anil Ruia Senior Software Design Engineer IIS Core Server

• 09-03-2009, 4:04 PM

  In reply to

  smurtuza Joined on 11-26-2008, 9:51 PM Posts 5	Re: Framework v1.1 Installation Reply Contact anilr: The same cause and solution applies to you too. I'm not sure exactly what resolved this issue. I added the ASP.NET 1.1 (c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll) as an ISAPI filter. And modified the machine.config. The issue still exists. Please advise.

• 09-03-2009, 4:22 PM

  In reply to

  smurtuza Joined on 11-26-2008, 9:51 PM Posts 5

  Re: Framework v1.1 Installation Reply Contact anilr: The same cause and solution applies to you too. Hello, Misunderstood the answer. The ASP.NET 1.1 is already "Not Allowed" Under ISAPI and CGI Restrictions. I get the following error now: Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Source Error: Line 26: Line 27: Line 28: Line 29: Line 30: Source File: C:\Web Sites\Polaris\web.config Line: 28 Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded. WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Please advise. Thanks.

• 09-03-2009, 4:26 PM

  In reply to

  smurtuza Joined on 11-26-2008, 9:51 PM Posts 5

  Re: Framework v1.1 Installation Reply Contact Posted from google chrom messed up.  Here you go again  Hello, Misunderstood the answer. The ASP.NET 1.1 is already "Not Allowed" Under ISAPI and CGI Restrictions. I get the following error now:  Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Source Error: Line 26:    </compilers> Line 27:       <assemblies> Line 28:         <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/> Line 29:         <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> Line 30:         <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>   Source File: C:\Web Sites\Polaris\web.config    Line: 28 Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded. WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

• 09-03-2009, 4:48 PM

  In reply to

  smurtuza Joined on 11-26-2008, 9:51 PM Posts 5	Re: Framework v1.1 Installation Reply Contact Nevermind. The issue was related to Ajax Extension. Thanks for the help.

• 10-28-2009, 10:10 PM

  In reply to

  branko56 Joined on 10-29-2009, 2:06 AM Posts 2	Re: Framework v1.1 Installation Reply Contact Im experiencing a HTTP 500.19 Error trying to load a .Net 1.1 App in IIS 7 on a Windows 2008 x64 Server. Can anyone verify if this is possible, I've read mixed responses where some are saying that it works and some not. Any help would be much appreciated. Web Development Sydney | Led Downlights

• 10-29-2009, 12:50 AM

  In reply to

  anilr Joined on 05-23-2006, 6:13 PM Redmond, WA Posts 2,343	Re: Framework v1.1 Installation Reply Contact asp.net 1.1 is fully supported on ws08/iis7 - can you provide more details of the error either by making a localhost request or by using failed request tracing. Anil Ruia Senior Software Design Engineer IIS Core Server