I am trying to get phpMyAdmin working on a server with IIS7.5 installed. We have done the following and cannot get access to phpMyAdmin working:
MySql installed
Windows Server 2008 running IIS7.5
Followed this tutorial: enter link description here
Created a new site and added phpMyAdmin directory beneath it as an application (I can see the subdirectories of the phpMyAdmin root on this application)
Navigating to the subdomain set up for the application indicates we do not have sufficient permissions. I gave users and administrator read/write access for the site and the application:
HTTP Error 401.3 - Unauthorized
You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.
I feel like we are very close, but I am unsure what other permissions need to be set to gain access.
I'm not used to IIS 7.5, but I believe typically you would need to give the IIS user read permission on the phpMyAdmin folder, files, and subdirectory. You mention giving permission to users and administrators, but I don't think the IIS user would fall in to either of those categories.
Related
edit
I also have the same problem as an admin on a domain
I just installed SSRS locally on a machine for and I cannot access the reports I deployed. Everything was installed as admin
when going to the web portal I get this massage
Could not load folder contents
You are not allowed to view this folder. Contact your administrator to obtain the necessary permissions.
and when trying to access the web service via the config manager I get this one:
The permissions granted to user <username> are insufficient for performing this operation. (rsAccessDenied)
Additionally in the web portal I got no "manage" folder and only "my subscriptions" under the settings button .
Everything is running locally and as admin, the OS is windows 11 and the SSRS is version 15.0.1102.1002 and running in native mode.
I've looked all over the place and found out something about certificates, but almost everything in google is about access problems via remote server.
adding the URL to the trusted sites didn't help
it certainly look like you don't have permission. Are you administrator? When you were installing did you set up some users to be administrators?
Find which account is administrator and then add yourself from the SSRS site. Is there another account you can run or Run as administrator?
Another way to install again.
If you decide to install again pay attention on the page with the users.
I was configuring authentication for a third party in Sourcegraph and did a SAVE when it told me I needed to have enterprise version. I then deleted the authentication provider section in administration and saved it. Did a restart and received message 'Access to Sourcegraph is forbidden because no authentication provider is set in site configuration.' on the web page. I deleted DOCKER, deleted docker folder in /var/lib, Reinstalled docker and then did another quickstart of sourcegraph. Received the raph.same message again when I went to web page for sourcegraph. I must not be getting a fresh copy of something. Any suggestions?
I determined that there is a .sourcegraph directory in the home directory of root (the user I was logged inas when sourcegraph was installed) that contains configuration data. Wiped out that directory and then reinstalled and everything worked.
We've been working hard on a sandbox server. We installed WordPress to it from scratch. I created the database, and imported the previous database into it. The user and password both have been created.
Right now, our error is "403 Forbidden: You don't have permission to access / on this server". I can't access any of the files by typing in the server IP address,though we see and control everything as root via Putty, or manage it through FileZilla. Root is the owner of all WP files/folders.
I found this source: WPBeginner-403-Error-Fix and am currently changing the permissions on the files; the folders are done and the permissions are set to 755. File permissions are being set to 644. Out of all the resources we had referred to, it never mentioned WP requiring specific permissions. I got right onto that today. While this is running, I still get the message after the folder permissions were changed, and as the file permissions are being processed:
You don't have permission to access /wp-admin/login.php on this server.
We also had a bootstrap file located in the same place as the WP installation / contents (this was a test). The bootstrap is very much accessible: the CSS/JS folders with the supporting content can be seen if you type the ipaddress/directory for the bootstrap version... you can see the files and structure. If you type in ipaddress/boot.html, it runs it flawlessly. If we try referring to anything with WP, it does not like it and throws the 403 error.
There is no .htaccess, I read online it would generate via permalinks in the panel. But we can't even see the panel. It's currently .htaccessOLD (from when we imported our old WP contents to the dev server, from the production site), so there should be no interference.
None of us has installed WP directly, the guy who did it previously no longer is part of the company, so we are becoming lost in this process.
Edit: Plugins were disabled via renaming convention, however, WP actually regenerated this folder.
Edit (2): With the permissions set, and the plugin/theme deactivated, it still does not run due to 403.
Weird... my answer didn't post yesterday as I had thought.
So- we solved it. The permissions were set accordingly for all directories/files, the issue was the server configuration. Just triple check the server configuration file (usually httpd.conf on current servers) to ensure it points to the directory containing the WP contents.
If this is still a problem to some people, and you swear that the httpd.conf file is correct, it does not hurt to double check your directories. The directories should be permission 755. Files should be 644, excluding the wp-config.php (that ought to be set for permissions 455).
Thank you for helping us troubleshoot! We really appreciated it! :)
I am having trouble conecting to a mysql server that is runing on ubuntu 14.04. i can log into phpmyadmin and upload webpages via ftp but when i go to create a record set and define a database i get a 403 access forbiden. does any one have any ideas.
A 403 error doesn't mean your script is having trouble connecting to the database server, it means your client (the web browser) is not permitted to access the file/web page you're trying to access.
Most likely your permissions aren't set properly on the files you've uploaded by FTP. Check the owner and permissions and verify that they're appropriate for your situation (for instance, on my system files are 644 and directories are 755 and the file owner doesn't matter. Your mileage may vary).
After a fresh install of SQL Server 2012 Developer on my Windows 7 machine, I configure SSRS. Then, in IE (version 11), I try to access the SSRS server at http://(servername)/Reports. Windows asks for my username and password. Odd, because I'm an administrator. So I enter my username and password and I get this reply:
User '' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
Researching the issue, I come across a number of answers, including:
Reporting Services permissions on SQL Server R2 SSRS
SSRS 2008: User Does Not Have Required Permissions
The answers to these questions are similar:
Run IE as an administrator
Add the SSRS URL to Trusted Sites in Security tab of Internet Options
Retry SSRS URL
On success, add your user to Site Settings and Folder Settings with the appropriate permissions.
You should then be able to access SSRS without running IE as administrator
Additional workarounds include disabling UAC and repeating the steps above.
Running IE as an administrator did not work. At step 3. I got the same response as above and was never able to get to the SSRS home page.
Before disabling UAC, are there any other workarounds?
The workaround I found is from Peter O’Gorman's blog entry.
The steps above are the same, except add the URL to Local Intranet, not Trusted Sites:
Run IE as an administrator
Add the SSRS URL to Local Intranet in Security tab of Internet Options
Retry SSRS URL
On success, add your user to Site Settings and Folder Settings with the appropriate permissions.
You should then be able to access SSRS without running IE as administrator
To my pleasant surprise, this worked like a charm. Thanks Peter!
Run IE as an administrator - not Chrome. I swear I tried this before with no joy.
I don't understand why not Chrome and why administrator. Maybe Chrome somehow dismisses the elevated permissions. How does the rsManager know at what level the browser is running anyway?
Microsoft SQL Server Management Studio 12.0.2000.8
Microsoft Analysis Services Client Tools 12.0.2000.8
Microsoft Data Access Components (MDAC) 6.3.9600.16384
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 9.11.9600.17498
Microsoft .NET Framework 4.0.30319.34209
Operating System 6.3.9600
Chrome Version 39.0.2171.95 m
Same steps as Glenn mentioned previously. I also had to add user to role in two different spots once I was able to access SQL Server Reporting Services - Home. In Folder setting -> security -> new role assignment and site settings -> security -> new role assignment. I added my user as well.
http://techasp.blogspot.com/2013/06/how-to-fix-reporting-services.html
This works for Reporting Services 2008 onwards
This one has been bugging me for a while, some users have access to the report server others get this error message. While trying to resolve it with a system administrator I came across this post from microsoft support
For users to navigate to a particular folder, they must have Browser role on
all folders starting at the root folder (the folder named "/" in the
item path or "Home" in Report Manager). So you will need to grant
those permissions explicitly. By default, permissions are inherited
from the parent folder. If there are any breaks in the inheritance,
you will need to set those permission explicitly.
What we did as a administrator users, was to navigate to Reports page, then folder settings and grant the user that does not have permissions Browser rights to the folder. Use could then navigate to the home page and work their way down the tree. the sys admin hadn't granted access to the user at the home level just on the folders and reports that have access to.