IIS 6 - Application Protection (LOW)

Hopefully someone has some insight into this situation.

We currently have an intranet that runs on an IIS 5 box. In the IIS 5 box you can set Application Protection to LOW (IIS Process).

We are testing out IIS 6 on Windows .NET Server 2003 Beta/

We currently have some ASP code that calls ASPExec that when it runs I get the following error : ERROR: Could not create process

I have been asking around and our Systems guys seems to think that it has to do with setting the Application Protection Level to Low. Now in IIS 6 I don't see any kind of setting for this. It seems to have gone away.

Any thoughts on this problem. Does this make sense?

Thanks

Josh
JoshFinkAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nuclear_eclipseCommented:
I have had similar issues when I originally migrated from Win2k to .Net RC1 with my PHP sites.  Although I am not versed in ASP itself, I may be able to offer some advice:

-Open the IIS manager eihter through Administration Tools or from Manage My Server, depending on how your server is set up.
-Open the Web Service Extensions folder
-Make sure that both the Active Server Pages and the ASP .Net extensions are enabled
-If they are, then go to the properties of the individual site, and then proceed to the Home Directory tab
-Make sure that Executable Permissions is set to either Scripts Only or Scripts and Executables
-Click the Configuration button and make sure that ASP pages have their own ISAPI mappings created, and also make sure that the mappings are pointing to the correct ISAPI dlls.  I apologize that I cant tell you what they should be, as I said above, I do not work with ASP, so I am unsure of the correct mappings.
-If all that doesnt change anything, there may be specific code that is incompatible with the new ASP.Net.  I attended one of Microsoft's Developer Conferences on the new ASP.Net when they had one in my hometown, and the way they put it, it sounded as if there might be issues when upgrading...

I hope these tips help you, if not, hopefully someone else will have a little more experience with ASP than I do...

- Nuclear_Eclipse
0
JoshFinkAuthor Commented:
Thanks for the help. I do appreciate it.

The strange thing is I keep mucking around with it and all of a sudden it starts to work. 20 minutes later it stops.. Very strange. I think it has something to do with permissions for either the IWAM or ISUR user.

I might just go back to Win2K as I know it works right out of the box.. Very strange, huh?

Thanks again

Josh

PS.. Any more suggestions are welcome as I believe I have done all of the above except for it's own ISAPI mapping. But then again I don't know the correct DLL's for those.
0
nuclear_eclipseCommented:
Ya, my problem with PHP frustrated me so bad at first that I reverted to loading 2k.  Luckily, I had thought to create a dual-boot with the old 2k OS and the new Beta, so it was as easy as rebooting, but once I took the time to figure it all out, it started working and I have been using RC1 ever since, its really great.

Anyways, I hope someone can help you out more than I did, good luck.

- Nuclear_Eclipse
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

JoshFinkAuthor Commented:
Ok.. The only way I've gotten this to work (in the interim, not a safe solution) was to set both IUSR users in the administrator group. It really shouldn't be this hard though.. I'll keep looking.

Thanks

Josh
0
JoshFinkAuthor Commented:
Found a fix. Since ASPExec uses cmd.exe we actually need to give specific permissions for the web user to use cmd.exe as it is locked down.

How about that??

Josh
0
JoshFinkAuthor Commented:
Can I get points refunded on this, I found the answer myself.

Thanks

Josh
0
moduloCommented:
PAQ-ing the question and refunding 30  points

modulo

Community Support Moderator
Experts Exchange
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.