"Unable to perform" issue in IIS Manager (localhost) - iis

When I'm trying to open any app in IIS Manager (local machine) like CGI, Handler mappings etc. I got an error There was an error while performing this operation:
I'm unable to find out this issue.

I installed the hosting bundle again. i.e. repair and then checked if the iis_usr has all access for the wwwroot folder.
This resolved the problem for me.

Related

How can I fix IISNode internal server error? listen EACCESS permission denied

I added a node application as a website on IIS with a web config file and whenever I try to browse the website it gives this error:
Error on web browser.
I have tried using the taskkill command to stop the process listening to this port and I also tried giving IIS_IUSRS user full permission on the root folder, but this issue persists
web.config file:
config file image
So I was able to find my way around this issue. I removed the application from IIS and I used pm2 to start the node application and I didn't encounter any error after using this approach.

NopCommerce error SevenSpikes.Nop.Plugins.Core.dll' is denied

I got this error continually on my nopCommerce website.
Application startup exception:
System.Exception: Plugin 'Seven Spikes Core'.
Access to the path
'C:\Inetpub\wwwroot\mywebsite\Plugins\bin\SevenSpikes.Nop.Plugins.Core.dll' is denied.
I have tried disabling overlapped recycle in the application pool and still, I still get the same error occasionally. What's the permanent fix?
I'm using nopCommerce version 4.20 version.
It is because of the shadow copy of plugin which is resolved at the nopCommerce4.2. To resolve the error you need to follow below steps
You need to stop app_pool and the website.
Remove the all .dll from the plugin bin folder(your website==>Plugins==>bin)
At the appsetting.json(root directory of the website) change "UsePluginsShadowCopy" :
true to "UsePluginsShadowCopy": false
Start the app_pool first then website.
It should resolved the error. I faced same problem and get solution by following the above steps. You do not need to disable overlapped recycle.
After I copied the site folder to a new folder I gave this folder the APP-POOL permisions:
'IIS APPPOOL\My-IIS-Site-Name' then - restart IIS.

CF 11. 'ColdFusion is not defined' error using ColdFusion.Ajax.submitForm

Just re-installed everything on new laptop after old one crashed. Upgraded from CF9 to CF11 in the process. Running IIS on Windows 10. Local site is working fine, except when it comes to submitting a form with ajax.
ColdFusion.Ajax.submitForm('registerForm', '/register_action.cfm', callback,errorHandler);
I have <cfajaximport> at the top.
I have an IIS virtual CFIDE directory
pointing to C:\ColdFusion2016\cfusion\wwwroot\CFIDE
Mapping in CFAdmin is correct
There was not issue with CF9. But I notice CF11 has its scripts directory OUTSIDE the CFIDE directory on the same level (directory named "cf_scripts"), whereas CF9 has the scripts INSIDE the CFIDE directory.
Before I stuff things up, has anyone any pointers in the right direction?
SOLUTION
For the benefit of others, I did the following:
CFAdministrator Default ScriptSrc directory: /CF_SCRIPTS
IIS Virtual Directory: CF_SCRIPTS pointing to C:\ColdFusion2016\cfusion\wwwroot\cf_scripts\scripts\
Create a virtual directory in IIS that points to that scripts folder.
In the ColdFusion administrator, under the Server > Settings tab, make sure the Default ScriptSrc Directory name matches the IIS virtual directory name you created.

Setting up Bonobo 5.0.0 with Windows authentication

I'm trying to install Bonobo 5.0.0 on Windows 7 + IIS 7.5 with Windows authentication.
When I go to the homepage (http://domain/bonobo), I'm prompted for my Windows username/password and after that it redirects back to the root to look for a route called windowsAuthCallback:
http://domain/windowsAuthCallback?id=xxx
Obviously this gives me a 404 error.
I have authentication set to 'anonymous' in IIS and 'Windows' in the Bonobo web.config and I'm not sure what I'm doing wrong.
UPDATE
Not sure if this is related... I have an existing Bonobo installation on the same server and I'm installing Bonobo 5 fresh as a new application. After running into the issue I described, trying to open the original Bonobo app gives me the following error:
Unable to find an entry point named 'sqlite3_open_interop' in DLL 'SQLite.Interop.dll'.
Restarting IIS resolves the issue and I can access my old Bonobo app again.
This commit should resolve the windowsAuthCallback redirecting to root: https://github.com/jakubgarfield/Bonobo-Git-Server/commit/852563e2e1f969abca008b8be798c265a52f4d81
A workaround for this issue along with a link to the commit that resolves it can be found on the following page:
https://github.com/jakubgarfield/Bonobo-Git-Server/issues/333

Config Error Failed to decrypt attribute 'password'

Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error Failed to decrypt attribute 'password'
Config File Unavailable (Config Isolation)
When i run my app im getting this error and i couldn't find any solution please help?
I resolved the issue. The problem was C:\Windows\System32\inetsrv\config\applicationHost.config file. In the config file, I deleted username and password definitions for applications and it worked well.
I had the same issue after clone a Web Server.
Solution:
Source Server:
aspnet_regiis -px "iisConfigurationKey" "C:\temp\iisConfigurationKey.xml" -pri
aspnet_regiis -px "iisWasKey" "C:\temp\iisWasKey.xml" -pri
Destination Server:
aspnet_regiis -pi "iisConfigurationKey" "C:\temp\iisConfigurationKey.xml"
aspnet_regiis -pi "iisWasKey" "C:\temp\iisWasKey.xml"
And, at the final, copy applicationhost.config from the source server to destination server.
This is one of those mystery errors. For me, the issue occurred when we cloned a development server. When I went to reconfigure some the sites in IIS on the cloned server, one of the sites threw this error. You need to delete all the sites that shared the same app pool in IIS and recreate them.
I fixed this by disabling Anonymous Access in the application, then re-enabling it immediately. No IIS restart necessary.
I had the same problem and I changed the Physical Path under the website's advanced settings to a dummy path then changed it back, then it started working.

Resources