"Bill" <Bill@discussions.microsoft.com> wrote in message
news:D7047A89-E25F-4F0E-8E87-31B5DF171ED3@microsoft.com...
> This error has been showing up in tons of contexts in multiple report
> server
> forums. In my case, local sql mgmt studio can't connect to report server
> (soap error "object reference..."), but config tools can. Nothing remote
> can
> connect. Analysis, DBengine connects ok from everywhere. Can't connect
> using http://server/ReportServer ("declines to show webpage") or trying to
> deploy from bus dev studio (object reference...) or Visual Studio. But
> reports continue to be scheduled and sent (pdf, anyway, I have no links
> reports to test). I can go into tables & change things like report freq &
> see
> it reflected in outgoing reports.
> I've looked at all the logs I can find, seen a couple of compile
> failures on .net modules, failure of w3wp?.exe, occasional unrelated,
> probably, report failures. I've changed & rechanged service accounts &
> resaved keys, looked at config files, IIS, started & stopped various
> services
> that might have had some bearing. I removed anti-virus (McAfee has a
> nasty
> habit of resetting port 25 blocking rules, killing dbmail, so I thought
> they'd done something nefarious). I'm in the process of backing out
> updates
> to win2003, sql server, iis and .net & testing. I'll reapply when done.
> So
> far no joy. I'll yell if I get anything. If anybody can find a solution,
> I'd be really grateful. Report Server is now like a runaway train....
> almost
> no control.
>
>
>

"William (Bill) Vaughn" wrote:

> Ok, is the server configured so it requires HTTPS? Is the report server
> installed on the default instance of SQL Server or on a named instance? If
> the latter you need to reference the specific named instance (as shown when
> you drill into the IIS virtual directory) like this:
>
> https://mymachine/reportserver$myinstancename
>
> hth.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Bill" <Bill@discussions.microsoft.com> wrote in message
> news:D7047A89-E25F-4F0E-8E87-31B5DF171ED3@microsoft.com...
> > This error has been showing up in tons of contexts in multiple report
> > server
> > forums. In my case, local sql mgmt studio can't connect to report server
> > (soap error "object reference..."), but config tools can. Nothing remote
> > can
> > connect. Analysis, DBengine connects ok from everywhere. Can't connect
> > using http://server/ReportServer ("declines to show webpage") or trying to
> > deploy from bus dev studio (object reference...) or Visual Studio. But
> > reports continue to be scheduled and sent (pdf, anyway, I have no links
> > reports to test). I can go into tables & change things like report freq &
> > see
> > it reflected in outgoing reports.
> > I've looked at all the logs I can find, seen a couple of compile
> > failures on .net modules, failure of w3wp?.exe, occasional unrelated,
> > probably, report failures. I've changed & rechanged service accounts &
> > resaved keys, looked at config files, IIS, started & stopped various
> > services
> > that might have had some bearing. I removed anti-virus (McAfee has a
> > nasty
> > habit of resetting port 25 blocking rules, killing dbmail, so I thought
> > they'd done something nefarious). I'm in the process of backing out
> > updates
> > to win2003, sql server, iis and .net & testing. I'll reapply when done.
> > So
> > far no joy. I'll yell if I get anything. If anybody can find a solution,
> > I'd be really grateful. Report Server is now like a runaway train....
> > almost
> > no control.
> >
> >
> >
>
>