Error with Report Manager

Hi,
"localhost/reportserver" is all right.
But With "localhost/reports" i have the following error:
--"The underlying connection was closed: The remote name could not be
resolved."
I have no more idea. Thanks !!Hello MIB,
Try accessing the Report Manager with https://<machinename>/Reports or
http://<machinename>/Reports
Peter Blackburn
www.sqlreportingservices.net
"MIB" <MIB@.discussions.microsoft.com> wrote in message
news:CB391524-0F0E-4FAB-A5D5-17467F120B02@.microsoft.com...
> Hi,
> "localhost/reportserver" is all right.
> But With "localhost/reports" i have the following error:
> --"The underlying connection was closed: The remote name could not be
> resolved."
> I have no more idea. Thanks !!|||Thanks for your helps.
I tried to access with the machinename, but it doesn't work.
I'm using Wondows Server 2003 (FAT 32 - It's stupid I know but i haven't
choose this configuration).
At the end of RS install, I had the following message : launch manually
report manager (How to do it?).
I need to access to the report mnager, i tried so many things and i have no
more idea.
"Peter Blackburn (www.sqlreportingservice" wrote:
> Hello MIB,
> Try accessing the Report Manager with https://<machinename>/Reports or
> http://<machinename>/Reports
> Peter Blackburn
> www.sqlreportingservices.net
> "MIB" <MIB@.discussions.microsoft.com> wrote in message
> news:CB391524-0F0E-4FAB-A5D5-17467F120B02@.microsoft.com...
> > Hi,
> > "localhost/reportserver" is all right.
> > But With "localhost/reports" i have the following error:
> >
> > --"The underlying connection was closed: The remote name could not be
> > resolved."
> >
> > I have no more idea. Thanks !!
>
>

Error while running Query

Hi,

SQL Server 7
When i ran a query in query analyzer i am getting the below error.
once i closed and opened the query analyzer and ran the same query it worked fine.

pls the error which i got in first time.

Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large
[Microsoft][ODBC SQL Server Driver]TDS buffer length too large

Pls help me in this

TIA
AdilSo, after you reopened QA the same query ran with no errors? Are you suspecting you're going to get it again?|||hi
thanks for the reply

yes, i'm worried if it comes again whats the solution for it.
pls help me out.

TIA|||The problem seems to be that you've got some bits stuck in your network cable. Remove the cable, shake it vigorously in all four cardinal compass points (north, east, south, and west), and plug it back in. Things should work just fine then!

On a slightly more serious note, removing the network cable will actually fix the problem in most cases. There was some kind of communication error, possibly lost data/framing error/digi-voodoo/etc. When you remove the network cable for any significant amount of time (over a few seconds), the NIC resets. When the cable is reattached, the NIC reconnects, and whatever problem there was is magically gone.

If nothing else, the attention that you get when everybody thinks that you've clearly lost what little mind you might have once had, then your bizzare behavior appears to fix the problem will get you lots of digi-voodoo status.

-PatP|||that's an interesting solution, but considering the real reason for the above error actually very precise. now, here's your reference material (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q176/2/56.asp&NoWebContent=1) in this regard.|||Pat Phelan, you need to be more carefull about your advice. I followed your intructions and got bits all over my carpet. They are extremely hard to get out, and since the dang things carry a static charge they stick to my cat and he has tracked them all over the house. On a positive note, they seemed to pass through his digestive tract pretty quickly.