Questions[asp](server)

I am trying to migrate a classic ASP application from a Windows Server 2003, IIS6 server to a Windows 2008, IIS 7 server.

The ASP page comes up fine, but the first time it tries to use our .NET interop DLL, it fails with the following error in the IIS logs:

2012-01-06 18:50:41 X.X.X.X POST /downloads.asp |27|ASP_0177_:_8000ffff|Server.CreateObject_Failed 80 - X.X.X.X Mozilla/5.0+(Windows+NT+6.1;+rv:8.0)+Gecko/20100101+Firefox/8.0 500 0 0 0

The corresponding line in the ASP page is:

Set subscription = Server.CreateObject("DLLNAME")

I successfully registered the DLL using RegAsm.exe, and confirmed by using a VBscript that successfully called CreateObject. I've also ensured both NETWORK SERVICE, IUSR_MACHINENAME, and IUSR have read access to the DLL location and the HKEY_USERS...Internet Settings\Zones.

Any thoughts?

On my Windows 7 machine, I've just installed IIS and it should work, but doesn't!

Well, finding it anyway... and when I run inetmgr.exe the command prompt doesn't recognize it.

C:\Windows\system32>inetmgr.exe
'inetmgr.exe' is not recognized as an internal or external command,
operable program or batch file.

What should I do to fix this to ensure IIS works properly? Also, the IIS Manager doesn't appear in the start menu.

Should I re-install it from scratch?

thanks

Namely how is setting read/write permission for this account different from giving read/write access in the IIS (Windows 2003, so it should be IIS6 if I am not mistaken).

Here is the issue: It looks like we had a security sweep and as a part of that IUSR account lost write access everywhere. A whole bunch of legacy ASP sites didn't like that at all...

My very surfacish understanding is that it is enough to deny write access in the IIS console to protect a website from someone just dropping random files into it, and IUSR access only has effect on the application scripts running server side, and thus can be safely given write access back.

edit:

The applications in question obviously require write access to their own web folders, otherwise this wouldn't be an issue at all. Question is how to configure IIS/application to both satisfy security and make them work. My first instinct was to change account which is used to run the app pool. However that is already set to NETWORK_SERVICE, and that guy already has full access to folders in question.

Say you have a public ASP.NET (or Classic ASP) application on IIS with a script/page that needs to write or update files in a specific folder that is located within the web publishing folder tree.

1) What is the proper way to set this up?

My main concern is that I want to let the ASP/ASP.NET apps write to a folder, but I don't want regular http users to be able to PUT files into it.

We've started to see instances on our Intranet server where for any page the server just responds with the error page 'HTTP/1.1 New Session Failed'. It seems we can fix it by running IISRESET but this feels like we're only treating the symptom.

The server is a virtualised server running IIS6 on Windows Server 2003 with 0.5Gb of RAM. Our Intranet is written in ASP, but we also have ASP.NET 2.0 applications running on the web site. The site is set up for Anonymous and Integrated Authentication.

What causes IIS to get into this error state? Could the server be saturated with requests i.e. we need to scale out and move some applications onto another server?

I've seen KB210842 but I'm not sure it applies as that is applicable to IIS 4