Over the weekend the SQL Server 2008 R2 (running on Windows Server 2008 R2) was rebooted.
This morning my reports don't run.
I try to login to SQL Server 2008 R2 Reporting Services Configuration Manager and it gives me an error: Unable to connect to the Report Server
I did some searches and found this, but I don't see any service called Report Server. I also don't see any services that - by its name - seem to be the reporting service when running SQL Server Configuration Manager.
Ideas?
Thanks.
The link you provided was for the 2012 version. Use the appropriate version of the link for a few ideas:
http://msdn.microsoft.com/en-us/library/ms143773(v=sql.105).aspx
If the Reporting Services Configuration Manager can't be launched, I would check the system event logs for errors pointing in the right direction: This could be a lot of things: permissions, SQL connectivity problems, certificate expiration, &c.
Edit: the service name is still incorrect in the corret version of the docs I provided. The default instance of this service is called
SQL Server Reporting Services (MSSQLSERVER)
If you have multiple instances of SSRS installed there will be multiple services listed, with the instance name in parenthesis.
Related
I have a SQL 2012 instance called LTT which contains a database called ReportServer$LTT. I have installed SSRS 2017. After the installation of SSRS2017 it is using SSRS as its Report Server Instance. But I need it to use LTT. How do i change the Report Server Instance? Using SQL Management Studio I am unable to connect to <servername>\LTT Report Server and I get the following error:
The Reporting Services instance could not be found.
(MS.sqlserver.managment.UI.RSClient)
I am also unable to connect to: \SSRS and get this error:
Unable to connect to the server at \SSRS. The specified
URL might not be valid or there might be a problem with the report
server version of configuration. Specify a different URL....
You'll need to remote desktop to the report server. Then open Reporting Services Configuration Manager.
Click on the "Database" tab. From there you'll be able to change the database the report manager uses.
I have a copy of SQL Server 2008 and SQL Server 2014 on my machine.
Reporting services has been installed and configured for both instances
SQL Server 2008 instance - machinename\SQL08
SQL Server 2014 instance - machinename
However I can't connect to the 2008 instance of the report server.
From SSMS 2014 I see the following
From SSMS 2008 I see the following
From the Reporting Server Configuration for 2014 I get the following, which shows that it can connect to the 2014 report server
From the Reporting Server Configuration for 2008 I get the following, which shows that it isn't able to see any servers
When I enter the 08 reporting instance I get the following error message.
Has anyone seen this WMI error message and know how to resolve it?
Can you please make sure the reporting service is actually running? From the run command type "Services.msc" and search for SQL Server Reporting Services. It should be running and set to "Automatic"
If its running and issue still persist then please check your firewall.
Hope this helps!
I've two 64-bit Windows Server 2008 R2 machines. On one of the machines BizTalk Server 2010 Standard Edition is installed & on the other SQL Server 2008 R2 is installed.
When I use the 'BizTalk Server Configuration' on the BizTalk machine to create the necessary databases on the SQL Server machine, just the 'SSODB' gets created & then the configuration fails due to below errors
Failed to create the SQL database 'SSODB' on SQL Server 'SQLServerName' (with SSO Administrator account 'SSO Administrators').
(0xC0002A21) An error occurred while attempting to access the SSO database.
Could not find the account name 'SSO Administrators' on computer 'SQLServerName'. Configuration can proceed, but it might fail.
(0x800706BA) The RPC server is unavailable.
A few sites suggested to register both the 32-bit & 64-bit SSOSQL.dll using the regasm command to resolve this issue & I did the same. But, the issue still persists.
What is a solution for this?
Create "Domain user accounts/user groups" before configuring and use those instead of the local user accounts/user groups. (http://msdn.microsoft.com/en-us/library/aa577661(v=BTS.70).aspx)
Add the domain user account as sys-admin on the Sql server.
Most likely the above 2 steps will help you resolve this issue.
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DSView'. (rsErrorOpeningConnection)
The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services. (rsOperationNotSupported)
Hi, I have encountered the above mentioned error while doing an SSRS project. And from the research, it seems like it is SQL server related issue.
I am trying to access a remote SQL server....so I was wondering how can I get rid of that error?
Do I have to install SQL server Standard edition on my local machine or the server that I am trying to access should be installed with Sql Standard edition?
I have got Express editions installed on both my local machine and the server...
Thx
From Books Online:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Features Supported by Reporting Services in SQL Server Express.
With SQL Server Express you can only use a Data Source where the database engine is from the same instance running SSRS.
If you need to connect to other instances your only options are to get a backup restored to your local instance or to install a SQL Server edition that allows remote Data Sources; most likely Developer for your own needs or Standard or above for any production instances.
It depends on what's allowed under your specific licencing agreement.
A neat way to get around this (that just worked for me) is to add a Linked Server on the Local machine to point to the server that hosts your remote data source.
Then modify your Dataset query in the SSRS report to look something like this...
select * from openquery(REMOTE_SERVER,'Put your original query here');
I have two virtual machines runs on my laptop, let's say their name are VMApp and VMDB, and both are runs the same OS, Windows Server 2008 R2.
On VMDB, I installed all SQL Server 2008 features except the Reporting Services. in contrast, I installed only SQL Server 2008 Reporting Services on VMApp.
I run Reporting Services Configuration Manager on VMApp and point the Server Name to the VMDB's computer name, then I got an error message
"A connection to the computer cannot be established"
I enabled the named pipe from SQL Server Configuration Tools on VMDB, but I still get that error message on VMApp.
I think the problem is not network connection because the VMs are connected in same domain network and they could ping each other.
Sorry for this dumb case because I am newbie in SQL Server, and I really appreciate any help from you guys!
Regards,
Chrisma Andhika
You cant set the DB path to SERVERNAME\INSTANCENAME on the configuration manager. There isnt even that option. First you set the server:
and then the DB:
where exactly are you having your issue?
FYI: try to enable SQL Browser on VMDB or to connect by IP if you cant enable browser