IIS not displaying asp.net files

[gav12345]

Hi,

I'm running IIS6 on Windows 2003 server and am having problems viewing asp.net (and asp files). I can view htm files without any problems. This is irrelevent to where they are placed, for example:

http://localhost/test.htm

http://trasapp18/businessobjects/enterprise11/testgjn.htm

http://trasapp18/test.htm

...all work OK, but as soon as I place an asp or aspx file in the same place, I get the generic 'The Page Cannot be Displayed' error. No error number.

To fix this I have tried:

Running the Aspnet_regiis.exe utility
Allowing .net web service extensions in IIS
Running the synciwam.vbs vb script.

Does anyone have any ideas why IIS doesn't like asp.net pages? Many thanks, Gavin

 

[vbkris]

one more info, after the request is made are you able to make out the aspnet_wp.exe process on your server's processes???

Known is handfull, Unknown is worldfull

 

[gav12345]

Hi vbkris - No, that process isn't showing in the Task Manager. Thanks, Gavin

 

[Turkbear]

Hi,
Did you set the security on the site to allow .NET?
This is disabled by default..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[gav12345]

Thanks Turkbear - Do you mean changing the Web Service Extensions from 'Prohibit' to 'Allow' for .net? If not, where else would I change the security to allow .net?

Gavin

 

[vbkris]

Hi Gavin,

Did you also check to see for a process called w3p.exe?

If either is not there that means that the .NET engine is unable to startup. Therefore the question by TurkBear.

Normally the ASP.NET account has a separate Account name called ASPNET that is responsible for execting the pages. Check wether this account is enabled...

Known is handfull, Unknown is worldfull

 

[gav12345]

Thanks vbkris. The w3p.exe process is not showing in the Task Manager, but the ASPNET account looks OK. Is there a way to start the w3p.exe and aspnet_wp.exe processes manually to see if this is the problem?

Gavin

 

[gav12345]

For what its worth, this was eventually resolved by uninstalling the Web Component Adaptor (Control Panel, Add/Remove programs, Business Objects XI > Change), uninstalling IIS and ASP.NET (Add/Remove Windows Components), reinstalling IIS and ASP.NET, then reinstalling the Web Component Adaptor.

It took two attempts of the above to eventually get this working and I still don't really know what was causing the problem...but its working now so I'm happy.

Gavin