Walkabout Report Server URL and Stopped Service Application - sharepoint

I've installed SQL 2012 in Sharepoint Integrated Mode and have Sharepoint 2010 installed on a different server. In Central Administration I have added a SQL Server Reporting Services Service Application and proxy. This all appears to have worked (the RS databases were created).
The problem is I cannot finish the configuration as I need the report server URL. Upon researching I found that this would be "http://myspserver/_vti_bin/reportserver" however this does not connect. I have looked at the rsreportserver.config file and where the URL should be is just
<ReportServerUrl>
</ReportServerUrl>
Upon looking at the at the service applications list I have noticed that the SQL Server Reporting Services Service Application is stopped. This might be why I can't connect to the URL so I tried stopping and restarting the SQL Server Reporting Services Service and although this was successful it made no difference to the state of the service application.
How to get this setup sorted out?

Related

Share point site configurations issue while using port other than 80

I am using SharePoint 2019 on premise and hosting our .net application into it.
I created a site in share point using port 80 and i can deploy my application into it with no problem.
while creating multiple site to host the same application system is not allowing to host application other than 80
Error:-
error occurred in deployment step recycle IIS application pool the local sharepoint server is not available.Check the server is running and connected to the sahre point farm
Please try to do some troubleshooting:
Clear the visual studio's cache.
Open VS as Administrator.
IIS reset executed before every deploy.
Use the account has full control and is the primary site collection administrator.
Restart the server.
Similar issue for reference: Getting Error occurred in deployment step 'Recycle IIS Application Pool': A task was canceled when deploying custom action to Sharepoint

SharePoint 2013 Web Application Association for SSRS

We are running into an issue when we try and setup a new SSRS Application within Central Administration.
I am able to set the Name, App Pool, Configurable App Pool Account, Database Server, Database Authentication, but unable to set the Web Application Association.
The first time I setup the Application it allows me to select the Service Application Sites. When I return back to the Properties, Above the Web Application Association I get this message:
"There are no web applications available to associate with this sql server reporting services server application."
I am suck and cant seem to get this resolved. Has anyone came across this issue before?
You have to approach this in a different way; instead of configuring the associated Web Applications within the Service App. Config, you change the Service Application Associations (Central Admin > Application management > Service Applications > Configure Service Application Associations)
Once there, click on the Application Proxy Group that you're using - in my case, this was 'default'.
That will then pop open a window - "Configure Service Application Associations". Simply untick your old SSRS Service Application and tick the new one.
While it doesn't solve your exact issue... A combination of this and another proxy group might do what you want.

Repeated Reporting Services Login issue when deploying through BIDS to a remote server

We are having a problem deploying a reporting services report to a sql reporting services computer that is configured in SharePoint Integrated mode. I can successfully deploy to the SharePoint document libraries set up for reports and data connections if I do it locally from the box that SharePoint and Reporting Services are deployed on. If I try and do the same thing with the exact same deployment properties from a remote box, I constantly get a Reporting Services Login dialog popping up and no combination of domain\username and password will work. I've even tried the machines local admin account and still nothing.
Any ideas where to start looking?
This occurs when BIDS cannot connect to the Report Server instance. Check the URLs, and see if any firewall is blocking the connectivity to the remote RS instance.
I finally found the solution to this issue. Basically the build of sql server 2008 reporting services I installed added an RSWindowsNegotiate setting into rsreportserver.config file and I was running the reporting service under an account other than Network Service. I removed the RSWindowsNegotiate setting and just left the RSWindowsNTLM setting and everything started working properly for us.
More info can be found here, Solving the Reporting Services Login Issue

Web Service and Report Manager don't load (Sql Server Express 2008 with Reporting Services)

I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.

Moss Farm Issue (Front End) Web Application Service Won't Start

So, I have three servers in my moss farm. A database server and two front-end servers...
On server 1 I am able to access my web application just fine and the services are running fine. However, on server 2 I am unable to start the Web Application service; I receive a error message on the screen stating "Check the server event logs for additional error information"...
When I check the event logs on server I see this error...
Error executing service instance (un)provisioning job. Service instance: "Windows SharePoint Services Web Application" (id "2d8886db-4b63-4841-bf48-4bd48d9a0c89) "1387""
Any thoughts..?
I would guess that either you have something up with IIS on Server 2 or that there's a deeper MOSS problem on Server 2. First thing is to figure out which web application is causing the problem.
Under Central Administration > Application Management > Web Application List. When you click on a web application name you'll see the ID for it in the query string. (i.e. /applications.aspx?WebApplicationId=ID-here)
Find the matching ID and you know that's the web application having issues. Check to make sure there's nothing wrong with that web application in IIS on Server 2.
If everything looks fine, I would remove server 2 from the farm and re-add to provision. If that doesn't work, remove server 2 from farm, reinstall MOSS, and then add back to farm.
I would check that the service account used for the web application has got the nessecary rights.
Go to central administration
then open "operations" > "service accounts"
click web application
Select the web application or check what users are used for the different web applications. Then check if they have the nessecary rights. I cant remember if it is nessecary for them to be local administrators on the server, but at least i would try making them local administrators. Then check if they have the nessecary rights on the SQL server. I think that db creator and writer is the only nessecary roles.
But i generally up the rights until it works, then remove what i think is unnessecary rights afterwards.

Resources