A connection could not be made with report server ...

I just installed SQL Server 2005 (Reporting Services) on my collegues laptop
(Windows XP, SP2) and when we try to deploy the reports we get the message:
"A connection could not be made with report server at
http://localhost/ReportServer"
Everything is running (green checks) in the Reporting Services configuration
manager. We get the error, "Page not found." when we just try to open
http://<machinename>/Reports or http://localhost/Reports. I see the virtual
directories in IIS, all services seem to be running correctly.
Please help! I have installed reporting services about 10 times and have
not run into this problem before. The only issue that we had initially was
that the IIS default web site would not run because there was a conflict on
TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
problem should it.
Thank you,
Laurie
--
LaurieTWhat happens when you try going to http://localhost/?
Have you tried http://localhost:81/Reports, since that's what you changed
the port to?
Clint
"LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
>I just installed SQL Server 2005 (Reporting Services) on my collegues
>laptop
> (Windows XP, SP2) and when we try to deploy the reports we get the
> message:
> "A connection could not be made with report server at
> http://localhost/ReportServer"
> Everything is running (green checks) in the Reporting Services
> configuration
> manager. We get the error, "Page not found." when we just try to open
> http://<machinename>/Reports or http://localhost/Reports. I see the
> virtual
> directories in IIS, all services seem to be running correctly.
> Please help! I have installed reporting services about 10 times and have
> not run into this problem before. The only issue that we had initially
> was
> that the IIS default web site would not run because there was a conflict
> on
> TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> problem should it.
> Thank you,
> Laurie
> --
> LaurieT|||Clint -- Thanks, I tried this and still got some errors (although different
than I was seeing before).
I got this error when trying http://localhost:81/Reports
"The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
----
A name was started with an invalid character. Error processing resource
'http://localhost:81/Reports'. Line 1, Position 2
<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
Inherits="Microsoft.ReportingServices.UI.HomePag..."
Any ideas?
Thank you.
--
LaurieT
"Clint" wrote:
> What happens when you try going to http://localhost/?
> Have you tried http://localhost:81/Reports, since that's what you changed
> the port to?
> Clint
> "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> >I just installed SQL Server 2005 (Reporting Services) on my collegues
> >laptop
> > (Windows XP, SP2) and when we try to deploy the reports we get the
> > message:
> > "A connection could not be made with report server at
> > http://localhost/ReportServer"
> >
> > Everything is running (green checks) in the Reporting Services
> > configuration
> > manager. We get the error, "Page not found." when we just try to open
> > http://<machinename>/Reports or http://localhost/Reports. I see the
> > virtual
> > directories in IIS, all services seem to be running correctly.
> >
> > Please help! I have installed reporting services about 10 times and have
> > not run into this problem before. The only issue that we had initially
> > was
> > that the IIS default web site would not run because there was a conflict
> > on
> > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > problem should it.
> >
> > Thank you,
> > Laurie
> > --
> > LaurieT
>
>|||Sorry, I got nothing else. :) I'm pretty much an RS newbie. Hopefully
someone else can chime in for you.
Clint
"LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
news:71DB89B9-F5F4-445E-A480-95A635B73ECB@.microsoft.com...
> Clint -- Thanks, I tried this and still got some errors (although
> different
> than I was seeing before).
> I got this error when trying http://localhost:81/Reports
> "The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> ----
> A name was started with an invalid character. Error processing resource
> 'http://localhost:81/Reports'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag..."
> Any ideas?
> Thank you.
> --
> LaurieT
>
> "Clint" wrote:
>> What happens when you try going to http://localhost/?
>> Have you tried http://localhost:81/Reports, since that's what you changed
>> the port to?
>> Clint
>> "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
>> news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
>> >I just installed SQL Server 2005 (Reporting Services) on my collegues
>> >laptop
>> > (Windows XP, SP2) and when we try to deploy the reports we get the
>> > message:
>> > "A connection could not be made with report server at
>> > http://localhost/ReportServer"
>> >
>> > Everything is running (green checks) in the Reporting Services
>> > configuration
>> > manager. We get the error, "Page not found." when we just try to open
>> > http://<machinename>/Reports or http://localhost/Reports. I see the
>> > virtual
>> > directories in IIS, all services seem to be running correctly.
>> >
>> > Please help! I have installed reporting services about 10 times and
>> > have
>> > not run into this problem before. The only issue that we had initially
>> > was
>> > that the IIS default web site would not run because there was a
>> > conflict
>> > on
>> > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't
>> > be a
>> > problem should it.
>> >
>> > Thank you,
>> > Laurie
>> > --
>> > LaurieT
>>|||laurie,
I had the same problem and Now it has been fixed.i looked online and
here is what i found:
1)The FIX
For IIS MMC: Right click My Computer...then click manage...under
services and applications....expand IIS
then right click the "reports" virtual directory, select property and
then under the
ASP.NET tab select asp.net version that belongs to the .NET framework
version 2.something. For some reason, after you installed reporting
services,
the version of the ASP.NET was removed from the asp.net tab. click ok
2)New Problem
Then you get this new problem when you go to http://localhost/Reports/
--my comment Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
Exception Details: System.Web.Hosting.HostingEnvironmentException:
Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the
IIS metabase (e.g. IIS://servername/W3SVC). For information on
modifying metabase permissions, please see
http://support.microsoft.com/?kbid=267904 .
Source Error:
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of
the exception can be identified using the exception stack trace below.
Stack Trace:
[HostingEnvironmentException: Failed to access IIS metabase.]
System.Web.Hosting.HostingEnvironment.MapPathCaching(String path)
+3609369 System.Web.CachedPathData.GetPathData(String path) +406
System.Web.Configuration.RuntimeConfigLKG.GetInternalSection
(String sectionName, Type type, ResultsIndex index) +134
2) The FIX
To correct the problem To repair IIS mappings for ASP.NET, run the
Aspnet_regiis.exe utlity. To do so, follow these steps:
Click Start, and then click Run.
Type cmd, and then click OK.
At the command prompt, type the following command, and then press
ENTER:
"\<Windows folder>\Microsoft.NET\Framework\<Version
Number>\aspnet_regiis.exe" -i
NOTE:Replace <Windows folder> with the name of the directory where the
operating system is installed and replace <Version Number> with the
.NET Framework version installed on your computer. Or you could do a
seach for the .exe file and locate the directory
You can find the above reference at
http://support.microsoft.com/default.aspx?scid=kb;en-us;325093
Now try going to http://computername/reports/
Hope it helps,
Sharan Doddakashi
LaurieT wrote:
> Clint -- Thanks, I tried this and still got some errors (although different
> than I was seeing before).
> I got this error when trying http://localhost:81/Reports
> "The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> ----
> A name was started with an invalid character. Error processing resource
> 'http://localhost:81/Reports'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag..."
> Any ideas?
> Thank you.
> --
> LaurieT
>
> "Clint" wrote:
> > What happens when you try going to http://localhost/?
> >
> > Have you tried http://localhost:81/Reports, since that's what you changed
> > the port to?
> >
> > Clint
> >
> > "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> > news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> > >I just installed SQL Server 2005 (Reporting Services) on my collegues
> > >laptop
> > > (Windows XP, SP2) and when we try to deploy the reports we get the
> > > message:
> > > "A connection could not be made with report server at
> > > http://localhost/ReportServer"
> > >
> > > Everything is running (green checks) in the Reporting Services
> > > configuration
> > > manager. We get the error, "Page not found." when we just try to open
> > > http://<machinename>/Reports or http://localhost/Reports. I see the
> > > virtual
> > > directories in IIS, all services seem to be running correctly.
> > >
> > > Please help! I have installed reporting services about 10 times and have
> > > not run into this problem before. The only issue that we had initially
> > > was
> > > that the IIS default web site would not run because there was a conflict
> > > on
> > > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > > problem should it.
> > >
> > > Thank you,
> > > Laurie
> > > --
> > > LaurieT
> >
> >
> >|||Sharan,
Thanks for the valuable solution. That was very helpful, precisely to
the point and it solved the issue.
Good Work!
Shailesh
HELP wrote:
> laurie,
> I had the same problem and Now it has been fixed.i looked online and
> here is what i found:
> 1)The FIX
> For IIS MMC: Right click My Computer...then click manage...under
> services and applications....expand IIS
> then right click the "reports" virtual directory, select property and
> then under the
> ASP.NET tab select asp.net version that belongs to the .NET framework
> version 2.something. For some reason, after you installed reporting
> services,
> the version of the ASP.NET was removed from the asp.net tab. click ok
> 2)New Problem
> Then you get this new problem when you go to http://localhost/Reports/
> --my comment Failed to access IIS metabase.
> Description: An unhandled exception occurred during the execution of
> the current web request. Please review the stack trace for more
> information about the error and where it originated in the code.
> Exception Details: System.Web.Hosting.HostingEnvironmentException:
> Failed to access IIS metabase.
> The process account used to run ASP.NET must have read access to the
> IIS metabase (e.g. IIS://servername/W3SVC). For information on
> modifying metabase permissions, please see
> http://support.microsoft.com/?kbid=267904 .
> Source Error:
> An unhandled exception was generated during the execution of the
> current web request. Information regarding the origin and location of
> the exception can be identified using the exception stack trace below.
>
> Stack Trace:
> [HostingEnvironmentException: Failed to access IIS metabase.]
> System.Web.Hosting.HostingEnvironment.MapPathCaching(String path)
> +3609369 System.Web.CachedPathData.GetPathData(String path) +406
> System.Web.Configuration.RuntimeConfigLKG.GetInternalSection
> (String sectionName, Type type, ResultsIndex index) +134
>
> 2) The FIX
> To correct the problem To repair IIS mappings for ASP.NET, run the
> Aspnet_regiis.exe utlity. To do so, follow these steps:
> Click Start, and then click Run.
> Type cmd, and then click OK.
> At the command prompt, type the following command, and then press
> ENTER:
> "\<Windows folder>\Microsoft.NET\Framework\<Version
> Number>\aspnet_regiis.exe" -i
> NOTE:Replace <Windows folder> with the name of the directory where the
> operating system is installed and replace <Version Number> with the
> .NET Framework version installed on your computer. Or you could do a
> seach for the .exe file and locate the directory
> You can find the above reference at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325093
> Now try going to http://computername/reports/
> Hope it helps,
> Sharan Doddakashi
>
> LaurieT wrote:
> > Clint -- Thanks, I tried this and still got some errors (although different
> > than I was seeing before).
> >
> > I got this error when trying http://localhost:81/Reports
> >
> > "The XML page cannot be displayed
> > Cannot view XML input using XSL style sheet. Please correct the error and
> > then click the Refresh button, or try again later.
> >
> >
> > ----
> >
> > A name was started with an invalid character. Error processing resource
> > 'http://localhost:81/Reports'. Line 1, Position 2
> >
> > <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> > Inherits="Microsoft.ReportingServices.UI.HomePag..."
> >
> > Any ideas?
> >
> > Thank you.
> > --
> > LaurieT
> >
> >
> > "Clint" wrote:
> >
> > > What happens when you try going to http://localhost/?
> > >
> > > Have you tried http://localhost:81/Reports, since that's what you changed
> > > the port to?
> > >
> > > Clint
> > >
> > > "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> > > news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> > > >I just installed SQL Server 2005 (Reporting Services) on my collegues
> > > >laptop
> > > > (Windows XP, SP2) and when we try to deploy the reports we get the
> > > > message:
> > > > "A connection could not be made with report server at
> > > > http://localhost/ReportServer"
> > > >
> > > > Everything is running (green checks) in the Reporting Services
> > > > configuration
> > > > manager. We get the error, "Page not found." when we just try to open
> > > > http://<machinename>/Reports or http://localhost/Reports. I see the
> > > > virtual
> > > > directories in IIS, all services seem to be running correctly.
> > > >
> > > > Please help! I have installed reporting services about 10 times and have
> > > > not run into this problem before. The only issue that we had initially
> > > > was
> > > > that the IIS default web site would not run because there was a conflict
> > > > on
> > > > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > > > problem should it.
> > > >
> > > > Thank you,
> > > > Laurie
> > > > --
> > > > LaurieT
> > >
> > >
> > >