Blog J.Schweiss

Infosammlung zu .NET- Programmier-Themen & Elektronik


clock Oktober 31, 2016 07:10 by author Administrator

here LT5534 by Linear Technology

Jeelink & NodeRed

clock Oktober 31, 2016 03:29 by author Administrator

Raspberry Pi: Wie können Daten mit JeeLink mit Node-RED eingelesen werden

NodeRed install

Atmel SAMD21

clock Oktober 30, 2016 23:14 by author Administrator

here and intro

Smart Home mit FHEM

clock Oktober 21, 2016 05:38 by author Administrator


Homeautomation mit ioBroker

clock Oktober 16, 2016 19:41 by author Administrator



Technologie nodejs und Javascript.


Funksteckdosen in FHEM schalten

clock Oktober 15, 2016 02:21 by author Administrator


fhem-Installation auf RASPI

CSharp + IOT

clock Oktober 14, 2016 03:57 by author Administrator

CSharp + IOT


clock Oktober 10, 2016 04:15 by author Administrator


Error in BlogEngine - System.UnauthorizedAccessException

clock Oktober 10, 2016 03:50 by author Administrator

The app server could be running under a different account.  For example, I run plesk on my hosting machines.  I tried installing BlogEngine and giving IIS permissions to the App_Data directory.  However, this did not work, because the application pool is running under a Plesk created admin account. Therefore, Plesk is the admin of that app pool. So, I had to give the Plesk admin account full write access and it worked.

Here's some steps to follow to troubleshoot.

1) In IIS, right-click on your website and go to Properties.
2) Click on the Home Directory Tab.
3) Your application pool is listed at the bottom.
4) Click cancel and return to IIS.
5) In IIS, under Application Pools, right click on the pool that your BlogEngine is running in.
6) Click the Identity Tab.
7) You could have Predefined or Configurable selected. No matter, but which ever one is selected is the account that you need to give write permissions to your App_Data dir.

If the above doesn't work, another solution would be create a "no-remote-login" admin account.  The account can only login to the server if they are logging in locally.  Therefore you don't have to worry about people logging into your server as admin.  Then run the app under the created account's identity.

1) Load the Users snapin (or right-click on My Computer, Click Manage, then click Local Users and Groups)
2) Create new user (remember username and password, you'll need this in a minute)
3) Check "User cannot change password" and "Password never expires"
4) On the MemberOf tab, add the user to the Administrators group.
5) On the Dial-in tab, choose "Deny Access" and "No Callback"
6) On the Terminal Services Profile tab, check "Deny this user permissions to log on...."
7) Click OK or Apply
8) Now, in's web.config file add the line inside your system.web element:
            <identity impersonate="true" userName="the username you typed above" password="the password you typed above" />

While the second option is not the most ideal, sometimes its necessary depending on your hosting environment and need of environment resources.

Über den Author

Windows, Server, Programming, .Net, Tools, Arduino, RaspberryPi, IoT  & more

Sign in