Hey,
Need your help again. I'm setting up a dev environment and I'm having issues with SQL2012 Reporting Services for Sharepoint not showing up as a "service on server". My farm consist of 1 web front end, 1 app server and then one Bussiness Intelligence centered servicer that has some Sharepoint 2010 features and some SQL 2012 features installed. It all works pretty well but when I try to install SQL2012 reporting services, the owstimer crashes during install (like it does when applying CUs) but the installer says "Succesfull!" for both the features (Reporting Service - Sharepoint and the add-in).
But it doesn't show up as a service under "Service on Server" for this server! And yes, I've tried running the powershell commands for this ("Install-SPRSService", "Install-SPRSServiceproxy") neither of which gives any error but when running the command "get-spserviceinstance -all | where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance" all I get is a warning saying it's already started when it should say that it is provisioned as application with a guid.
I've used this guide as well as TechNet article (which for some reason says "single server farm" but it's the same steps.. right?) for this and they all have the exact same result! Now I had the same issues in my previous lab environment (with somewhat equal topology) and it ended up with me having to install it on the web front server for it to appear as a service on server! So this is the second environment I'm seeing this in so I'm thinking I'm doing something wrong! I've googled it and no guide or article has mentioned that it only shows up with this warning, only saying "If it doesn't show up as service for server, run the powershell commands"!
We're running Sharepoint 2010 with the latest CU (aug 2012), all SQL tools and services are SQL2012 enterprise editions on Windows Server 2008 R2s with an AD at 2003 function level.
I also read in an article that you can actually install this before joining the farm and running these commands manually to register the service in the farm. So I removed it from the farm, installed them (this time without the OWSTIMER crash), rejoined the farm and executing the powershell commands and in the end it goes back to the same warning, already started, but nothing in the services on server!
Is there some farm feature that is required for this to be provisioned as a service on server that this server doesn't have? Like "it needs to run Central admin" or "it can't be running calims to windows token service" or something I missed? Need to sort this out because we can't have this in the final production environment. I've rebooted the entire farm, ran the config wizard countless times on all servers, it just won't show up and therefore I can't create the application! Attaching a screenshot of the "services on server" screen for that server, -SHP04.
Please help. And as always, feel free to call me an idiot for missing a checkbox somewhere if that's what it takes, I just wanna get this working :)