I know this is a really old post, but for anyone that is still having this issue... I managed to work around it by going into my local administrators group on the server and clearing out any accounts showing up as a GUID.
Once I did that, I was able to launch the tool, fill in no server/user info and just hit connect. It logged right in after that.
If the response's Server header returns "Microsoft-HttpApi/2.0", it means that the HTTP.sys is being called instead of IIS. Exploits and port scans use this as a means of fingerprinting an IIS server (even one that is otherwise hiding the Server header).
You can test this by throwing an error using CURL:
curl -v http://www.yourdomain.com/ -H "Range: bytes=...
According to the various documents I found during my initial research and the documents provided in links and discussions I have come up with a solid, reliable, compliant solution.
The binary comparisons conducted further down and the rules applied are according to RFC 3484 which is apparently also valid for IPv4 addresses.
RFC 3484 ...
SSRS supports several standard data sources as well as other .NET data sources:
Assuming you are using the SQL native client for the data source, you have no option to specify a source IP address:
According to the Google Developers guide, you don't have to set up multiple code snippets for each site, as long as they share the same top level domain:
Google Developer's Guide
Here's a good article on displaying subdomains in the dashboard.
Here the solution to download the Microsoft® System CLR Types for Microsoft® SQL Server® 2012
Step 1 : Choose the below website link
Step 2 : In this link, you have to choose the "Install instructions" menu. Then, you need to ...
I checked Add/Remove programs and no luck either, Can't find SSRS
That's because it's not listed as SQL Server Reporting Services. You will need to choose SQL Server in the list of installed programs, click "Uninstall/Change", select the instance of SQL Server that you want to work with, then finally in the 'Select Features' interface, check only '...
Using ILSpy, I've determined that "ExecutionLogLevel" setting isn't even used by SSRS 2012; it's not a supported setting. There is no code that references that string anywhere. FYI, I can find code that references "EnableExecutionLogging" and "ExecutionLogDaysKept" (complete with the internal constants defining the default values that SSRS uses).
The solution was two-fold:
I exported the certificate from the primary site sever under "Personal\Certificates" the friendly name is "ConfigMgr SQL Server Identification Certificate." I then imported the certificate to my local workstation under "Trusted Root Certificate Authorities\Certificates." This allowed me to connect to SQL server when I choose "Use ...
I don't think that you can. I think it's hard-coded.
I have SBS08, not SBS2011, but apparently they both use the Windows SBS Fax Sharepoint Receive Connector for the SBS console mail. This is set to allow all connections from 127.0.0.1 anonymously.
Your best bet would probably be to set up some kind of SMTP server with similar properties, perhaps the ...
You said in a comment above that your databases are only about 10GB total. SQL Server can easily load them entirely in memory, including data, indexes, and temporary data from your queries. This is a good thing, and provides better performance than reading from disk.
Ok, I think I found a workaround - it's not exactly pretty, but it does work.
From information found here: https://blogs.msdn.microsoft.com/sambetts/2014/02/04/multi-subnet-clustered-sql-registerallprovidersip-sharepoint-2013/
I set RegisterAllProvidersIP to 0 then set the HostRecordTTL to 300 and restarted the role.
This will force the cluster to only ...
In order to resolve the issue I had to edit C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\reportserver.xml
Comment out the following:
Leaving WindowsBasic as the only ...
Yes, you have two use accounts (one on each server) with the same name and password. Then run your application Pool under that user-account. Give limited permission to the account, to just do what it is suppose to do.
The AppPoolIdentity account has no access to the network or other servers.
If you look in the ReportServer database in question and run the following query it will show the SSRS web server(s) that are connected to it in the MachineName column.
SELECT * from Keys where Client=1
From the http://reportservername/Reports/browse page, click on "Manage Folder" then from http://reportservername/Reports/manage/catalogitem/security/ page you can click add group or user. You should then see full list.
Based on the version that you got which is 163, try to apply this query on the
instance hosting your reporter server database.
In my below example, the database is named ReportServer :
FROM ServerUpgradeHistory WHERE ServerVersion > 163
Uninstalling and reinstalling .NET 3.5 resolved this problem. Could not find a source for the problem, or what was wrong with the initial installation of .NET, and wish I could provide a better answer.
By default SSRS only allows connections using Negotiate and NTLM authentication. You will need to add Basic Authentication as an allowed authentication method to your SSRS installation in order to use the simple Username and Password credentials. Use the following post to guide you through the setup: https://msdn.microsoft.com/en-us/library/cc281309(v=sql....
Found the fix here: http://blogs.msdn.com/b/selvar/archive/2012/07/14/reporting-services-unexpectedly-loads-net-framework-4-0-by-default-and-fails-with-http-500-19-while-browsing-report-server-and-report-manager-url.aspx
Turns out that the registry key HKLM\SOFTWARE\Microsoft\.NETFramework\OnlyUseLatestCLR was set to 1. No idea how it got there. Once we ...
Found it - the solution is to give the service account access to create its own SPNs. To do that, simply grant SELF to read and write the servicePrincipalName field:
Once you do that, you'll need to restart the SQL service. DO NOT USE THE SERVICES SNAP-IN WITH CLUSTERED SQL SERVERS! The Failover Cluster service will take this as a failure and cut it over.
Got exactly the same problem, How I fixed it?
I went to local users and groups on the server with SPN issues
Groups>Administrators> and removed any account that is not part of the same domain as the server.
I had a user account from another domain, after removing it and trying the App again it worked.
I had the same issue on SQL 2016 hosted on a Windows Server 2016.
Running as admin didnt resolve my problem. I had to 'Run as a different user', then I logged in as my Active Directory domain admin. Then I was able to connect to the hosted SQL server.
Mine was similar to the other answers but slightly different. I had an account from another domain in the Local Administrators group. I'm not sure the exact type of trust that was present. After removing that account the tool was able to run.
I know this thread is old, but I was having the same issue. In my case the Remote Registry service was not running. I have found that on some servers it is just running, and on others it shows Automatic (trigger start), and in both of those cases I can use the tool successfully. If the service is manual/disabled, etc... and not running, this error ...
Hey just for future reference you got this the wrong way around. the 32bit DLL files should go to SysWOW64 and the 64bit should go in system32.
Confusing but that is the way it works with DLL's is SysWOW64 contains the 32bit emulated DLL files and system32 contains the native 64 bit ones.
Hope this helps someone.
This is most likely a problem with your SQL Server edition.
I had the same issue on SQL 2012 express. As it was enabled in the config but not visible in the export list, I tried exporting via URL directly and got an error rsRenderingExtensionNotFound.
Checking in the logs of SSRS I found a line indicating that the XML extension was removed at startup ...
The problem is that a ClickOnce application seems to need Windows Explorer to be running as the shell.
As a quick workaround, the RemoteApp definition might just call %SYSTEMROOT%\explorer.exe instead of the iexplore.exe executable. Providing an URI as a parameter to the explorer.exe call would set up the RemoteApp session with explorer.exe as the shell and ...