IIS 6 site --> IIS 7: request for any resource in site yeilds error, can't read web.config, Error Code 0x8007007b

[Ken Fine]

Hi, I'm having some trouble testing an application on my new IIS7
installation. Any page or resource I try to render returns the error below,
and I get similar errors when I try to configure the site in the IIS
console.

Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x8007007b
Config Error Cannot read configuration file
Config File \\?\c:\Inetpub\wwwroot/ni\web.config

I'll reproduce exactly how I got to this point: it might suggest a clue:

1) I set up a DFS replication on the wwwroot of my old machine and
replicated the wwwroot from that machine to the wwwroot on the new machine.
This wiped out a few files that were previously in place on the new machine.
Don't know if that matters or not.
2) For now the new machine, a Server 2008 machine, is set up both as a
domain controller on a legacy 2003 domain and with IIS, which is not
intended to be the production configuration. This caused the following error
when I first installed:

The Windows Process Activation Service (WAS) encountered an error attempting
to look up the built in IIS_IUSRS group. There may be problems in viewing
and setting security permissions with the IIS_IUSRS group. This happens if
the machine has been joined and promoted to be a Domain Controller in a
legacy domain. Please see the online help for more information and
solutions to this problem. The data field contains the error number.

The "event data" (I think that's the error number" is 34050780.

3) The directory I'm trying to run as an application is
c:\Inetpub\wwwroot\ni. I configured it as an application by expanding the
default web site, right clicking on the subdirectory, and filling in the
appropriate information.

4) I get this error no matter what resource I try to request. Even a static
HTML or image file yeilds the error.

5) There is no web.config file at c:\Inetpub\wwwroot\. This mirrors the
setup on my old IIS installation.

I am wondering if IIS7 has different expections about what should be in the
web.config, or if I'm doing something else wrong. I tried monkeying with the
compat mode of the AppPool, but that makes no difference. For some reason
IIS7 is not reading in my web.config.

The app is a ASP.NET 3.5 application. I don't +think+ that should mean I
need to install anything additional on a Server 2008 box, but....

Any help out there? This one shouldn't be too tough.

Thanks!

-KF

[David Wang]

Reinstall. DCPROMO. Then install IIS7 and .Net 3.5. Finally, drag/
drop your "ni" folder to the directory you want, ensuring permissions
are merged, and recreate the application in IIS7 to point to that
directory.

ACLs are different between IIS6 and IIS7, so verbatim copy/replication
and assuming "if it wasn't there before, it's not needed now" will not
be a good idea. IIS7 has distributed configuration within web.config
now, so even existing web.config will cause issues with default IIS7
installation. You'd either need to upgrade to use handlers/modules, or
revert to classic ASP.Net pipeline.

#2 looks like the main problem right now. Without IIS_IURS, IIS7 will
not be able to read anything, including .config.

Finally, there is a flipped slash in the file pathname, which I
highlighted by [[ ]]
\c:\Inetpub\wwwroot[[/]]ni\web.config

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

[Ken Fine]

Thanks very much for your help David. Are you saying I have to reinstall the
entirety of the Server 08 OS on my new server machine and re-elevate my
server to a DC to deal with this?

Couldn't I just disable replication, remove IIS7 as a role, re-add it, and
do the other steps you describe? Or did I misunderstand?

-KF

"David Wang" <w3....@gmail.com> wrote in message
news:955e9a4c-d03b-4db4...@i36g2000prf.googlegroups.com...

[David Wang]

You can do whatever you want as long as it resolves the problem #2
with IIS_IUSRS.

I do not have faith in reinstallations magically "fixing" things. You
can certainly try; I can only warn that your mileage may vary. If we
see something else that is weird after the reinstallation, then I hope
you'd understand why I would not be inclined to spend time to
troubleshoot.

It is not a commonly tested scenario to run:
1. Do something that should be after DCPROMO
2. DCPROMO
3. Uninstall #1
4. Reinstall #1
5. Ensure that #1 still works.

The testing procedure usually run:
1. DCPROMO
2. Do something that should be after DCPROMO
3. Ensure that #2 works

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

On Jun 21, 10:02 pm, "Ken Fine" <kenf...@newsgroup.nospam> wrote:
> Thanks very much for your help David. Are you saying I have to reinstall the
> entirety of the Server 08 OS on my new server machine and re-elevate my
> server to a DC to deal with this?
>
> Couldn't I just disable replication, remove IIS7 as a role, re-add it, and
> do the other steps you describe? Or did I misunderstand?
>
> -KF
>

> "David Wang" <w3.4...@gmail.com> wrote in message

> > //- Hide quoted text -
>
> - Show quoted text -

[WenJun Zhang[msft]]

Hi Ken,

I'd like to suggest you clean up IIS stuff on the Windows 2008 server and
then try the migration with MS Deploy.

Migrating from IIS 6.0 to IIS 7.0 using MS Deploy
http://learn.iis.net/page.aspx/427/migrating-from-iis-60-to-iis-70-using-ms-
deploy/

Please update here on how things are going.

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[WenJun Zhang[msft]]

Hi Ken,

Do you have any update on this issue?