I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.
Related
I have installed Microsoft SQL Server Developer Edition in my local machine for my own development use with a Windows Authentication. I have been able to connect to DB Engine, SSAS (Multidimensional Model) Engine, SSIS Engine, SSAS (Tabular Model Engine using another instance).
I was able to connect to SSRS engine (Native Mode) a few weeks earlier. Recently I installed CheckPoint SSL VPN to access our client Remote Desktop. After this installation, whenever I connect to SSRS either using SSMS or Report Server or Report Manager, even though the SSRS Services is running (I have been able to verify from SQL Server Configuration Manager as well as Reporting Services Configuration Manager). I even tried to add the SSRS Report Server link in the SSMS for the SSRS Engine, but still not successful.
I get the following:
TITLE: Connect to Server
Cannot connect to LAPTOPNAME\SQL2012DEV.
ADDITIONAL INFORMATION:
Unable to connect to the server at LAPTOPNAME\SQL2012DEV. The specified URL might not be valid or there might be a problem with the report server version or configuration. Specify a different URL, or contact your
server administrator to verify that the report server runs SQL Server 2008 or later. Additionally, if you are trying to connect to a SharePoint-integrated report server, verify that SharePoint is installed on the server
and that the report server uses SharePoint integrated mode. (Microsoft.SqlServer.Management.UI.RSClient)
BUTTONS:
OK
Could this be due to some permission issues ? I have restarted the SSRS services many times, though it is running, I am not able to connect. Should some Admin privileges be given to my Windows account ? If so, can you guide me how ?
Information from SQL Server Configuration Manager (for SSRS service):
Log on As: NT Service\ReportServer$SQL2012DEV
Information from Reporting Serivces Configuration Manager:
Service Account is built-in: ReportServer$SQL2012DEV
Should I change built-in account to Local Service, Network Service, Local System ?
Open "Reporting Services Configuration Manager" in "Web Service URL" OR "Web Portal URL" tab check your IP and Port access & use the link in URLs to be sure. I think your new application changed this settings.
I am trying to debug a stored Procedure from Microsoft SQL Server Management Studio 2008 which is connected to MS SQL Server 2008 Database Instance running on a different system.
System Information:
1. Remote system is running with Symantec End Point Security
I have done the following settings for running the remote debugger:
I have added the inbound Rules for TCP 139, TCP 445, UDP 137 and UDP 138 ports.
My local system's instance is running with sysadmin user role.
I have added the sqlservr.exe and svchost.exe at server windows firewall exception list.
I have added the svchost.exe and ssms.exe at client windows firewall exception list.
The SSMS and SQL server services are running in the same domain.
Following necessary services are running properly
TCP/IP NetBIOS Helper
Remote Registry
RPC Service
But after doing all these specified steps i am getting following error after clicking the debugger button in client SSMS.
Unable to start T-SQL Debugging. Could not attach to SQL Server process on 'remotesystem_name'. Click Help for more information.
If there is another alternative please let make me aware of that.
I solved this problem by creating a new login account (windows authentication account) on server for my machine.
I have been wanting to deploy my SSRS reports to a Test server. However I found that on that server the SSRS service had stopped, and I had to change the setting so that it used a built in Network Service account. After doing that I found I could start the service. However when I key in the ReportService url in my browser, I get the above error message.
One problem that I had when I changed the settings to the Network Service account is that I got the error message:
"A connection could not be established with the information provide. Hit OK to change your connection settings.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: named Pipes Privider, error: 40 - Could not open a connection to SQL Server)"
Even so, this did not stop the service from starting.
As a result of all this I still cannot deploy my reports. How do I fix this?
If you are running SSRS 2016, restart the SSRS services:
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
The best way to find the answer is to check the log files.
You can find the log files for report server at below path:
In SQL Server Reporting Services 2016 or earlier: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
In SQL Server Reporting Services 2017: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
Thanks & Regards
Karan
Error 503 Usually comes if the database credentials are wrong , you can test the connection from Reporting Configuration Manager.
Otherwise, Check the Reportserver config file "rsreportserver" at path
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer
and find the following tags are correct or not.!
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
According to user permissions/properties you can change <AuthenticationTypes> tag.
Restart Following Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
This error is also generated if you are using a trial version of SSRS and it has expired.
Find <IsWebServiceEnabled>False</IsWebServiceEnabled> and change to
<IsWebServiceEnabled>True</IsWebServiceEnabled> in the rsreportserver
config file.
I was getting this error and tried deleting the URL's from the rsreportserver.config file.
After lots of frustration, I found that the permissions on that file and directory itself did not allow ReportServer user to modify the file. Once I gave the reporting user permission on the file, all was good to remove / update URL's, and returned SSRS back into service.
Try explicitly adding the user permissions to the config file.
Good luck!
In rsreportserver.config, my value was not correct. It was showing up as: http://+:80. Of course, this needs to map to the URL specified in the Report Server Configuration Manager, Web Portal URL (ie the blue URL link that was bringing me to a "not connected" browser screen). It did not, so I got Service Unavailable with a 503 (HTTP error).
The solution: edit the value/address to match the Web Portal URL.
Web Service URL -> URLs: http://MYSERVERNAME:80/Reports
rsreportserver.config -> http://MYSERVERNAME:80/Reports
Once I saved the rsreportserver.config with the edited value to match accordingly (above), I could click on the provided link in the Web Portal section of the Report Server Configuration Manager, and it brought up the SQL Server Reporting Services page. Note: I didn't need to restart anything.
Cheers!
I have SQL Server 2008 Developer Edition and I'm facing the following issues with the Reporting Services.
When I open the Report Manager URL (I get it from the Reporting Services Configuration Manager) in a browser, it shows me a SQL Server Reporting Services page with a folder icon on top left and links with text 'Home', 'My subscriptions', 'Help' on top right. That's it, I don't get to see anything else.
I have a virtual directory with the same name as specified for Report Manager in Reporting Services Configuration Manager.
Opening the Report Server in the browser gives the following error message-
Reporting Services Error
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)
I tried the following at the command prompt in order to resolve it-
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a Windows -u <MYDOMAIN\MYACCOUNT> -p <PASSWORD>
but I got another error saying Report Server WMI Provider error: Invalid namespace
I would really appreciate any help on this.
cheers
I was finally able to get through both the problems by opening a port in Windows firewall for the Report Server.
For Windows 2003 and Vista the steps are mentioned here http://msdn.microsoft.com/en-us/library/bb934283.aspx
cheers
1) Open Start -> SQL Server (20xx) -> find "Reporting Services Configuration Manager" in subfolders -> go to Database tab -> check if "sql server name" and "Database Name" are selected correctly. It is the database which reporting services stores reports in it.
2) if it was OK, check if you have more the one sql instances. If you have more than one instances on your machine, decide which one you want to use. for example sql server 2008 or sql server 2012. Maybe you are using the URL of the reporting services 2008 that is not using a correct database in its "Reporting Services Configuration Manager"
I have a SQL 2008 developer edition with SSRS and the report manager is only available from the local machine. If I try to access it from any other machine I get challenged for my domain u/name and pwd 3 times and then the screen stays blank.
I have made changes to some config files (originals copied out) in order to get a 3rd party application to run but that is now uninstalled and the config files are all back to vanilla (originals copied back in)
I feel its something to do with authentication but am stuck ...
any suggestions welcomed
Jonathan
I have just stumbled on the answer.
I changed the Report Server Service Account to use the built-in Local System account and its all accessible from remote browsers.
Anyone any ideas why?
You may need to change the SSRS Configuration (through the GUI) (Start - Microsoft SQL Server 2008 - Configuration Tools - Reporting Services Configuration Manager) and set it to allow connections from outside the box it is on.
Also don't forget that it's using domain credentials / local machine credentials, so if you're not on a domain, you'll have to provide credentials to log onto that machine (i.e. MACHINE1 where SSRS is installed, from MACHINE2, log on with MACHINE1\username and password for MACHINE1).
Or you may need to open up your SQL Server instance to permit connections from other boxes.