Lorenzo Barbieri @ Weblogs.Asp.Net

Shake your thoughts... Confessions of a MSF and .NET addicted
        www.lorenzobarbieri.info

Activities

My articles<br><font size="1">(in English)</font>

My articles<br><font size="1">(in Italian)</font>

My old articles<br><font size="1">for <a href="http://www.objectway.it">ObjectWay SpA</a> (in Italian)</font>

My projects

The Italian Blog...<br><font size="1">(my Official Italian blog)</font>

Server installation problems...

Today I've seen a very strange problem.
I've finished the development of a couple of Web Services and I needed to put them in production.
I've received the Windows 2000 Server already locked down, with a lot of tweaks, permissions changed, IIS Lockdown, URLScan, registry tweaks, etc...
I've installed the .NET Framework after the locking (it was the procedure that they used for every other environment), but this time there was no way to have ASPX and ASMX pages served.
Everytime I try to read ASPX or ASMX pages, I receive "You are not authorized to view this page" without any information in Event Log, IIS Log and URLScan.log.
Also nonexisting pages return the same "not authorized" error.
I've tried some knowledge base articles, I've restored the permissions on the directories, removed URLScan and IISLockDown, but nothing happened.

Tomorrow I'll receive a new server not already locked down, I will install the .NET Framework, and then we will try to lock down the system.

Perhaps we will find what is breaking the connection between IIS and ASP.NET...

The moral of the story is: "Do your work BEFORE others can break it!!!!"

UPDATE: We've reinstalled .NET on a fresh installation of Windows 2000 Server and applied exactly the same tweaks and locks, and... EVERYTHING WORKS  :-)

Posted: Dec 04 2003, 05:11 PM by barbilor | with 4 comment(s)
Filed under: ,

Comments

Larry Johnson said:

It kind of sounds like the Framework may not have installed correctly. I had this problem once when I originally installed .NET on my XP Pro machine, because due to my inexperience with it at the time, I installed the .NET development environment before installing IIS.

Anyway, go into the properties of your website in IIS. Check the 'Documents' tab. If you don't see any "default.aspx" or "index.aspx" entry, then IIS isn't recognizing the extension.

There is a "fix" utility called "aspnet_regiis.exe" in your Framework directory. The Frameword directory should be somewhere like, "...WINNT\Microsoft.NET\Framework" but your particular system may vary.

There are several available parameters for the utility that you can read at this link on MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfASPNETIISRegistrationToolAspnet_regiisexe.asp

Hope this is applicable to your problem.
Good Luck!
# December 4, 2003 1:03 PM

Lorenzo Barbieri said:

I've already checked that ASP.NET DLL is correctly installed in IIS.
I've also already used aspnet_regiis and it tells me that everything is ok, but i'm still not authorized to use my Web Services...
# December 5, 2003 3:43 AM

Chakresh Maheshwari said:

Try to use aspnet_regiis with i option.
It will work
# January 27, 2004 1:58 AM

Lorenzo Barbieri said:

I've tried aspnet_regiis -i, but it didn't work.
# January 27, 2004 7:27 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)