Getting an UnauthorizedAccessException when trying to set up a new site.

Dan Soleimani asked on April 5, 2017 18:22

Just setup Kentico 10 on a new machine running Windows 7 Pro. I'm going through the tutorial now and I'm trying to set up a new site by going to Admin > Configuration > Sites > New site wizard. However, when I click on that button, I'm receiving an UnauthorizedAccessException for the path c:\inetpub\wwwroot\Kentico10\CMS\App_Data\Persistent\newsitewizard_...._settings.dat.

There is nothing in the Persistent folder and I get this same error when clicking on the Import site or objects and Export buttons (but for a different settings.dat).

I went to that folder and gave full access to the IIS_IUSR account and verified the same for NETWORK SERVICES. That did not work, so I just went to the Kentico10 folder and did that same. Still not working. Any ideas?

Thanks! Curt

Recent Answers

Zach Perry answered on April 5, 2017 18:33

Is the App pool that the site is running under using the NETWORk SERVICES account or a custom account?

0 votesVote for this answer Mark as a Correct answer

Dan Soleimani answered on April 5, 2017 18:55

Just looked and it's running under ApplicationPoolIdentity.

0 votesVote for this answer Mark as a Correct answer

Zach Perry answered on April 5, 2017 18:56

I believe that would be the account that needs access to the path.

0 votesVote for this answer Mark as a Correct answer

Dan Soleimani answered on April 5, 2017 19:06

I granted full control for IIS APPPOOL\DefaultAppPool, which is the account ApplicationPoolIdenity uses, to everything under the Kentico10 directory. Still get this same error.

I'm on Windows 7 Pro running IIS 7.5. I also applied the 10.0.16 hotfix for Kentico.

0 votesVote for this answer Mark as a Correct answer

Zach Perry answered on April 5, 2017 19:26

Verify the site is actually using the DefaultAppPool and not a custom one. If so, then your DefaultAppPool user should be correct, as long as it as the correct permissions, which it sounds like you gave it full control.

Other than that, might get lucky with restarting IIS.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.