- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
Configuring and Running Classic ASP Applications on IIS 7
Wednesday, June 24, 2009
Copy the asp files to inetpub\wwwroot folder, set up the Database, install the COM+ DLLs and run the application, Yes this would have worked if you are working on IIS 4, 5, 6 but not anymore. There are more steps to do when you are working with IIS 7. And most of them are tricky and can make seasoned developer run around for solutions.
Below is the list of some trouble shooting tips, in no particular order while configuring and running classic ASP applications in IIS 7.
- Enable ASP - Classic ASP is not installed by default on IIS7, so we need to enable it first. http://learn.iis.net/page.aspx/562/classic-asp-is-not-installed-by-default-on-iis-70-and-iis-75
- “Enable Parent Paths” – Is disabled by default so we need to enable it before we can use parent paths. http://support.microsoft.com/default.aspx?scid=kb;en-us;332117
- Classic ASP script error messages are no longer shown in a Web browser by default so if you want to see them, it needs to be enabled. http://learn.iis.net/page.aspx/564/classic-asp-script-error-messages-are-no-longer-shown-in-a-web-browser-by-default
- And in IE options, “Advanced” tab uncheck “Show friendly HTTP error messages”.
- “Server object error ‘ASP 0178 : 80070005′” error message when you attempt to connect to a database results page created in FrontPage, This is due to NTFS permissions check here to solve it. http://support.microsoft.com/kb/315454
- BUG: ASP error 80070005 “Server.CreateObject Access” when you create a Visual Basic component. This is again due to insufficient permissions, Check here for solution. http://support.microsoft.com/default.aspx?scid=kb;EN-US;q278013
- PRB: Server Object Error ‘ASP 0178′ Instantiating COM Object. Again a permissions issue, Check here for solution http://support.microsoft.com/default.aspx/kb/198432
- “Enforce access checks for this application” - In Component Services, COM+ application properties, under “Security” tab uncheck the “Enforce access checks for this application” check box. Also make sure in the “Identity” tab, “Local Service” account is selected.
- If you are using “myinfo.dll” in your application, copy it to the “C:\Windows\System32” folder and register it using “regsvr32”. OR if you do not have a need for it just take out the references from your application.
- Turn off UAC [User Access Control] check if required.
- Make sure the you create a application pool for classic ASP application with the settings “.Net Framework version” as “No Managed Code” and “Managed Pipeline” as “Classic” .
- “Enable Windows Authentication” in IIS, under “Authentication”.
Rohit is a Microsoft Certified Solution Developer (MCSD.Net) with more than 10 years of experience. He has expertise in...
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6
- Why You Should Get the WCM Experts Involved Early