here LT5534 by Linear Technology
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 BlogEngine.net'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.
- Firmware-Upload and here
- NodeMCU & DHT22 get startet enable modules
- WiFi IoT
ESPESY hat Probleme beim Login in WLAN mit Passwortlänge > 8 Zeichen.
Man kann das WLAN auswählen, aber man gelangt immer wieder auf die Auswahlseite zurück.
Abhilfe: WLAN-Repeater als Bridge mit Passswortlänge = 8 Zeichen –> geht!