4 days and still can't get my report to depoly (help)...
in [Reports]
|
From: trint on 24 Sep 2007 17:08 I have had a great deal of success in the past on other systems with deploying reports... BUT now, to save my life, I haven't been able to get the first report to deploy. I get these errors: A connection could not be made to the report server http://###.###.##.###/reportserver. Additional information: The attempt to connect to the reoprt server failed. Check your connection information and that the report server is a compatible version. (Microsoft.ReportingServices.Designer) I change the TargetServerURL (after remote desktoping to the Report Server itself) to: http://GCC/ReportServer or http://localhost/ReportServer and get another type of error: A connection could not be made to the report server http://localhost/reportserver The request failed with HTTP status 404: Bad Request (System.Web.Service) I've tried all the configurations I know and granted all permissions and turned off the firewall. Any help (especially at this point) is very appreciated. Thanks, Trint
From: Bruce L-C [MVP] on 25 Sep 2007 10:51 First things first. You need to make sure that you can open up Report Manager (that is the portal that ships with RS). Sure, there won't be any reports if none have been deployed but that is fine. It will show you that everything is setup and working and that you have rights. It sounds like in your case the easiest thing to do is to first remote desktop to the server and then do this: http://localhost/Reports/Pages/Folder.aspx Do not try anything else until this comes up for you. If you have been changing permissions in the database or in IIS after installing RS then you have most likely just messed things up. You should never have to be doing either one. Everything from a security perspective can be done using Report Manager. If IIS has set the two RS websites to anonymous then this will come up but you will not be able to deploy because with anonymous no-one has rights to deploy. RS uses roles. Read up on how roles are used. -- Bruce Loehle-Conger MVP SQL Server Reporting Services "trint" <trinity.smith(a)gmail.com> wrote in message news:1190668106.834755.26140(a)22g2000hsm.googlegroups.com... >I have had a great deal of success in the past on other systems with > deploying reports... > BUT now, to save my life, I haven't been able to get the first report > to deploy. I get these > errors: > > A connection could not be made to the report server > http://###.###.##.###/reportserver. > Additional information: > The attempt to connect to the reoprt server failed. Check your > connection information and that the report server is a compatible > version. (Microsoft.ReportingServices.Designer) > > I change the TargetServerURL (after remote desktoping to the Report > Server itself) to: > http://GCC/ReportServer or http://localhost/ReportServer and get > another type of error: > > A connection could not be made to the report server > http://localhost/reportserver > The request failed with HTTP status 404: Bad Request > (System.Web.Service) > > I've tried all the configurations I know and granted all permissions > and turned off the firewall. > Any help (especially at this point) is very appreciated. > > Thanks, > Trint >
From: trint on 26 Sep 2007 11:27 On Sep 25, 10:51 am, "Bruce L-C [MVP]" <bruce_lcNOS...(a)hotmail.com> wrote: > First things first. You need to make sure that you can open up Report > Manager (that is the portal that ships with RS). Sure, there won't be any > reports if none have been deployed but that is fine. It will show you that > everything is setup and working and that you have rights. > > It sounds like in your case the easiest thing to do is to first remote > desktop to the server and then do this: > > http://localhost/Reports/Pages/Folder.aspx > > Do not try anything else until this comes up for you. If you have been > changing permissions in the database or in IIS after installing RS then you > have most likely just messed things up. You should never have to be doing > either one. Everything from a security perspective can be done using Report > Manager. > > If IIS has set the two RS websites to anonymous then this will come up but > you will not be able to deploy because with anonymous no-one has rights to > deploy. > > RS uses roles. Read up on how roles are used. > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "trint" <trinity.sm...(a)gmail.com> wrote in message > > news:1190668106.834755.26140(a)22g2000hsm.googlegroups.com... > > > > >I have had a great deal of success in the past on other systems with > > deploying reports... > > BUT now, to save my life, I haven't been able to get the first report > > to deploy. I get these > > errors: > > > A connection could not be made to the report server > > http://###.###.##.###/reportserver. > > Additional information: > > The attempt to connect to the reoprt server failed. Check your > > connection information and that the report server is a compatible > > version. (Microsoft.ReportingServices.Designer) > > > I change the TargetServerURL (after remote desktoping to the Report > > Server itself) to: > >http://GCC/ReportServerorhttp://localhost/ReportServerand get > > another type of error: > > > A connection could not be made to the report server > >http://localhost/reportserver > > The request failed with HTTP status 404: Bad Request > > (System.Web.Service) > > > I've tried all the configurations I know and granted all permissions > > and turned off the firewall. > > Any help (especially at this point) is very appreciated. > > > Thanks, > >Trint- Hide quoted text - > > - Show quoted text - Bruce, I'm going to try this right now! Please stay with me on this I will be right back with you. Thanks for your help! Trint
From: trint on 26 Sep 2007 11:36 On Sep 25, 10:51 am, "Bruce L-C [MVP]" <bruce_lcNOS...(a)hotmail.com> wrote: > First things first. You need to make sure that you can open up Report > Manager (that is the portal that ships with RS). Sure, there won't be any > reports if none have been deployed but that is fine. It will show you that > everything is setup and working and that you have rights. > > It sounds like in your case the easiest thing to do is to first remote > desktop to the server and then do this: > > http://localhost/Reports/Pages/Folder.aspx > > Do not try anything else until this comes up for you. If you have been > changing permissions in the database or in IIS after installing RS then you > have most likely just messed things up. You should never have to be doing > either one. Everything from a security perspective can be done using Report > Manager. > > If IIS has set the two RS websites to anonymous then this will come up but > you will not be able to deploy because with anonymous no-one has rights to > deploy. > > RS uses roles. Read up on how roles are used. > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "trint" <trinity.sm...(a)gmail.com> wrote in message > > news:1190668106.834755.26140(a)22g2000hsm.googlegroups.com... > > > > >I have had a great deal of success in the past on other systems with > > deploying reports... > > BUT now, to save my life, I haven't been able to get the first report > > to deploy. I get these > > errors: > > > A connection could not be made to the report server > > http://###.###.##.###/reportserver. > > Additional information: > > The attempt to connect to the reoprt server failed. Check your > > connection information and that the report server is a compatible > > version. (Microsoft.ReportingServices.Designer) > > > I change the TargetServerURL (after remote desktoping to the Report > > Server itself) to: > >http://GCC/ReportServerorhttp://localhost/ReportServerand get > > another type of error: > > > A connection could not be made to the report server > >http://localhost/reportserver > > The request failed with HTTP status 404: Bad Request > > (System.Web.Service) > > > I've tried all the configurations I know and granted all permissions > > and turned off the firewall. > > Any help (especially at this point) is very appreciated. > > > Thanks, > >Trint- Hide quoted text - > > - Show quoted text - Bruce, Something is bad...I get the Reporting Services type screen, you know, it's not the avereage looking html page with the two lines at the top, a big red X in a red circle and the message after the lines: "The request failed with HTTP status 400: Bad Request." and that's all there is on the page. I could get that, unless i used the full ip address of the server it's on, because I would just get the same message on a regular http page using "localhost" or gcc, which is the virtual folder. Thanks for you help! I sure hope I don't have to drive ALL the way over to Virginia (where my server is) and reinstall SQL '05 Trint
From: Bruce L-C [MVP] on 26 Sep 2007 12:16
Run the program files->Microsoft SQL 2005->Configuration Tools -> reporting services configuration Make sure you have no red X's. -- Bruce Loehle-Conger MVP SQL Server Reporting Services "trint" <trinity.smith(a)gmail.com> wrote in message news:1190820960.305074.169310(a)r29g2000hsg.googlegroups.com... > On Sep 25, 10:51 am, "Bruce L-C [MVP]" <bruce_lcNOS...(a)hotmail.com> > wrote: >> First things first. You need to make sure that you can open up Report >> Manager (that is the portal that ships with RS). Sure, there won't be any >> reports if none have been deployed but that is fine. It will show you >> that >> everything is setup and working and that you have rights. >> >> It sounds like in your case the easiest thing to do is to first remote >> desktop to the server and then do this: >> >> http://localhost/Reports/Pages/Folder.aspx >> >> Do not try anything else until this comes up for you. If you have been >> changing permissions in the database or in IIS after installing RS then >> you >> have most likely just messed things up. You should never have to be doing >> either one. Everything from a security perspective can be done using >> Report >> Manager. >> >> If IIS has set the two RS websites to anonymous then this will come up >> but >> you will not be able to deploy because with anonymous no-one has rights >> to >> deploy. >> >> RS uses roles. Read up on how roles are used. >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "trint" <trinity.sm...(a)gmail.com> wrote in message >> >> news:1190668106.834755.26140(a)22g2000hsm.googlegroups.com... >> >> >> >> >I have had a great deal of success in the past on other systems with >> > deploying reports... >> > BUT now, to save my life, I haven't been able to get the first report >> > to deploy. I get these >> > errors: >> >> > A connection could not be made to the report server >> > http://###.###.##.###/reportserver. >> > Additional information: >> > The attempt to connect to the reoprt server failed. Check your >> > connection information and that the report server is a compatible >> > version. (Microsoft.ReportingServices.Designer) >> >> > I change the TargetServerURL (after remote desktoping to the Report >> > Server itself) to: >> >http://GCC/ReportServerorhttp://localhost/ReportServerand get >> > another type of error: >> >> > A connection could not be made to the report server >> >http://localhost/reportserver >> > The request failed with HTTP status 404: Bad Request >> > (System.Web.Service) >> >> > I've tried all the configurations I know and granted all permissions >> > and turned off the firewall. >> > Any help (especially at this point) is very appreciated. >> >> > Thanks, >> >Trint- Hide quoted text - >> >> - Show quoted text - > > Bruce, > Something is bad...I get the Reporting Services type screen, you know, > it's not the avereage > looking html page with the two lines at the top, a big red X in a red > circle and the message after the lines: > "The request failed with HTTP status 400: Bad Request." > and that's all there is on the page. > I could get that, unless i used the full ip address of the server it's > on, because I would just get the same > message on a regular http page using "localhost" or gcc, which is the > virtual folder. > Thanks for you help! > I sure hope I don't have to drive ALL the way over to Virginia (where > my server is) and reinstall SQL '05 > Trint > |