"Unable to Connect to the Remote Server" when connected via .NET ReportingService web service call - sql

I have reporting services running on SQL Server 2008 inside the domain. I'm able to hit http://localhost/reportserver without error. I can hit the same site from the web box (also in the domain name) using the internal ip of the DB box (192.169.X.X/ReportServer/ReportService.asmx.) I've looked in the SSRS logs and I see these hits being properly recorded, no errors.
However.. I have a website that uses the .NET ReportingService class to make a connection to SSRS. Using the same credentials as before, I get "Unable to connect to the remote server."
I've checked, there's no firewall active. Quadrupled checked the config in the web site to make sure it has the proper credentials and service URL for SSRS. There are also no hits in the SSRS logs when I'm trying to connect via .NET, so something is most certainly blocking access.
I've Googled my fingers bloody, and would seriously love some help. I'm sure it's some small thing, I just can't think of it.

The following change worked for me:
Remove the SSL configuration
1.1. Reporting Services Configuration Manager;
1.2. Web Service URL (click on Advanced button and then remove the SSL configuration);
1.3. Report Manager URL (click on Advanced button and then remove the SSL configuration);
Edit the file rsreportserver.config, normally it's in the path C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\
2.1. find out the Key SecureConnectionLevel;
2.2. change the Key's value from "2" to "0";

Could be your reporting services is exposed only to the private ip and your localhost. Try setting your domain name's static ip to the configuration. I've added a SSRS Url configuration link for your quick reference.

The following worked for me:
1. Remove the SSL if configured.
2. Go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config
3. In rsreportserver.config Change the SecureConnectionLevel value from "2" to "0"

The following worked for me: I Removed the SSL and set it to 0 vs 2 in the path
G:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer file is reportserver.config file.
Basically it was previously configured with SSL at port 443 but the server has been moved to another domain, and did not know where to go to get a new SSL certificate for this domain,
So i removed the SSL config in the reporting services configuration GUI and then remove it also in the reportserver.config file.

Make sure your report URL ends with /Reportserver/ (For the purpose of .NET code calling). Also keep in mind that you should use complete URL i.e. It should include servername and domain.
Check this link

I like the other solutions however in my instance I had to update the following. For some reason or another the service wasn't able to use 127.0.0.1, localhost, or any of the other IP addresses assigned to the computer, this method however worked.
Open "Report Server Configuration Manager"
Web Service URL
Click on Advanced Button
Click the IP entry that I wanted to edit.
Click "Host Header Name" and type in the fully qualified name for the server.
Report Manager URL
Click on Advanced Button
Click the IP entry that I wanted to edit.
Click "Host Header Name" and type in the fully qualified name for the server.
After the above were done both URLs in "Web Service URL" and "Report Manager URL" were able to work once correct credentials were passed to the server.

Related

Changed Server Name Now Can't Connect to Configuration Database SharePoint 2010

We recently changed the name of the server that SharePoint 2010 Foundation was running on and now we get the following message when trying to launch the central administration application:
"Cannot connect to the configuration database"
I looked up some resources and some noted to try stsadmin and run the renameserver command, but that didn't work. The result read that the "Operation was successful".
Any ideas
I figured it out.
Needed to do the following (fyi. adding a sql server alias didn't work for me).
1) Add a record to the host file that directs the localhost IP (127.0.0.1) to the old server name.
2) Add registry entries to allow the host entry to be recognized (if they don't exist you'll have to add them).
Computer\hkey_local_machine\system\currentcontrolset\services\lanmanserver\parameters
OptionalNames = OldServerName
Computer\hkey_local_machine\system\currentcontrolset\control\lsa\msv1_0
BackConnectionHostNames = OldServerName

VisualSVN Server : get /svnindex.xsl forbidden while accessing from browser

We have configured the visualsvn server in remote machine, while accessing the repository from the browser in our local machine, we are getting the below error in the internet explorer browser
'The XML page cannot be displayed'
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later
In the server machine's Event viewer, we found the log 'get /svnindex.xsl forbidden'.
Please note that we are able to connect the repository in TortoiseSVN & other subversion command line tools.
Is any setup or permission is needed to browse the repository in the browser ?
The account that runs VisualSVN Server service (the account is "Network Service" by default) must have Read & Execute permissions to %VISUALSVN_SERVER%. It seems that in your case the account does not have Read access to %VISUALSVN_SERVER%htdocs or %VISUALSVN_SERVER%htdocs\svnindex.xsl. Check the permissions in order to solve the issue.
Read the article KB37: Permissions required to run VisualSVN Server for more information.

Starting up Worklight Server

I am trying to run a simple HelloWorld app on my MacBook using Eclipse Luna and I am getting this message:
The current server configuration is set to "localhost". Therefore the
Worklight build uses the primary IP address of this computer
(???.???.?.???) instead. It is recommended to set the server
configuration to use the fully qualified hostname or IP address of
this computer. To configure the setting, in the "Servers" view
double-click the Worklight Development Server entry and edit the "Host
name" field.
Clicking the Worklight Development Server opens a sub menu with different files. I believe that I need to replace localhost by my IP address. Which file and which entry need to be modified?
It is only a recommendation and typically in most cases for local development there is no need to change this value.
If you still prefer to change it, it is where the message says so.
Open the Servers view and double-click on the "Worklight Development Server" entry (no need to expend it):
I just solved the same problem. I had to change the Host Name to the name of my PC and it worked.
#Simon, Can you do a DNS flush on your mac once and give it a try. Sometimes DNS flush causes some sort of unwanted issues which doesnt resolve the ip address and acts funny
refer :- link

How do I restore a missing IIS Express SSL Certificate?

After setting up HTTPS in IIS Express, according to such articles as this and this, I am unable to actually load an IIS Express site using HTTPS. In Chrome, I am only getting:
This webpage is not available (with error code "ERR_CONNECTION_RESET")
...and in IE I am only getting:
Internet Explorer cannot display the webpage
...when I follow the directions in those articles.
It appears this has to do with the fact that the "IIS Express Development Certificate" that IIS Express installs automatically has been removed. How do I get this certificate reinstalled?
Windows 10 users: Repair is only in the Control Panel, not in the Add Remove programs app. I typically run appwiz.cpl to launch the old control panel applet and run repair from there.
Windows 7 and 8.1:
After going to Add/Remove Programs and choosing the "Repair" option on IIS Express, the certificate has been reinstalled and I can now launch IIS Express sites using HTTPS.
The certificate is back:
And I can now launch the IIS Express site using HTTPS:
For Visual Studio 2015, IIS Express 10, Windows 10, these options didn't work for me. IIS Express 10 didn't have a repair option.
I managed to solve the problem using the IisExpressAdminCmd.exe command available at C:\Program Files (x86)\IIS Express.
From an elevated command prompt run:
cd C:\Program Files (x86)\IIS Express
IisExpressAdminCmd.exe setupsslUrl -url:urlToYourSite -UseSelfSigned
Replacing urlToYourSite with your url.
e.g.
cd C:\Program Files (x86)\IIS Express
IisExpressAdminCmd.exe setupsslUrl -url:https://localhost:44387/ -UseSelfSigned
After that I closed IIS Express and restarted my site from Visual Studio and it prompted to automatically trust the self-signed certificate.
Also note that for IIS Express to work with SSL, the port used needs to be in the 44300 through 44399 range (http://www.iis.net/learn/extensions/using-iis-express/running-iis-express-without-administrative-privileges).
So, if you're using IIS Express in Visual Studio, make sure the port selected is in the required range:
vs setting for iis express
Sometimes this error is because of a different certificate installed for localhost. If that is the case, there is no need to restore the IIS Express certificate. Instead, you can do the following to tell IIS Express to use your existing certificate:
Open the Certificates MMC snap-in as described here
Find your localhost certificate e.g. under Personal...Certicates and get its thumbprint:
Bring up the properties dialog for the localhost certificate and find the Thumbprint property
Paste the thumbprint value into Notepad (or whatever) and remove the spaces and any special characters at the beginning
Find the port value of your IIS Express project:
Go to the project properties in Visual Studio and finding the "SSL URL" value, e.g. "https://localhost:44300/MyApp".
In this example 44300 is the port number. If yours is different, change that value in the later commands.
Use the following commands in an administrative command prompt (not Powershell):
netsh http delete sslcert ipport=0.0.0.0:44300
netsh http add sslcert ipport=0.0.0.0:44300 certhash=your_cert_hash_with_no_spaces appid=
{123a1111-2222-3333-4444-bbbbcccdddee}
The Guid in the above command can be replaced with one that you generate. It does not correspond to any existing IIS Express value.
For further reference see Handling URL Binding Failures in IIS Express.
With new Chrome 58, nothing from the answers below will help. I've just spent 1 hour uninstalling / reinstalling certificates and trying to find out where the problem is.
Apparently Chrome 58 will refuse certificate because "missing_subjectAltName"
The solution is either "badidea" passphrase or if you need to open popups for login you have to use:
chrome://flags/#allow-insecure-localhost
The source is and the upvote belongs to: https://stackoverflow.com/a/38926117/2089232 :)
I wanted to add this, because it is ridiculous but maybe it will help someone. Keep in mind that I had never opened my project properties before so I have no idea how this happened (I did not change this myself or have the opportunity to), but in Project > Properties > Web my SSL url was listed as my usual URL but as http instead of https (had previously been https because it was working before). I went through all the steps listed on this page, uninstalled VS, then IIS, and finally noticed the error which should have been https://mySSLURL (but was missing the s in https). Once I changed http to https everything worked again.
I just had this issue after updating my VS 2017 to the latest version(s) and created a new (.Net) MVC/WebAPI project (from template). I was able to fix this by adjusting my port numbers to be within the correct range
Chorme Default Port Ranges for DEV SSL
Which I was able to find here: https://www.pluralsight.com/guides/visual-studio-2017-resolving-ssl-tls-connections-problems-with-iis-express
Hope this helps!
You can reinstall IIS Express 10.0 (or whatever version you need) to fix the missing certificate. Download from Microsoft here

SQL Server 2005 Reporting Services and the Report Viewer

I am having an issue embedding my report into an aspx page.
Here's my setup:
1 Server running SQL Server 2005 and SQL Server 2005 Reporting Services
1 Workstation running XP and VS 2005
The server is not on a domain.
Reporting Services is a default installation.
I have one report called TestMe in a folder called TestReports using a shared datasource.
If I view the report in Report Manager, it renders fine. If I view the report using the http ://myserver/reportserver url it renders fine. If I view the report using the http ://myserver/reportserver?/TestReports/TestMe it renders fine. If I try to view the report using http ://myserver/reportserver/TestReports/TestMe, it just goes to the folder navigation page of the home directory.
My web application is impersonating somebody specific to get around the server not being on a domain. When I call the report from the report viewer using http ://myserver/reportserver as the server and /TestReports/TestMe as the path I get this error:
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.
When I change the server to http ://myserver/reportserver? I get this error when I run the report:
Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.
I have been searching for a while and haven't found anything that fixes my issue. Please let me know if there is more information needed.
Thanks in advance,
Kendra
There are two virtual directories of interest with SSRS.
http://myserver/reportserver is where the web services are.
http://myserver/reports is where the Report Manager interface is.
http ://myserver/reportserver?/TestReports/TestMe works because you're going to the web services and passing in a parameter of the 'address' of the report you want. Notice the ? in there, indicating that the rest is a querystring parameter
http ://myserver/reportserver/TestReports/TestMe is trying to go a subdirectory of the virtual directory, which doesn't really exist.
To get your system working using anonymous access, you'll need to tell IIS to be running your website's application pool as a known user, which has sufficient permission to view the report. You can set this up in Report Manager (http://myserver/reports).
See how you go - good luck.