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.
Related
The problem is that I cannot create new web app on SharePoint 2016, it takes a too long time, loading infinitely with hours until I end it, and the central admin gives 404 not found
First I restarted and made sure the SQL server is started and the farm admin account has correct roles all passes, but with no luck. Finally, I decided to start the configuration wizard but I found this error
WEBCONFIG.ACCSRV.XML, does not have element "configuration/configSections/sectionGroup[#name='SharePoint']" or it is invalid.
I have compared this file with its pair on one server, which it works found they are the same content. Any help, please.
The solution is as follows:
1-Delete All unused Web Apps
2-Delete Some unused IIS sites which are used the ports of SharePoint (port 80,...)
3-clear SharePoint recycle bin
4-confirm all SharePoint service and IIs App pools are running " as I found Service Application App Pool was stopped"
5-Delete the additional trust provider
The main reason is the user was trying to install SharePoint add-in so he changes the trust and changes the port of default site of SharePoint and central admin seeking to change them to HTTPS and then try to create many web apps which have been created with the corrupted web. configs and those changes make all this hassle
I hope this Question may help others
In our current Production Setup, we have setup SSRS and have been able to successfully use the SSRS reports in our .NET Web Application since years. We have used Impersonation in Web.Config (there might be other solutions available, we had to go with this) as shown below.
<identity impersonate="true" userName="domainname/username" password="password"></identity>
This solution worked well becuase our Active Di
rectory and SSRS server are located in the same Network / domain.
Now, as part of our Azure migration, we have migrated our SSRS server to an Azure VM. and we are able to view the reports using Report Server Manager within the VM. Now, when we access the Web Application (App Service - Web App), we are getting the following error. Below is the updated impersonation attribute that we have used.
<identity impersonate="true" userName="username#ouremailaddressdomainname.onmicrosoft.com" password="password"></identity>
"Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'The user name or password is incorrect"
Obviously, this is because of the fact that we don't have a Active Directory domain setup in Azure. Below are my questions.
Can we utilize the users available in the default Directory that gets created on Azure?
If yes, how do I specify the impersonization?
Thanks,
Prawin
With your planned setup you cannot use identity impersonation. This is because the AppService Web Apps do run in an isolated sand-boxed environment which cannot be part of a Windows Domain.
You have couple of options:
Change the reporting server to use mixed mode Authentication and create local for the SQL Server login and user with appropriate permissions. Then configure your reporting application to provide these SQL Server credentials
Move your Web Application to same VM (will not require Domain environment) as your Reporting Server (or just the part which deals with the reports)
Move your application to a separate VM and utilize the Azure Active Directory Domain Services to make the VMs part of same domain (an overkill IMO)
I would vote for the first option, as it requires least changes and leverages PaaS services (App Service). Everything else is overkill or just an abuse of the cloud platform.
I am using Windows Azure, and find it a lot difficult and useless make a new "Package" each time you make a small change, and want to test it on the Cloud. I heard about the opportunity to update the web roles without re-deploy the whole instance each time (about 15 minutes), and do a Web Deploy - upload just the modified files (some seconds).
None of the resources found on the web seems to describe this particular situation.
There are tutorials, on how to enable Web Deploy on Azure Web Roles, but not a one how to set it up. [This tutorial is showing the settings, but not for Azure]
To enable web deploy you first need to be able to do a standard Publish (not Package) from the CloudConfiguration project.
there are some good tutorials how to do that.
While the Publish dialog is open, make sure to select this option, and make a normal publish.
After this configuration is published, you are ready to set up the Publish settings for the Web Role project. Note, the CloudCongiguration project is used for Package deployment, and the Web project is used to deploy to Azure via Web Deploy as deploying to normal web hosting.
When you click on the "Publish" context menu of the Web project, a "Publish Web" dialog appears. All settings are easy to guess/standard, except the second tab: Connection.
Here the things go little hard, if you have not messed with Web Deployment before.
Must select the Web Deploy method
The URL to your Web Role (DNS or IP address found on Windows Azure Management portal)
The name of the web site in the IIS on the Host machine. In our case this is the Azure WebRole instance. So Login via RDP, start "Server Management", navigate to: Roles->WebServer(IIS)-> Internet Information Services Manager. In the Connections Pane (The Left part of the Manager) expand the tree-view pointing to the "localhost" service -> Sites -> and there you find the Website Name (should be something like : xxxxx_IN_0_Web)
This is the username you use for RDP connections /and the password below/
is that strange URL, that is pointing to the Web deploy Service, that will eventually update our website content.
you can check, if the Package deployment went OK, in the Azure Management portal, on the Overview page of the web deployment if the port 8172 is open.
Now "Validate Connection" should succeed!
If not, try "http://{0}.cloudapp.net//MSDEPLOYAGENTSERVICE" for Destination URL
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?
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.