HSChronic Posted September 28, 2010 Report post Posted September 28, 2010 When I install the DB role on the primary box running SCCM everything works fine with SSRS. However when I use a remote install of SQL I can never get SSRS working. The connect newsgroups were a waste of time. I keep getting invalid namespace errors. When I go to the SQL box I am able to access the report server and it seems to be working fine, though I have to use the SSL report site because the one on port 80 gives me a 404 error. Everything else is working fine though just this is the only piece not working. I thought it was SQL 2008 SP2 but that wasn't it, so I am thinking that this might be broken in the beta. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 28, 2010 Report post Posted September 28, 2010 if you disable firewalls on both boxes does it help ? as a test Quote Share this post Link to post Share on other sites More sharing options...
HSChronic Posted September 28, 2010 Report post Posted September 28, 2010 if you disable firewalls on both boxes does it help ? as a test Windows Adv firewall is off by GPO, and there isn't any other firewall on there or AV software. I have another instance on the same box that runs MSDPM and the SSRS on that works fine. Both were configured with Native mode. I reinstalled from scratch yesterday (just default instance, I tried a named one that didn't work either), and pretty much set everything up the same way I did when it was living on the SCCM box, only diff is this is remote and that isn't. I added the computer account, the SSRS report account, and domain admins to every role on the reporting server just to cover my bases. So maybe it is broke when using remote instances or there are some crazy rights that I need to assign it (full rights on SQL and admin rights on the box itself pretty much takes care of everything), it wouldn't surprise me since this is beta 1. I know they said they were working on reworking parts of this component to lessen the hoops you have to go to in order to get it running. I would move the SQL back to the box but when I do the RAM starts pegging 4gigs ish and even with Dynamic memory in Hyper-V the other VMs suffer. So I wanted to run just SQL on my machine with 10gigs of RAM but NOOOO MS has to make you go through hoops with reporting edit: forgot to mention the site is running in Native mode Quote Share this post Link to post Share on other sites More sharing options...
HSChronic Posted October 2, 2010 Report post Posted October 2, 2010 Windows Adv firewall is off by GPO, and there isn't any other firewall on there or AV software. I have another instance on the same box that runs MSDPM and the SSRS on that works fine. Both were configured with Native mode. I reinstalled from scratch yesterday (just default instance, I tried a named one that didn't work either), and pretty much set everything up the same way I did when it was living on the SCCM box, only diff is this is remote and that isn't. I added the computer account, the SSRS report account, and domain admins to every role on the reporting server just to cover my bases. So maybe it is broke when using remote instances or there are some crazy rights that I need to assign it (full rights on SQL and admin rights on the box itself pretty much takes care of everything), it wouldn't surprise me since this is beta 1. I know they said they were working on reworking parts of this component to lessen the hoops you have to go to in order to get it running. I would move the SQL back to the box but when I do the RAM starts pegging 4gigs ish and even with Dynamic memory in Hyper-V the other VMs suffer. So I wanted to run just SQL on my machine with 10gigs of RAM but NOOOO MS has to make you go through hoops with reporting edit: forgot to mention the site is running in Native mode Edit: 2-Oct-10 I think I got this working. It seems that the instructions don't mention (oh wait there aren't any published yet) that you have to install this role on your database server. I kept on looking at the logs and it kept saying SSRS wasn't configured on ChronicMGMT which is my MGMT Point not my Database Server. So I said to myself hrmm lets try installing this role on the DB box, it can't hurt. So I go through the wizard and instead of the SSRS instance being blank it populated with the right SSRS instance without me putting it in there. So hopefully the component turns green when I reset the count. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted October 3, 2010 Report post Posted October 3, 2010 good work, is it functioning correctly now ? Quote Share this post Link to post Share on other sites More sharing options...
HSChronic Posted October 3, 2010 Report post Posted October 3, 2010 good work, is it functioning correctly now ? Still giving me invalid namespace. I guess I will just use the all inclusive VHD since it has everything preconfigured. It sucks, I got everything working it seems minus this. Though I am not getting any notifications on updates, but the windowsupdate.log seems to be identifying and downloading them. I hope beta 2 comes out soon, I like the product but the betaness of it makes me want to go back to 2007 since everything is configured the same and works, yet it doesn't on vNext. Quote Share this post Link to post Share on other sites More sharing options...
Eaglenest Posted December 21, 2011 Report post Posted December 21, 2011 Did you got it working. I've installe RC1 and use a seperate SQL 2008 R2 server. When installing SQL on a Windows Core server SCCM Reporting Service will not work. When installing it on Windows Standard Full it will work. You need to install SQL 2008 R2 CU4 patch. Quote Share this post Link to post Share on other sites More sharing options...
