I have set up a new SSRS 2019 site with HTTPS & DNS. When I am connecting to the site through the https://ComputerFQDN/Reports then everything works just fine. When I try to connect through DNS to https://DNSName/Reports then the main page comes up and everything functions, until I try to run a report and then I get a 404 error. I can't figure out what setting I am missing or why all the reports work with the FQDN but fail with DNS alias.
Certificate is good and has the FQDN + DNS entries.
Tried with multiple DNS entries and get the same error.
Tried multiple browsers with same results and multiple computers.
I have checked that the DNS entries are both in the URL ACL and the RSReportServer.config files.
Server is configured to only use HTTPS.
Server is not running IIS.
This is an on-prem install and not in the cloud.
SQL 2019 with an Always On High Availability cluster.
I've read everything I can find, but so far I have not been able to find an answer to this problem.
Problem resolved. The DNS entries were not properly input into the URLACL for ReportServer.
When looking at the "netsh http show urlacl" command we noticed that the /Reports entries were present for the DNS entries, but were not present for the /ReportServer entry. Once we added the entries for the /ReportServer then it started working correctly.
Related
We are currently working on transferring websites to our own plesk environment from third party hostings. we start with the website first and then the rest. Now we have the problem that domain names whose dns points to the same plesk server can no longer mail them to each other. We have already disabled the DNS on the plesk server because it is provided externally, but it doesn't matter.
If we have the website running on the same server and want to email each other, the following error message appears:
server error 5.1.1. User unknown in virtual mailbox table
Does anyone have experience with this?
I am trying to deploy an Always Encrypted app to Amazon AWS. There is a 2016 RDS database and a Windows Server 2016 hosting the ASP.NET 4.6 app.
On the Windows Server, when the application is run under Network Service or the Application Pool Identity, we get what I'm pretty sure is this exact problem.
Our Error:
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
We tried the solution in that post and it didn't work
We tried the solution in this post and couldn't get the powershell script to return enything except runtime exceptions. I am not very familiar with powershell so maybe I don't understand the script.
If we import the certificate to the Andministrator account, and run the IIS app pool with the Administrator account then everything works fine (not a connectivity issue or anything)
We tried importing the certificate to the local computer "Personal" certificates and giving the application account full control of the keys
We tried importing the certificate to the local computer Trusted Root Certification Authorities (as suggested in a s/o post somewhere).
We tried running certmgr with "runas" for both the DefaultAppPool and Network Service account, but when prompted for the password did not know what that would be (blank password did not work). I even looked up the DefaultAppPool password as suggested here and according to that output the password is blank.
So far nothing (apart from running the app as Administrator) as worked and we're at a loss what to try next. We've looked high and low for some sort of "Microsoft Official Deployment Guide" but all that is out there is tutorials on how to get Always Encrypted working in a local dev environment, nothing about server deployment.
When you originally created the Always Encrypted Keys for the SQL database did you generate them in the Current User Certificate Store or the Local Machine Certificate Store? It turns out its really important to place them under Local Machine. This was the issue for me when I tried to deploy my web app to our web server. No matter where I installed the certificate on the server, SQL was still looking for it under Current User which IIS cannot see and Manage Private Key does not appear for this store so you can't assign IIS user accounts to it (at least I couldn't).
Once I'd temporarily reset my table fields to plain text, deleted the master and encryption keys and regenerated them under Local Machine on my PC, and exported the certificate, it installed into the Local Machine/Personal store just fine and all I had to do was give IIS_IUSRS permissions using "Manage Private Key" to clear the remaining "Keyset does not exist" error. Hope this saves someone else a day of googling.
I've never used Parallels' Plesk before and I'm trying to get my site up and running. I was using MAMP as a local server and everything worked fine, but now getting in on Plesk doesn't seem to be working.
I've connected a domain name (toptasty.gr) to the server, I've set "toptasty.gr/" as the document root (it doesn't seem to allow a default root), and inside that directory I have all my files, including an index.php.
But when I try to see my site, Chrome tells me the DNS can't find the site. I'm out of ideas, what am I doing wrong?
Thanks
Plesk creates a root called /httpdocs where you need to place your web files. With regards to DNS issue I would say that you have setup DNS in Plesk only. You will need to add or edit your DNS details to your hosting providers DNS or if your Domain registrar allows DNS you will need to add detail there. i.e www points to your Plesk server IP. N.B. Even though you have DNS in Plesk it is not controlling your domains DNS.
I had 2 GAE apps running wordpress and connecting to a single cloud SQL instance.
As of just a few minutes ago I'm guessing both apps can not longer connect.
My IP address is whitelisted and I'm able to connect to the SQL instance without an issue, it's just the App Engine instances that are having issues.
The error is the standard WordPress error "Error establishing a database connection"
We have not changed anything, maybe someone from Google can chime in?
So far I've tried rebooting the Cloud SQL instance which did not resolve the issue.
I resolved the problem. The issue was that the MySQL user has to have a 'wp_user'#'localhost' account. You can't just have a 'wp_user'#'%' which seems odd because % is a wildcard so you'd think it would match everything. But somehow with the way GAE authenticates with Cloud SQL it needs to have the localhost user.
And because of the caching configuration the cause of this issue must be a change I made with the MySQL users a number of days ago. And the error only surfaced today. Gotta love caching.
I use a Apache server as frontend balancer. So I also pass requests to a SQL Server Report Server.
The main URL is SSL secured, so the ProxyPass through the RS works with basic auth.
The report server has a interesting issue. Most of the links in the report server seems to be hardcoded http://. With that issue, many links you click on the /reports URL gives you a "Bad Request (Invalid Hostname)" from the Apache front end server.
You can browse reports, you can open them, but if you click e.g. the root link on top or the view details link to switch the list mode, then the report server uses http://yourserver/reports/... which results in an error. Correct links are https:// in this setup.
Link which are not http:// hardcoded works so far.
I opened a support ticket at Microsoft already which escalated to redmond to the dev team. The result was... this is by design and can't be changed. Is MS really so censored? Anyway. Did anyone face the same situation and got a workaround to fix that?
I am not that familiar with Apache config, but maybe is there a way to do a URL rewrite within the Apache? So if the Apache gets an http://myfrontendurl/reports/... it replaces the request with https:// ?
I'd recommend deactivating the http access from the Reporting Services Configuration tool and seeing what happens.