500.19 on IIS 7, Cant log on locally

22

I don't know where sholud I ask this...

I've seen this issue and I think the answer should me close to that, but seems that I can't still do this.

The funny thing is the same (I think) was done by me in another server w/ IIS 7 a year ago or so, without further trouble. It could be also that I don't remember so much of it. I have an Apache server running on port 80 (That can't be changed)

This is what I've done:

Integrated AppPool was an issue on the other server I've placed so I've tried to change the

  • Default AppPool to a Classic .Net
  • The WebApp Pool to a Classic .Net

The User is also mandatory on the Webservice so I'm placing a Service Account that impersonates for any anonymous (or not) user that might access so I have

  • The ServiceAccount as Administrator of wwwroot and subfolders
  • The ServiceAccount as Impersonated by default in the Default Web Site
  • The ServiceAccount as Impersonated in every Web App I need
  • Shared r/w the folder with the ServiceAccount

Also

  • I've tested the access and both Authorization & Authentication works marvelous.
  • I've restarted the app, the site and the IIS multiple times without success.
  • Checked the Event Log without finding anything useful.
  • Modified applicationHost.config getting into more troubles than solutions.

This is what I get when I try to see the App Settings at IIS7

--------------------------- Application Settings ---------------------------

There was an error while performing this operation.

Details:

Filename: \?\C:\Windows\system32\inetsrv\config\applicationHost.config

Line number: 165

Error: Can not log on locally to %SystemDrive%\inetpub\wwwroot as user MyDOMAIN\MyUser with virtual directory password

--------------------------- OK ---------------------------

This is what I see when I go to my page (an asmx)

HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information Module IIS Web Core Notification Unknown Handler Not yet determined

Error Code 0x80070569

Config Error Can not log on locally to C:\inetpub\wwwroot as user MyDOMAIN\MyUser with virtual directory password

Config File Unavailable (Config Isolation)

Requested URL http://localhost:8080/myApp/MyWebService.asmx

Physical Path

Logon Method Not yet determined

Logon User Not yet determined


@Edit: 0x80070569 Drove me to see that The service account weren't logging on as a Service (as it should), nor as a Batch process.

It was a Security Setting that should be touched, a group policy object has to be set to the account (in the Example MyDOMAIN\MyUser). And that's an access that only the area of IT Security can grant.

Even when this was changed the problem remained still.

asp.net
iis-7
asked on Stack Overflow Jul 18, 2011 by apacay • edited May 23, 2017 by Community

3 Answers

53

The accepted answer didn't work for me.

But when I followed the below steps, my issue was resolved:

  1. Go to your IIS manager.
  2. Click on Sites
  3. Right click on Default websites, Go to Manage Website and then click on
    Advanced Settings
  4. Set your physical path credential to Specific user with credentials
  5. Restart IIS

Note: You may also need to reenter the credentials in the application pool, if the system password has been changed recently.

answered on Stack Overflow Mar 1, 2017 by Sibeesh Venu • edited Feb 18, 2020 by Kate Orlova
7

It actually was a secpol.msc Policy What was blocking the web access. The ServiceAccount wasn't a Service one.

As in the edit that I posted IT Security gave me the privileges to set it a*s a Service Account*, but that alone just wouldn't do the trick.

In the Advanced Settings of the webSite

Physical Path Credentials Logon Type, Batch logonMethod was selected.

And the service account still wasn't with the privileges to run as a Batch Process.

And that was it.

Not only the service account, but also The Run as a Batch Job was necessary.

answered on Stack Overflow Aug 3, 2011 by apacay
0

Sometimes it causes by changing administrator password or changing user access. After that application pool cannot access to local user. One of the most stupid solution for this problem is remove website and application pool then make another website. This solution helped me.

answered on Stack Overflow Aug 31, 2020 by keivan kashani

User contributions licensed under CC BY-SA 3.0