IIS 8 error on windows server 2012 insufficient permission - credentials

There was an error when trying to connect. Do you want to retype your credentials and try again?
Details:
Filename: \?\C:Windows\system32\inetsrv\config\redirection.config
Error: Cannot read configuration file due to insufficient permissions
Screenshot:
Suddenly I have this error when trying to access my application on IIS 8! Does anyone know how to fix it?

I had a similar issue and this article helped me resolve the issue: https://blogs.msdn.microsoft.com/prashant_upadhyay/2011/09/20/unable-to-expand-server-node-in-the-iis-7-ui-with-shared-configuration/
The issue in my case was the account associated with configurationRedirection was locked, once enabled the issue was resolved.
I guess a similar issue would arise if the account did not have access to the Shared configuration folder, or if the account's password/credentials had changed.

I had the exact same error message for one of my users following a permissions change to his user account. Turned out he had an old "disconnected" RDP session on the server. Once that was signed off (via task manager) the error went away.

Related

Remote server returned an error 404 Share Point connection Manager on SSIS tool

I'm trying to read data from Share Point online. I'm using KingwaySoft SharePoint Drivers on SSIS.
I'm getting below error even though with provided credentials
what could be the reason?
do I have to change the URL pattern?
Resolved
I have added /_vti_bin/listdata.svc/ at the end of the site URL.
like :
https://company0.sharepoint.com/sites/sfinfo/IT_team/_vti_bin/listdata.svc/
Thanks
The ideal service URL that you would need to provide should include the base site and subsite, if necessary, and no other details.
Give it a try and if the error persists, please reach out to our support team with the screenshot of the SharePoint connection manager configuration.

vtiger cron sorry! attempt to access restricted file

I'm trying to run vtigercron.sh file, but i have error
Sorry! Attempt to access restricted file.
I tried to do everything as described here but it didn’t help me
https://www.vtexperts.com/sorry-attempt-to-access-restricted-file/
Vtiger Custom Module : "Sorry! Attempt to access restricted file."
Vtiger web service "sorry! attempt to access restricted file" response
As far as I understand, this problem appeared after deleting and creating a user
please help me, what else could be the problem?

Azure SignalR: HubException method does not exist

I am finding we receive this error:
Failed to invoke 'CreateChatRequest' due to an error on the server. HubException: Method does not exist.
at _this.callbacks.<computed> (chat.min.js:2060)
at HubConnection.processIncomingData (chat.min.js:2154)
at WebSocketTransport.HubConnection.connection.onreceive (chat.min.js:1881)
at WebSocket.webSocket.onmessage (chat.min.js:3922)
The method does exist. The code does work, then after a while of testing, it returns this and won't stop.
What seems to temporarily fix the issue is restarting the Azure SigR service, but it comes back. This issue does not occur when targeting local SigR during development; it only happens against Azure SigR.
According to documentation, this seems to be a catchall error when something errors up on the server but, no exceptions are being logged. I've turned on detailed errors, but that didn't change the error coming back from the server. I've also tried catching the exception and sending back a HubException to see what is going on, but that didn't change the error message either.
TIA for any help.
So the answer, for me, was that i'd checked in (to source control) my azure service's connection string, so other devs were also using this and pointing their versions of the API service at that azure service. So when i ran my code sometimes azure would hit my API service with the new method in and it would work, sometimes it would hit someone else's API service and so fail because their code didn't have the new method in.

Coldfusion 2016 - 403 forbidden error for schedule tasks

I have two schedule task which is running in coldfusion administrator. They are giving 403 forbidden error when run through coldfusion administrator. Here is the log which i get.
"Information","DefaultQuartzScheduler_Worker-8","02/22/17","10:11:00","","Task default.example - Get detail Dev triggered."
"Information","DefaultQuartzScheduler_Worker-4","02/22/17","10:11:00","","Task default.example - Get detail Live triggered."
"Error","DefaultQuartzScheduler_Worker-8","02/22/17","10:11:00","","403 Forbidden "
"Error","DefaultQuartzScheduler_Worker-4","02/22/17","10:11:00","","403 Forbidden "
The task url is running good through browser. It seems that it is something related to permission problem. I have checked the permission of coldfusion Application 'log on as' user on the CFIDE directory and task url directory. It has full control.
Can anyone guide me to solve this problem.
This post is a little old but I've happened across the same problem and I thought I'd share our solution here.
We're running ColdFusion 2016 on a dedicated Windows 2012R2 box. We have several client sites on our box and we're completely locked down using Peter Freitag's lockdown guide.
This is was a new server migration from a CF10 server on another box. Once I set up the scheduled task exactly as we had done before, I received several "403 Forbidden" responses.
The only real way to troubleshoot this is to activate the "Save output to a file" option on the scheduled task itself and save the file to a directory where your CFUser has write access to. "CFUser" of course is the Windows user your CF service uses.
My first test of the URL was through Chrome on the server and it worked just fine so my URL was valid and of public access.
When I fired the scheduled task, it said "The scheduled task ran successfully" however the results of the output file showed it didn't. In our case, an outside service called "Cloudflare" was blocking our request. The error from Cloudflare asked us to enable cookies which we can't do in a scheduled task request. In our case, our hosting provider must provide an exception for requests made from our server's dedicated IP.
Most of the time, these error are generated because of file permission issues on Windows. If you're sure that your CFUser has read & execute permission to the requested template, then you need to output the scheduled task result to fully understand the error.

IIS 6 is throwing a "500 - Internal Server Error" for some users but not others

I had written a mini App in asp classic this week. It worked perfectly on the test server connecting to the test data base. Then yesterday evening I moved it from the test server to the live server updating the connection strings to the live db.
I published it as an application to the default website in the default app pool. Then I tested it and it worked perfectly.
This morning however both myself and another user receive a 500 -internal Server error when we try and save changes to the database(there appears to be no issue reading from the db) yet my two other collogues have no issue at all.
Even more odd is that the same thing is happening on the test server where the code hasn't been changed in weeks. But this morning I cannot commit to the db from there either.
I have attempt to enable more detailed error tracking and logging but the property options for the server are seem unavailable when i tried to set up custom Active Server Pages (ASP) error pages off online tutorials.
The server is used by a lot of people so I was wondering is their a permission issue depending on the user that restricts writting to the database. Or something else that may have changed to allow some users to write data and others to receive the error.
Im very knew to IIS so it may be something glaringly obvious that I haven't considered.
Thanks
This article should help you:
In earlier versions of IIS, error messages from classic ASP scripts
were sent to a Web browser, by default. Because these error messages
might reveal sensitive information to malicious users, IIS 7 and above
disables this feature by default. When your classic ASP scripts
encounter an error in IIS, you receive the following error message by
default:
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.

Resources