When I open reports from the ReportManager, the parameter list and the
reporting toolbar seem to be missing the normal style, and I get an "unable
to connect to the remote server The attempted operation is not supported for
the type of object referenced" error.
I can successfully execute reports from Visual Studio 'Run' or by browsing
"http://localhost/ReportServer/Pages/...".
BTW, this is a completely fresh XP and SQL2005 install, and I've seen the
same problem on another machine. Which probably means I made the same
mistake on both machines. ;-)
Thanks in advance,
TomDid you ever get this to work properly? What did it take to resolve?
"SQL2005_rocks" wrote:
> When I open reports from the ReportManager, the parameter list and the
> reporting toolbar seem to be missing the normal style, and I get an "unable
> to connect to the remote server The attempted operation is not supported for
> the type of object referenced" error.
> I can successfully execute reports from Visual Studio 'Run' or by browsing
> "http://localhost/ReportServer/Pages/...".
> BTW, this is a completely fresh XP and SQL2005 install, and I've seen the
> same problem on another machine. Which probably means I made the same
> mistake on both machines. ;-)
> Thanks in advance,
> Tom|||Nope.
Microsoft Developer Support has been investigating for two weeks. I'll post
when I know more.
"Audie Wright" wrote:
> Did you ever get this to work properly? What did it take to resolve?|||I actually got mine to work. I had SQL2K5 Developer installed on my
workstation (XP).
I reviewed what I had changed in the past week, and traced it to an
installation of Norton Privacy Service. I de-installed it, and it worked
properly.
It appeared to be an issue with how the winsock is controlled.
You could try a netsh winsock reset, reboot, and try it.
"SQL2005_rocks" wrote:
> Nope.
> Microsoft Developer Support has been investigating for two weeks. I'll post
> when I know more.
>
> "Audie Wright" wrote:
> > Did you ever get this to work properly? What did it take to resolve?
>
Showing posts with label reportmanager. Show all posts
Showing posts with label reportmanager. Show all posts
Friday, March 23, 2012
ReportServer virtual directory doubt...
Can a reportserver/reportmanager virtual directory be configured to run inside another virtual directory.
say...http://mymachine/web/reports
Thanks
Samuel
That should not be an issue. I have done this in the past ... Is there a specific reason why you want to do this?|||
i have report server running under my website......do i have to create another virtual directory and point it to what the main reportserver directory is pointing too.
this we need to do as we are publishing a host of application under /web/ virtual directory in ISA. and from my applications the call goes to
from internet http://domainname/web/reportserver
from LAN http://website/reportserver
reportserver2005,IIS6.0,win2003 server.
t
|||Thats easy,
All you have to do is go to teh actual folder's properties under websharing.
you should see in the top list box, if you have multiple websites on the server. you should all of them listed in a dropdown list box. just select the preferred one.
sqlFriday, March 9, 2012
ReportManager works fine until I modify the FQDN
I don't know how I can succinctly express my problem other than I've got all
the latest bits for SQL Server 2000, Reporting Services, service packs,
etc... installed. I have Share Point Portal / IIS 6 / Windows 2003 / SQL
Server 2000 all installed on same box.
I followed all directions to install Reporting Services correctly under this
configuration and, lo and behold, everything worked as advertised.
After I got the above stack working under a non SSL mode, I proceeded to
setup an SSL only option for IIS. No biggie. Everything works just fine! I
created a CA key using OpenSSL and signed my IIS cert request and installed
into IIS and Share Point and SQL Reporting Services are all very cool with
this. Of course, I installed the CA cert in my Trusted Root Authorities on
the server and my client.
So what's the problem, right? Well I want to do the unthinkable. I want to
expose my Reporting Server on the Internet behind an ISA server (in the DMZ).
So to make this work, of course, everyone on the planet needs to use an FQDN
rather than my local machine name.
There's lots of advice on the net and in various technet articles from MS
about how to do this. Just update the ReportServerUrl in the ReportManager
app config file. I did that. Some people believe you should update the
UrlRoot in the ReportServer config file. I've tried that and all
combinations to no avail.
So the deal is if come into the ReportManager virtual using anything other
than the local host name of the machine I get one of two errors (after a long
timeout):
1. Underlying connection was closed: could not establish trust relationship
with remote server.
-or-
2. Underlying connection was closed: unable to connect to the remote server.
I think I've tried everything I can think of. I don't think it could be SSL
related because SSL works if I setup the Reporting server config files to be
based upon the local host name of the machine. My virtual directories in IIS
only permit SSL connectivity to both Reports and ReportServer virtuals.
I also have played around with the SecureConnectionLevel parameter in both
config files (making it something like "2" in each to no avail).
I'm beat! I've tried any and all combinations and just cannot seem to
change the name by which I can access the report server.
Oh, in case you are curious, the FQDN of the internal server is something
like "server1.edc.local". If I setup the config files to come in either via
"server1" or "server1.edc.local" (hey, that's a FQDN, right?) then all works
fine.
The FQDN for the server on the internet will be something like
"www.edc.mycompany.com" which has no relation to the Active Directory domain
name (which ends in .local). Of course, this FQDN gives me serious fits.
Any ideas on what to try next?
JohnWhat's the name on the Certificate used for SSL? Sounds like this
http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
error you are seeing.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John" <John@.discussions.microsoft.com> wrote in message
news:B6A8E286-2598-44AC-9E82-49C219ADACC0@.microsoft.com...
>I don't know how I can succinctly express my problem other than I've got
>all
> the latest bits for SQL Server 2000, Reporting Services, service packs,
> etc... installed. I have Share Point Portal / IIS 6 / Windows 2003 / SQL
> Server 2000 all installed on same box.
> I followed all directions to install Reporting Services correctly under
> this
> configuration and, lo and behold, everything worked as advertised.
> After I got the above stack working under a non SSL mode, I proceeded to
> setup an SSL only option for IIS. No biggie. Everything works just fine!
> I
> created a CA key using OpenSSL and signed my IIS cert request and
> installed
> into IIS and Share Point and SQL Reporting Services are all very cool with
> this. Of course, I installed the CA cert in my Trusted Root Authorities
> on
> the server and my client.
> So what's the problem, right? Well I want to do the unthinkable. I want
> to
> expose my Reporting Server on the Internet behind an ISA server (in the
> DMZ).
> So to make this work, of course, everyone on the planet needs to use an
> FQDN
> rather than my local machine name.
> There's lots of advice on the net and in various technet articles from MS
> about how to do this. Just update the ReportServerUrl in the
> ReportManager
> app config file. I did that. Some people believe you should update the
> UrlRoot in the ReportServer config file. I've tried that and all
> combinations to no avail.
> So the deal is if come into the ReportManager virtual using anything other
> than the local host name of the machine I get one of two errors (after a
> long
> timeout):
> 1. Underlying connection was closed: could not establish trust
> relationship
> with remote server.
> -or-
> 2. Underlying connection was closed: unable to connect to the remote
> server.
> I think I've tried everything I can think of. I don't think it could be
> SSL
> related because SSL works if I setup the Reporting server config files to
> be
> based upon the local host name of the machine. My virtual directories in
> IIS
> only permit SSL connectivity to both Reports and ReportServer virtuals.
> I also have played around with the SecureConnectionLevel parameter in both
> config files (making it something like "2" in each to no avail).
> I'm beat! I've tried any and all combinations and just cannot seem to
> change the name by which I can access the report server.
> Oh, in case you are curious, the FQDN of the internal server is something
> like "server1.edc.local". If I setup the config files to come in either
> via
> "server1" or "server1.edc.local" (hey, that's a FQDN, right?) then all
> works
> fine.
> The FQDN for the server on the internet will be something like
> "www.edc.mycompany.com" which has no relation to the Active Directory
> domain
> name (which ends in .local). Of course, this FQDN gives me serious fits.
> Any ideas on what to try next?
> John|||"Jasper Smith" wrote:
> What's the name on the Certificate used for SSL? Sounds like this
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> error you are seeing.
I neglected to mention (somehow) that as I've tried both the inside and
outside FQDN attempts I do have two certs. I have a cert for the inside
(local) FQDN -- this one works as I said. When I flip all the configs around
to be using the outside FQDN, I use a cert for IIS that exactly matches (case
and all) the outside FQDN. No go. I even restart IIS and the Reporting
service thinking this might be it, but nothing.
Any other tricks to try?
John|||Is it just Report Manager giving the error, can you access the Report Server
web service ok (i.e. just go to https://externalname/ReportServer) and run a
report from there or do you get the same error?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John" <John@.discussions.microsoft.com> wrote in message
news:9FEE56AF-913A-4496-9D6A-C0FFCDA2C143@.microsoft.com...
> "Jasper Smith" wrote:
>> What's the name on the Certificate used for SSL? Sounds like this
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
>> error you are seeing.
> I neglected to mention (somehow) that as I've tried both the inside and
> outside FQDN attempts I do have two certs. I have a cert for the inside
> (local) FQDN -- this one works as I said. When I flip all the configs
> around
> to be using the outside FQDN, I use a cert for IIS that exactly matches
> (case
> and all) the outside FQDN. No go. I even restart IIS and the Reporting
> service thinking this might be it, but nothing.
> Any other tricks to try?
> John|||"Jasper Smith" wrote:
> What's the name on the Certificate used for SSL? Sounds like this
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> error you are seeing.
So the kb article talks about two scenarios. My certs match the URL I am
coming in on (as previously stated in a prior post), but the other scenario
seems more like what I have.
From the kb article:
"Other scenarios exist also. For example, some networks use a different
name-resolution scheme for internal versus external clients. In cases where
the certificate is issued to a server with a public URL (such as
www.adatum.com) and with intranet applications, the internal Domain Name
System (DNS) Server provides a different name for the same server (such as
www.internal.corporate.adatum.com). Requests for this Web service over SSL
may fail. This change is made to enhance the security of Web services that
use SSL."
The kb article subsequently states a possible remedy in unclear terms, as
follows:
"You can change the name-resolution scheme so that DNS provides the same
name for a server. The same name for the server must be used whether the
server is referred to from in the company or from outside the company.
For example, assume that a certificate has been issued to the URL
www.adatum.com. Any Web service application that is referred from outside the
organization is called by using the external DNS resolution schema
(www.adatum.com). When an intranet Web service application is called, the
internal DNS translates the name of the site as
www.internal.corporate.adatum.com. Therefore, any request for the Web Service
over SSL may fail unless you change the name-resolution scheme. "
So what does this really mean? Does it mean I can fix it somehow in DNS
(which I run out of my local AD) or does it mean I must rename my AD domain
(which is edc.local right now) to something that permits me to put the server
in the proper DNS zone (in this case mycompany.com).
What I am looking for right now is a quick fix without having to forklift my
AD into a new domain name. Any thoughts on what it means to change the
name-resolution scheme and what that translates to?
Regards,
John|||"Jasper Smith" wrote:
> Is it just Report Manager giving the error, can you access the Report Server
> web service ok (i.e. just go to https://externalname/ReportServer) and run a
> report from there or do you get the same error?
Yes, you can access the report server directly using either scheme (internal
or external FQDN scheme). This has always seemed to work so the problem is
limited to the ReportManager only as it is using the .NET Web service
technoloy that is really really mad about something.
Geesh -- I hope this gets easier with reporting services because I'm no
script kiddie and I feel like setting up reporting services to work in a real
internet setting is daunting to say the least!
John|||Anyone have any thoughts on the following I posted late last week to this
group? Specifically, the kb article (823177) states the following:
"You can change the name-resolution scheme so that DNS provides the same
name for a server. The same name for the server must be used whether the
server is referred to from in the company or from outside the company"
So I have done essential what this kb article suggest. The internal FQDN
host name on my box is server1.edc.local. Outsiders access this server via
my DMZ ISA server using the URL https://www.edc.mycompany.com.
So in addition to my outside DNS resolving www.edc.mycompany.com to my
front-end ISA server, I setup a split-DNS on the inside that resolves
www.edc.mycompany.com to the same IP address as server1.edc.local.
This *does not work* though. I still get the same error the KB article
describes. So what I am looking for is, do I have to renamed my local AD
domain to something like edc.mycompany.com and then rename server1 to www to
get this to work? Is that what the article's plan of action entails or is
there something else I can try?
John
"John" wrote:
> "Jasper Smith" wrote:
> > What's the name on the Certificate used for SSL? Sounds like this
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> > error you are seeing.
> So the kb article talks about two scenarios. My certs match the URL I am
> coming in on (as previously stated in a prior post), but the other scenario
> seems more like what I have.
> From the kb article:
> "Other scenarios exist also. For example, some networks use a different
> name-resolution scheme for internal versus external clients. In cases where
> the certificate is issued to a server with a public URL (such as
> www.adatum.com) and with intranet applications, the internal Domain Name
> System (DNS) Server provides a different name for the same server (such as
> www.internal.corporate.adatum.com). Requests for this Web service over SSL
> may fail. This change is made to enhance the security of Web services that
> use SSL."
> The kb article subsequently states a possible remedy in unclear terms, as
> follows:
> "You can change the name-resolution scheme so that DNS provides the same
> name for a server. The same name for the server must be used whether the
> server is referred to from in the company or from outside the company.
> For example, assume that a certificate has been issued to the URL
> www.adatum.com. Any Web service application that is referred from outside the
> organization is called by using the external DNS resolution schema
> (www.adatum.com). When an intranet Web service application is called, the
> internal DNS translates the name of the site as
> www.internal.corporate.adatum.com. Therefore, any request for the Web Service
> over SSL may fail unless you change the name-resolution scheme. "
> So what does this really mean? Does it mean I can fix it somehow in DNS
> (which I run out of my local AD) or does it mean I must rename my AD domain
> (which is edc.local right now) to something that permits me to put the server
> in the proper DNS zone (in this case mycompany.com).
> What I am looking for right now is a quick fix without having to forklift my
> AD into a new domain name. Any thoughts on what it means to change the
> name-resolution scheme and what that translates to?
> Regards,
> John|||John,
I am hoping this message will find you. Basically, you need to change the
links in the Reporting Services configuration file to match that of your
external link. There are 2 folders under C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportManager and ReportServer, look for
RSWebApplication.config and RSReportServer.config respectively and change to
(ie https://www.mydomain.com/Reports). Just have to make sure that
www.mydomain.com on the internal network resolves to the INTERNAL ip address
of the web server hosting Reporting Services and sounds like you may have
done that. Basically, INTERNAL clients pings www.mydomain.com will get
10.0.0.5 and EXTERNAL ping www.mydomain.com will get 208.11.111.111. Gluck.
"John" wrote:
> Anyone have any thoughts on the following I posted late last week to this
> group? Specifically, the kb article (823177) states the following:
> "You can change the name-resolution scheme so that DNS provides the same
> name for a server. The same name for the server must be used whether the
> server is referred to from in the company or from outside the company"
> So I have done essential what this kb article suggest. The internal FQDN
> host name on my box is server1.edc.local. Outsiders access this server via
> my DMZ ISA server using the URL https://www.edc.mycompany.com.
> So in addition to my outside DNS resolving www.edc.mycompany.com to my
> front-end ISA server, I setup a split-DNS on the inside that resolves
> www.edc.mycompany.com to the same IP address as server1.edc.local.
> This *does not work* though. I still get the same error the KB article
> describes. So what I am looking for is, do I have to renamed my local AD
> domain to something like edc.mycompany.com and then rename server1 to www to
> get this to work? Is that what the article's plan of action entails or is
> there something else I can try?
> John
> "John" wrote:
> > "Jasper Smith" wrote:
> >
> > > What's the name on the Certificate used for SSL? Sounds like this
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> > > error you are seeing.
> >
> > So the kb article talks about two scenarios. My certs match the URL I am
> > coming in on (as previously stated in a prior post), but the other scenario
> > seems more like what I have.
> >
> > From the kb article:
> >
> > "Other scenarios exist also. For example, some networks use a different
> > name-resolution scheme for internal versus external clients. In cases where
> > the certificate is issued to a server with a public URL (such as
> > www.adatum.com) and with intranet applications, the internal Domain Name
> > System (DNS) Server provides a different name for the same server (such as
> > www.internal.corporate.adatum.com). Requests for this Web service over SSL
> > may fail. This change is made to enhance the security of Web services that
> > use SSL."
> >
> > The kb article subsequently states a possible remedy in unclear terms, as
> > follows:
> >
> > "You can change the name-resolution scheme so that DNS provides the same
> > name for a server. The same name for the server must be used whether the
> > server is referred to from in the company or from outside the company.
> >
> > For example, assume that a certificate has been issued to the URL
> > www.adatum.com. Any Web service application that is referred from outside the
> > organization is called by using the external DNS resolution schema
> > (www.adatum.com). When an intranet Web service application is called, the
> > internal DNS translates the name of the site as
> > www.internal.corporate.adatum.com. Therefore, any request for the Web Service
> > over SSL may fail unless you change the name-resolution scheme. "
> >
> > So what does this really mean? Does it mean I can fix it somehow in DNS
> > (which I run out of my local AD) or does it mean I must rename my AD domain
> > (which is edc.local right now) to something that permits me to put the server
> > in the proper DNS zone (in this case mycompany.com).
> >
> > What I am looking for right now is a quick fix without having to forklift my
> > AD into a new domain name. Any thoughts on what it means to change the
> > name-resolution scheme and what that translates to?
> >
> > Regards,
> >
> > John
the latest bits for SQL Server 2000, Reporting Services, service packs,
etc... installed. I have Share Point Portal / IIS 6 / Windows 2003 / SQL
Server 2000 all installed on same box.
I followed all directions to install Reporting Services correctly under this
configuration and, lo and behold, everything worked as advertised.
After I got the above stack working under a non SSL mode, I proceeded to
setup an SSL only option for IIS. No biggie. Everything works just fine! I
created a CA key using OpenSSL and signed my IIS cert request and installed
into IIS and Share Point and SQL Reporting Services are all very cool with
this. Of course, I installed the CA cert in my Trusted Root Authorities on
the server and my client.
So what's the problem, right? Well I want to do the unthinkable. I want to
expose my Reporting Server on the Internet behind an ISA server (in the DMZ).
So to make this work, of course, everyone on the planet needs to use an FQDN
rather than my local machine name.
There's lots of advice on the net and in various technet articles from MS
about how to do this. Just update the ReportServerUrl in the ReportManager
app config file. I did that. Some people believe you should update the
UrlRoot in the ReportServer config file. I've tried that and all
combinations to no avail.
So the deal is if come into the ReportManager virtual using anything other
than the local host name of the machine I get one of two errors (after a long
timeout):
1. Underlying connection was closed: could not establish trust relationship
with remote server.
-or-
2. Underlying connection was closed: unable to connect to the remote server.
I think I've tried everything I can think of. I don't think it could be SSL
related because SSL works if I setup the Reporting server config files to be
based upon the local host name of the machine. My virtual directories in IIS
only permit SSL connectivity to both Reports and ReportServer virtuals.
I also have played around with the SecureConnectionLevel parameter in both
config files (making it something like "2" in each to no avail).
I'm beat! I've tried any and all combinations and just cannot seem to
change the name by which I can access the report server.
Oh, in case you are curious, the FQDN of the internal server is something
like "server1.edc.local". If I setup the config files to come in either via
"server1" or "server1.edc.local" (hey, that's a FQDN, right?) then all works
fine.
The FQDN for the server on the internet will be something like
"www.edc.mycompany.com" which has no relation to the Active Directory domain
name (which ends in .local). Of course, this FQDN gives me serious fits.
Any ideas on what to try next?
JohnWhat's the name on the Certificate used for SSL? Sounds like this
http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
error you are seeing.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John" <John@.discussions.microsoft.com> wrote in message
news:B6A8E286-2598-44AC-9E82-49C219ADACC0@.microsoft.com...
>I don't know how I can succinctly express my problem other than I've got
>all
> the latest bits for SQL Server 2000, Reporting Services, service packs,
> etc... installed. I have Share Point Portal / IIS 6 / Windows 2003 / SQL
> Server 2000 all installed on same box.
> I followed all directions to install Reporting Services correctly under
> this
> configuration and, lo and behold, everything worked as advertised.
> After I got the above stack working under a non SSL mode, I proceeded to
> setup an SSL only option for IIS. No biggie. Everything works just fine!
> I
> created a CA key using OpenSSL and signed my IIS cert request and
> installed
> into IIS and Share Point and SQL Reporting Services are all very cool with
> this. Of course, I installed the CA cert in my Trusted Root Authorities
> on
> the server and my client.
> So what's the problem, right? Well I want to do the unthinkable. I want
> to
> expose my Reporting Server on the Internet behind an ISA server (in the
> DMZ).
> So to make this work, of course, everyone on the planet needs to use an
> FQDN
> rather than my local machine name.
> There's lots of advice on the net and in various technet articles from MS
> about how to do this. Just update the ReportServerUrl in the
> ReportManager
> app config file. I did that. Some people believe you should update the
> UrlRoot in the ReportServer config file. I've tried that and all
> combinations to no avail.
> So the deal is if come into the ReportManager virtual using anything other
> than the local host name of the machine I get one of two errors (after a
> long
> timeout):
> 1. Underlying connection was closed: could not establish trust
> relationship
> with remote server.
> -or-
> 2. Underlying connection was closed: unable to connect to the remote
> server.
> I think I've tried everything I can think of. I don't think it could be
> SSL
> related because SSL works if I setup the Reporting server config files to
> be
> based upon the local host name of the machine. My virtual directories in
> IIS
> only permit SSL connectivity to both Reports and ReportServer virtuals.
> I also have played around with the SecureConnectionLevel parameter in both
> config files (making it something like "2" in each to no avail).
> I'm beat! I've tried any and all combinations and just cannot seem to
> change the name by which I can access the report server.
> Oh, in case you are curious, the FQDN of the internal server is something
> like "server1.edc.local". If I setup the config files to come in either
> via
> "server1" or "server1.edc.local" (hey, that's a FQDN, right?) then all
> works
> fine.
> The FQDN for the server on the internet will be something like
> "www.edc.mycompany.com" which has no relation to the Active Directory
> domain
> name (which ends in .local). Of course, this FQDN gives me serious fits.
> Any ideas on what to try next?
> John|||"Jasper Smith" wrote:
> What's the name on the Certificate used for SSL? Sounds like this
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> error you are seeing.
I neglected to mention (somehow) that as I've tried both the inside and
outside FQDN attempts I do have two certs. I have a cert for the inside
(local) FQDN -- this one works as I said. When I flip all the configs around
to be using the outside FQDN, I use a cert for IIS that exactly matches (case
and all) the outside FQDN. No go. I even restart IIS and the Reporting
service thinking this might be it, but nothing.
Any other tricks to try?
John|||Is it just Report Manager giving the error, can you access the Report Server
web service ok (i.e. just go to https://externalname/ReportServer) and run a
report from there or do you get the same error?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"John" <John@.discussions.microsoft.com> wrote in message
news:9FEE56AF-913A-4496-9D6A-C0FFCDA2C143@.microsoft.com...
> "Jasper Smith" wrote:
>> What's the name on the Certificate used for SSL? Sounds like this
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
>> error you are seeing.
> I neglected to mention (somehow) that as I've tried both the inside and
> outside FQDN attempts I do have two certs. I have a cert for the inside
> (local) FQDN -- this one works as I said. When I flip all the configs
> around
> to be using the outside FQDN, I use a cert for IIS that exactly matches
> (case
> and all) the outside FQDN. No go. I even restart IIS and the Reporting
> service thinking this might be it, but nothing.
> Any other tricks to try?
> John|||"Jasper Smith" wrote:
> What's the name on the Certificate used for SSL? Sounds like this
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> error you are seeing.
So the kb article talks about two scenarios. My certs match the URL I am
coming in on (as previously stated in a prior post), but the other scenario
seems more like what I have.
From the kb article:
"Other scenarios exist also. For example, some networks use a different
name-resolution scheme for internal versus external clients. In cases where
the certificate is issued to a server with a public URL (such as
www.adatum.com) and with intranet applications, the internal Domain Name
System (DNS) Server provides a different name for the same server (such as
www.internal.corporate.adatum.com). Requests for this Web service over SSL
may fail. This change is made to enhance the security of Web services that
use SSL."
The kb article subsequently states a possible remedy in unclear terms, as
follows:
"You can change the name-resolution scheme so that DNS provides the same
name for a server. The same name for the server must be used whether the
server is referred to from in the company or from outside the company.
For example, assume that a certificate has been issued to the URL
www.adatum.com. Any Web service application that is referred from outside the
organization is called by using the external DNS resolution schema
(www.adatum.com). When an intranet Web service application is called, the
internal DNS translates the name of the site as
www.internal.corporate.adatum.com. Therefore, any request for the Web Service
over SSL may fail unless you change the name-resolution scheme. "
So what does this really mean? Does it mean I can fix it somehow in DNS
(which I run out of my local AD) or does it mean I must rename my AD domain
(which is edc.local right now) to something that permits me to put the server
in the proper DNS zone (in this case mycompany.com).
What I am looking for right now is a quick fix without having to forklift my
AD into a new domain name. Any thoughts on what it means to change the
name-resolution scheme and what that translates to?
Regards,
John|||"Jasper Smith" wrote:
> Is it just Report Manager giving the error, can you access the Report Server
> web service ok (i.e. just go to https://externalname/ReportServer) and run a
> report from there or do you get the same error?
Yes, you can access the report server directly using either scheme (internal
or external FQDN scheme). This has always seemed to work so the problem is
limited to the ReportManager only as it is using the .NET Web service
technoloy that is really really mad about something.
Geesh -- I hope this gets easier with reporting services because I'm no
script kiddie and I feel like setting up reporting services to work in a real
internet setting is daunting to say the least!
John|||Anyone have any thoughts on the following I posted late last week to this
group? Specifically, the kb article (823177) states the following:
"You can change the name-resolution scheme so that DNS provides the same
name for a server. The same name for the server must be used whether the
server is referred to from in the company or from outside the company"
So I have done essential what this kb article suggest. The internal FQDN
host name on my box is server1.edc.local. Outsiders access this server via
my DMZ ISA server using the URL https://www.edc.mycompany.com.
So in addition to my outside DNS resolving www.edc.mycompany.com to my
front-end ISA server, I setup a split-DNS on the inside that resolves
www.edc.mycompany.com to the same IP address as server1.edc.local.
This *does not work* though. I still get the same error the KB article
describes. So what I am looking for is, do I have to renamed my local AD
domain to something like edc.mycompany.com and then rename server1 to www to
get this to work? Is that what the article's plan of action entails or is
there something else I can try?
John
"John" wrote:
> "Jasper Smith" wrote:
> > What's the name on the Certificate used for SSL? Sounds like this
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> > error you are seeing.
> So the kb article talks about two scenarios. My certs match the URL I am
> coming in on (as previously stated in a prior post), but the other scenario
> seems more like what I have.
> From the kb article:
> "Other scenarios exist also. For example, some networks use a different
> name-resolution scheme for internal versus external clients. In cases where
> the certificate is issued to a server with a public URL (such as
> www.adatum.com) and with intranet applications, the internal Domain Name
> System (DNS) Server provides a different name for the same server (such as
> www.internal.corporate.adatum.com). Requests for this Web service over SSL
> may fail. This change is made to enhance the security of Web services that
> use SSL."
> The kb article subsequently states a possible remedy in unclear terms, as
> follows:
> "You can change the name-resolution scheme so that DNS provides the same
> name for a server. The same name for the server must be used whether the
> server is referred to from in the company or from outside the company.
> For example, assume that a certificate has been issued to the URL
> www.adatum.com. Any Web service application that is referred from outside the
> organization is called by using the external DNS resolution schema
> (www.adatum.com). When an intranet Web service application is called, the
> internal DNS translates the name of the site as
> www.internal.corporate.adatum.com. Therefore, any request for the Web Service
> over SSL may fail unless you change the name-resolution scheme. "
> So what does this really mean? Does it mean I can fix it somehow in DNS
> (which I run out of my local AD) or does it mean I must rename my AD domain
> (which is edc.local right now) to something that permits me to put the server
> in the proper DNS zone (in this case mycompany.com).
> What I am looking for right now is a quick fix without having to forklift my
> AD into a new domain name. Any thoughts on what it means to change the
> name-resolution scheme and what that translates to?
> Regards,
> John|||John,
I am hoping this message will find you. Basically, you need to change the
links in the Reporting Services configuration file to match that of your
external link. There are 2 folders under C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportManager and ReportServer, look for
RSWebApplication.config and RSReportServer.config respectively and change to
(ie https://www.mydomain.com/Reports). Just have to make sure that
www.mydomain.com on the internal network resolves to the INTERNAL ip address
of the web server hosting Reporting Services and sounds like you may have
done that. Basically, INTERNAL clients pings www.mydomain.com will get
10.0.0.5 and EXTERNAL ping www.mydomain.com will get 208.11.111.111. Gluck.
"John" wrote:
> Anyone have any thoughts on the following I posted late last week to this
> group? Specifically, the kb article (823177) states the following:
> "You can change the name-resolution scheme so that DNS provides the same
> name for a server. The same name for the server must be used whether the
> server is referred to from in the company or from outside the company"
> So I have done essential what this kb article suggest. The internal FQDN
> host name on my box is server1.edc.local. Outsiders access this server via
> my DMZ ISA server using the URL https://www.edc.mycompany.com.
> So in addition to my outside DNS resolving www.edc.mycompany.com to my
> front-end ISA server, I setup a split-DNS on the inside that resolves
> www.edc.mycompany.com to the same IP address as server1.edc.local.
> This *does not work* though. I still get the same error the KB article
> describes. So what I am looking for is, do I have to renamed my local AD
> domain to something like edc.mycompany.com and then rename server1 to www to
> get this to work? Is that what the article's plan of action entails or is
> there something else I can try?
> John
> "John" wrote:
> > "Jasper Smith" wrote:
> >
> > > What's the name on the Certificate used for SSL? Sounds like this
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;823177 from the
> > > error you are seeing.
> >
> > So the kb article talks about two scenarios. My certs match the URL I am
> > coming in on (as previously stated in a prior post), but the other scenario
> > seems more like what I have.
> >
> > From the kb article:
> >
> > "Other scenarios exist also. For example, some networks use a different
> > name-resolution scheme for internal versus external clients. In cases where
> > the certificate is issued to a server with a public URL (such as
> > www.adatum.com) and with intranet applications, the internal Domain Name
> > System (DNS) Server provides a different name for the same server (such as
> > www.internal.corporate.adatum.com). Requests for this Web service over SSL
> > may fail. This change is made to enhance the security of Web services that
> > use SSL."
> >
> > The kb article subsequently states a possible remedy in unclear terms, as
> > follows:
> >
> > "You can change the name-resolution scheme so that DNS provides the same
> > name for a server. The same name for the server must be used whether the
> > server is referred to from in the company or from outside the company.
> >
> > For example, assume that a certificate has been issued to the URL
> > www.adatum.com. Any Web service application that is referred from outside the
> > organization is called by using the external DNS resolution schema
> > (www.adatum.com). When an intranet Web service application is called, the
> > internal DNS translates the name of the site as
> > www.internal.corporate.adatum.com. Therefore, any request for the Web Service
> > over SSL may fail unless you change the name-resolution scheme. "
> >
> > So what does this really mean? Does it mean I can fix it somehow in DNS
> > (which I run out of my local AD) or does it mean I must rename my AD domain
> > (which is edc.local right now) to something that permits me to put the server
> > in the proper DNS zone (in this case mycompany.com).
> >
> > What I am looking for right now is a quick fix without having to forklift my
> > AD into a new domain name. Any thoughts on what it means to change the
> > name-resolution scheme and what that translates to?
> >
> > Regards,
> >
> > John
ReportManager over SSL
Anyone else having problems or have solved problems, running Report Manager
over SSL?Hi,
I do have an issue with SSL and reportmanager, the reportserver interface is
fine, but reportmanager at /Reports gives
"The underlying connection was closed: Could not establish trust..." message
Am using a self-issued cert, but reportserver is OK, been through lots,
still no joy...
Chris
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23fzPiL%23MGHA.3728@.tk2msftngp13.phx.gbl...
> Anyone else having problems or have solved problems, running Report
> Manager over SSL?
>
over SSL?Hi,
I do have an issue with SSL and reportmanager, the reportserver interface is
fine, but reportmanager at /Reports gives
"The underlying connection was closed: Could not establish trust..." message
Am using a self-issued cert, but reportserver is OK, been through lots,
still no joy...
Chris
"Kevin Antel" <kevina@.cqlcorp.com> wrote in message
news:%23fzPiL%23MGHA.3728@.tk2msftngp13.phx.gbl...
> Anyone else having problems or have solved problems, running Report
> Manager over SSL?
>
ReportManager ok button doesn't work
ReportManager ok button doesn't work, I access the reoport manager
http://213.63.184.203/reports apperantly everything is ok. But when try to
create a new role the ok button doesn't wok. What can be wrong?
Thanks in advance
Maria JoãoI am having exactly the same problem.
When you click Ok, nothing happens. I have checked that active scripting is
on.
Is there anything that I should do?
We have only started experiencing this problem after installing sp2.
Paul
"Maria João Lima" wrote:
> ReportManager ok button doesn't work, I access the reoport manager
> http://213.63.184.203/reports apperantly everything is ok. But when try to
> create a new role the ok button doesn't wok. What can be wrong?
>
> Thanks in advance
> Maria João
>
>|||Usually this has to do with having anonoymous access enabled for the
website.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
>I am having exactly the same problem.
> When you click Ok, nothing happens. I have checked that active scripting
> is
> on.
> Is there anything that I should do?
> We have only started experiencing this problem after installing sp2.
> Paul
> "Maria João Lima" wrote:
>> ReportManager ok button doesn't work, I access the reoport manager
>> http://213.63.184.203/reports apperantly everything is ok. But when try
>> to
>> create a new role the ok button doesn't wok. What can be wrong?
>>
>> Thanks in advance
>> Maria João
>>|||Anonoymous access is disabled in IIS
Cheers
Paul
"Bruce L-C [MVP]" wrote:
> Usually this has to do with having anonoymous access enabled for the
> website.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
> >I am having exactly the same problem.
> >
> > When you click Ok, nothing happens. I have checked that active scripting
> > is
> > on.
> > Is there anything that I should do?
> >
> > We have only started experiencing this problem after installing sp2.
> >
> > Paul
> >
> > "Maria João Lima" wrote:
> >
> >> ReportManager ok button doesn't work, I access the reoport manager
> >> http://213.63.184.203/reports apperantly everything is ok. But when try
> >> to
> >> create a new role the ok button doesn't wok. What can be wrong?
> >>
> >>
> >>
> >> Thanks in advance
> >>
> >> Maria João
> >>
> >>
> >>
>
>|||Are you an administrator of the machine where RS is installed? You need to
be in the administrators group (at least initially, until you create a role
for this).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:B2DEFD3F-79BC-4B26-AD76-09AA5B180F30@.microsoft.com...
> Anonoymous access is disabled in IIS
> Cheers
> Paul
> "Bruce L-C [MVP]" wrote:
>> Usually this has to do with having anonoymous access enabled for the
>> website.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
>> >I am having exactly the same problem.
>> >
>> > When you click Ok, nothing happens. I have checked that active
>> > scripting
>> > is
>> > on.
>> > Is there anything that I should do?
>> >
>> > We have only started experiencing this problem after installing sp2.
>> >
>> > Paul
>> >
>> > "Maria João Lima" wrote:
>> >
>> >> ReportManager ok button doesn't work, I access the reoport manager
>> >> http://213.63.184.203/reports apperantly everything is ok. But when
>> >> try
>> >> to
>> >> create a new role the ok button doesn't wok. What can be wrong?
>> >>
>> >>
>> >>
>> >> Thanks in advance
>> >>
>> >> Maria João
>> >>
>> >>
>> >>
>>|||I was logged in as admin. We think we have found a fix now.
When browsing reports on the server it comes up with an error message
suggesting reregistering iis
C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -c
"Bruce L-C [MVP]" wrote:
> Are you an administrator of the machine where RS is installed? You need to
> be in the administrators group (at least initially, until you create a role
> for this).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:B2DEFD3F-79BC-4B26-AD76-09AA5B180F30@.microsoft.com...
> > Anonoymous access is disabled in IIS
> >
> > Cheers
> > Paul
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Usually this has to do with having anonoymous access enabled for the
> >> website.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
> >> >I am having exactly the same problem.
> >> >
> >> > When you click Ok, nothing happens. I have checked that active
> >> > scripting
> >> > is
> >> > on.
> >> > Is there anything that I should do?
> >> >
> >> > We have only started experiencing this problem after installing sp2.
> >> >
> >> > Paul
> >> >
> >> > "Maria João Lima" wrote:
> >> >
> >> >> ReportManager ok button doesn't work, I access the reoport manager
> >> >> http://213.63.184.203/reports apperantly everything is ok. But when
> >> >> try
> >> >> to
> >> >> create a new role the ok button doesn't wok. What can be wrong?
> >> >>
> >> >>
> >> >>
> >> >> Thanks in advance
> >> >>
> >> >> Maria João
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
http://213.63.184.203/reports apperantly everything is ok. But when try to
create a new role the ok button doesn't wok. What can be wrong?
Thanks in advance
Maria JoãoI am having exactly the same problem.
When you click Ok, nothing happens. I have checked that active scripting is
on.
Is there anything that I should do?
We have only started experiencing this problem after installing sp2.
Paul
"Maria João Lima" wrote:
> ReportManager ok button doesn't work, I access the reoport manager
> http://213.63.184.203/reports apperantly everything is ok. But when try to
> create a new role the ok button doesn't wok. What can be wrong?
>
> Thanks in advance
> Maria João
>
>|||Usually this has to do with having anonoymous access enabled for the
website.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
>I am having exactly the same problem.
> When you click Ok, nothing happens. I have checked that active scripting
> is
> on.
> Is there anything that I should do?
> We have only started experiencing this problem after installing sp2.
> Paul
> "Maria João Lima" wrote:
>> ReportManager ok button doesn't work, I access the reoport manager
>> http://213.63.184.203/reports apperantly everything is ok. But when try
>> to
>> create a new role the ok button doesn't wok. What can be wrong?
>>
>> Thanks in advance
>> Maria João
>>|||Anonoymous access is disabled in IIS
Cheers
Paul
"Bruce L-C [MVP]" wrote:
> Usually this has to do with having anonoymous access enabled for the
> website.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
> >I am having exactly the same problem.
> >
> > When you click Ok, nothing happens. I have checked that active scripting
> > is
> > on.
> > Is there anything that I should do?
> >
> > We have only started experiencing this problem after installing sp2.
> >
> > Paul
> >
> > "Maria João Lima" wrote:
> >
> >> ReportManager ok button doesn't work, I access the reoport manager
> >> http://213.63.184.203/reports apperantly everything is ok. But when try
> >> to
> >> create a new role the ok button doesn't wok. What can be wrong?
> >>
> >>
> >>
> >> Thanks in advance
> >>
> >> Maria João
> >>
> >>
> >>
>
>|||Are you an administrator of the machine where RS is installed? You need to
be in the administrators group (at least initially, until you create a role
for this).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:B2DEFD3F-79BC-4B26-AD76-09AA5B180F30@.microsoft.com...
> Anonoymous access is disabled in IIS
> Cheers
> Paul
> "Bruce L-C [MVP]" wrote:
>> Usually this has to do with having anonoymous access enabled for the
>> website.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
>> >I am having exactly the same problem.
>> >
>> > When you click Ok, nothing happens. I have checked that active
>> > scripting
>> > is
>> > on.
>> > Is there anything that I should do?
>> >
>> > We have only started experiencing this problem after installing sp2.
>> >
>> > Paul
>> >
>> > "Maria João Lima" wrote:
>> >
>> >> ReportManager ok button doesn't work, I access the reoport manager
>> >> http://213.63.184.203/reports apperantly everything is ok. But when
>> >> try
>> >> to
>> >> create a new role the ok button doesn't wok. What can be wrong?
>> >>
>> >>
>> >>
>> >> Thanks in advance
>> >>
>> >> Maria João
>> >>
>> >>
>> >>
>>|||I was logged in as admin. We think we have found a fix now.
When browsing reports on the server it comes up with an error message
suggesting reregistering iis
C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -c
"Bruce L-C [MVP]" wrote:
> Are you an administrator of the machine where RS is installed? You need to
> be in the administrators group (at least initially, until you create a role
> for this).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:B2DEFD3F-79BC-4B26-AD76-09AA5B180F30@.microsoft.com...
> > Anonoymous access is disabled in IIS
> >
> > Cheers
> > Paul
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Usually this has to do with having anonoymous access enabled for the
> >> website.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> >> news:B11EA9F5-40BE-4F98-A737-54CB793EC548@.microsoft.com...
> >> >I am having exactly the same problem.
> >> >
> >> > When you click Ok, nothing happens. I have checked that active
> >> > scripting
> >> > is
> >> > on.
> >> > Is there anything that I should do?
> >> >
> >> > We have only started experiencing this problem after installing sp2.
> >> >
> >> > Paul
> >> >
> >> > "Maria João Lima" wrote:
> >> >
> >> >> ReportManager ok button doesn't work, I access the reoport manager
> >> >> http://213.63.184.203/reports apperantly everything is ok. But when
> >> >> try
> >> >> to
> >> >> create a new role the ok button doesn't wok. What can be wrong?
> >> >>
> >> >>
> >> >>
> >> >> Thanks in advance
> >> >>
> >> >> Maria João
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
ReportManager is faster than ReportServer-why?
I have a report based on a stored procedure. The procedure runs very fast
from Query Analyzer. The Report I build from it runs a little slower
in "Preview", I assume due to the Grouping I am doing. It takes about 1 sec.
Then when I move it to production and view it through ReportManager is it
slower,
maybe 3 sec. I wish I knew why.
But when I run it via URL from Reportserver, like this:
http://serveripname/Reportserver?/InstructorReports/AdminListAll"
it runs a couple of seconds slower yet.
Does anyone know why the rendor time isn't the same in all 3 cases?
thanks,
VinceUsing instructions on
http://msdn.microsoft.com/library/en-us/rsadmin/htm/arp_rslogfiles_v1_88gy.asp,
you should be able to pull down ExecutionLog details for analysis. This
will let you look at each report exeuciton to see if there really is any
difference in data retrieval, processing and render times. After you use DTS
to pull down the RS Execution Log details, run SELECT * FROM
[RSExecutionLog].[dbo].[ExecutionLogs] within Query Analyzer to look for
differences.
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:434FE938-0D45-4527-923E-8E007C930F5C@.microsoft.com...
>I have a report based on a stored procedure. The procedure runs very fast
> from Query Analyzer. The Report I build from it runs a little slower
> in "Preview", I assume due to the Grouping I am doing. It takes about 1
> sec.
> Then when I move it to production and view it through ReportManager is it
> slower,
> maybe 3 sec. I wish I knew why.
> But when I run it via URL from Reportserver, like this:
> http://serveripname/Reportserver?/InstructorReports/AdminListAll"
> it runs a couple of seconds slower yet.
> Does anyone know why the rendor time isn't the same in all 3 cases?
> thanks,
> Vince
>
from Query Analyzer. The Report I build from it runs a little slower
in "Preview", I assume due to the Grouping I am doing. It takes about 1 sec.
Then when I move it to production and view it through ReportManager is it
slower,
maybe 3 sec. I wish I knew why.
But when I run it via URL from Reportserver, like this:
http://serveripname/Reportserver?/InstructorReports/AdminListAll"
it runs a couple of seconds slower yet.
Does anyone know why the rendor time isn't the same in all 3 cases?
thanks,
VinceUsing instructions on
http://msdn.microsoft.com/library/en-us/rsadmin/htm/arp_rslogfiles_v1_88gy.asp,
you should be able to pull down ExecutionLog details for analysis. This
will let you look at each report exeuciton to see if there really is any
difference in data retrieval, processing and render times. After you use DTS
to pull down the RS Execution Log details, run SELECT * FROM
[RSExecutionLog].[dbo].[ExecutionLogs] within Query Analyzer to look for
differences.
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:434FE938-0D45-4527-923E-8E007C930F5C@.microsoft.com...
>I have a report based on a stored procedure. The procedure runs very fast
> from Query Analyzer. The Report I build from it runs a little slower
> in "Preview", I assume due to the Grouping I am doing. It takes about 1
> sec.
> Then when I move it to production and view it through ReportManager is it
> slower,
> maybe 3 sec. I wish I knew why.
> But when I run it via URL from Reportserver, like this:
> http://serveripname/Reportserver?/InstructorReports/AdminListAll"
> it runs a couple of seconds slower yet.
> Does anyone know why the rendor time isn't the same in all 3 cases?
> thanks,
> Vince
>
Reportmanager failed to load from internet as a webapplication
I works fine when I run from our lan by a IIS virtual directory. But using
reportmanager from a IIS application outside the lan as a true
webapplication, the reportmanager produce wrong paths for controls. E.x.
http://images/48folderopen.jpg There should have been a domain in front of
/images. I haven't been able to find any parameters in config's to meet this
problem.
Regards
Henrik Juel
GBS A/S
DenmarkI have same probleme, anybody have the solution'
"Henrik Juel" <hjh@.gbs.dk> a écrit dans le message de
news:clsmdo$2bti$1@.news.cybercity.dk...
> I works fine when I run from our lan by a IIS virtual directory. But using
> reportmanager from a IIS application outside the lan as a true
> webapplication, the reportmanager produce wrong paths for controls. E.x.
> http://images/48folderopen.jpg There should have been a domain in front of
> /images. I haven't been able to find any parameters in config's to meet
this
> problem.
> Regards
> Henrik Juel
> GBS A/S
> Denmark
>|||Have you added the <ReportServerExternalURL> tag to the
c:\programfiles\microsoft sql server\mssql\reporting services\report anager\
rswebapplication.config file as below?
<Configuration>
<UI>
<ReportServerUrl>http://servername/ReportServer</ReportServerUrl>
<ReportServerExternalURL>http://www.domain.org/ReportServer</ReportServerExt
ernalURL>
</UI>
Ken
"Henrik Juel" <hjh@.gbs.dk> wrote in message
news:clsmdo$2bti$1@.news.cybercity.dk...
> I works fine when I run from our lan by a IIS virtual directory. But using
> reportmanager from a IIS application outside the lan as a true
> webapplication, the reportmanager produce wrong paths for controls. E.x.
> http://images/48folderopen.jpg There should have been a domain in front of
> /images. I haven't been able to find any parameters in config's to meet
this
> problem.
> Regards
> Henrik Juel
> GBS A/S
> Denmark
>|||Hello Ken
After reading others posting about this topic, I have tried the tag
<ReportServerExternalURL>. But it made no difference. I belive in this setup
there is a ok connection from the reportmanager to the reportserver.
"Ken" wrote:
> Have you added the <ReportServerExternalURL> tag to the
> c:\programfiles\microsoft sql server\mssql\reporting services\report anager\
> rswebapplication.config file as below?
> <Configuration>
> <UI>
> <ReportServerUrl>http://servername/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>http://www.domain.org/ReportServer</ReportServerExt
> ernalURL>
> </UI>
> Ken
> "Henrik Juel" <hjh@.gbs.dk> wrote in message
> news:clsmdo$2bti$1@.news.cybercity.dk...
> > I works fine when I run from our lan by a IIS virtual directory. But using
> > reportmanager from a IIS application outside the lan as a true
> > webapplication, the reportmanager produce wrong paths for controls. E.x.
> > http://images/48folderopen.jpg There should have been a domain in front of
> > /images. I haven't been able to find any parameters in config's to meet
> this
> > problem.
> >
> > Regards
> >
> > Henrik Juel
> > GBS A/S
> > Denmark
> >
> >
>
>
reportmanager from a IIS application outside the lan as a true
webapplication, the reportmanager produce wrong paths for controls. E.x.
http://images/48folderopen.jpg There should have been a domain in front of
/images. I haven't been able to find any parameters in config's to meet this
problem.
Regards
Henrik Juel
GBS A/S
DenmarkI have same probleme, anybody have the solution'
"Henrik Juel" <hjh@.gbs.dk> a écrit dans le message de
news:clsmdo$2bti$1@.news.cybercity.dk...
> I works fine when I run from our lan by a IIS virtual directory. But using
> reportmanager from a IIS application outside the lan as a true
> webapplication, the reportmanager produce wrong paths for controls. E.x.
> http://images/48folderopen.jpg There should have been a domain in front of
> /images. I haven't been able to find any parameters in config's to meet
this
> problem.
> Regards
> Henrik Juel
> GBS A/S
> Denmark
>|||Have you added the <ReportServerExternalURL> tag to the
c:\programfiles\microsoft sql server\mssql\reporting services\report anager\
rswebapplication.config file as below?
<Configuration>
<UI>
<ReportServerUrl>http://servername/ReportServer</ReportServerUrl>
<ReportServerExternalURL>http://www.domain.org/ReportServer</ReportServerExt
ernalURL>
</UI>
Ken
"Henrik Juel" <hjh@.gbs.dk> wrote in message
news:clsmdo$2bti$1@.news.cybercity.dk...
> I works fine when I run from our lan by a IIS virtual directory. But using
> reportmanager from a IIS application outside the lan as a true
> webapplication, the reportmanager produce wrong paths for controls. E.x.
> http://images/48folderopen.jpg There should have been a domain in front of
> /images. I haven't been able to find any parameters in config's to meet
this
> problem.
> Regards
> Henrik Juel
> GBS A/S
> Denmark
>|||Hello Ken
After reading others posting about this topic, I have tried the tag
<ReportServerExternalURL>. But it made no difference. I belive in this setup
there is a ok connection from the reportmanager to the reportserver.
"Ken" wrote:
> Have you added the <ReportServerExternalURL> tag to the
> c:\programfiles\microsoft sql server\mssql\reporting services\report anager\
> rswebapplication.config file as below?
> <Configuration>
> <UI>
> <ReportServerUrl>http://servername/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>http://www.domain.org/ReportServer</ReportServerExt
> ernalURL>
> </UI>
> Ken
> "Henrik Juel" <hjh@.gbs.dk> wrote in message
> news:clsmdo$2bti$1@.news.cybercity.dk...
> > I works fine when I run from our lan by a IIS virtual directory. But using
> > reportmanager from a IIS application outside the lan as a true
> > webapplication, the reportmanager produce wrong paths for controls. E.x.
> > http://images/48folderopen.jpg There should have been a domain in front of
> > /images. I haven't been able to find any parameters in config's to meet
> this
> > problem.
> >
> > Regards
> >
> > Henrik Juel
> > GBS A/S
> > Denmark
> >
> >
>
>
Reportmanager failed to load from internet as a webapplication
I works fine when I run from our lan by a IIS virtual directory. But using
reportmanager from a IIS application outside the lan as a true
webapplication, the reportmanager produce wrong paths for controls. E.x.
http://images/48folderopen.jpg There should have been a domain in front of
/images. I haven't been able to find any parameters in config's to meet this
problem.
Regards
Henrik Juel
GBS A/S
DenmarkHi Henrik,
Thanks for your post.
From your descriptions, I understood that you could not access your Report
Manager via Internet while it's OK for intrannet. Have I understood you?
Correct me if i was wrong.
Based on my scope, it seems you should modify your <ReportServerUrl> Tag
for the remote access. Go look at the Report Manager configuration
file,RSWebApplication.config. There is a UI section
<UI>
<ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
>
</UI>
Change it to
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
or you could find another way in charpter "Deploying a Report Server for
Internet Access" under Topic "Enterprise Deployment Model" in Reporting
Services Books Online.
Last but not the least, make sure you follow the security practices before
you opening the Internet Access:)
Hope this helps and if you have any questions or concerns, don't hesitate
to let me know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
Thanks for your instant answer. And yes you do understand me.
I haved tried the <ReportServerVirtualDirectory> tag in the
RSWebApplication.config file but it didn't made any difference to this
problem. I have read the chapter in the online book as I have read about
this topic in my Wrox book. I was not able to find this issue.
When starting the reportmanager from http://rs.gbs.dk the reportmanager
application do have connection to the reportserver, as it is able to show
folders, but fail to work with fully urls. E.x. the image problem stated
earlier.
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> Thanks for your post.
> From your descriptions, I understood that you could not access your Report
> Manager via Internet while it's OK for intrannet. Have I understood you?
> Correct me if i was wrong.
> Based on my scope, it seems you should modify your <ReportServerUrl> Tag
> for the remote access. Go look at the Report Manager configuration
> file,RSWebApplication.config. There is a UI section
> <UI>
> <ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
> >
> </UI>
> Change it to
> <UI>
> <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
> </UI>
> or you could find another way in charpter "Deploying a Report Server for
> Internet Access" under Topic "Enterprise Deployment Model" in Reporting
> Services Books Online.
> Last but not the least, make sure you follow the security practices before
> you opening the Internet Access:)
> Hope this helps and if you have any questions or concerns, don't hesitate
> to let me know. We are always here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>|||Hi Henrik,
If the Report Manager and Report Server are on the same machine then remove
the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
in the config file - and replace with <ReportServerVirtualDirectory>
Let me know whether this works
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
Both applications are on the same machine.
And I have only the <ReportServerVirtualDirectory> tag in the
rswebapplication.config.
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
I have created a virtual directory in the reportmanager root, which point to
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
where the server originally is installed.
So I belive It doesn't work.
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> If the Report Manager and Report Server are on the same machine then remove
> the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
> in the config file - and replace with <ReportServerVirtualDirectory>
> Let me know whether this works
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>
>
>
>|||Hi Henrik,
First of all, I need to confirm that how do get the following link. Is it
in report manager when he right click a image->Properties to see the link
of the image? http://images/48folderopen.jpg
Secondly, please make sure that 'images' are in the IIS manager the image
folder:
1). Expand IIS server->Web sites->Default Website->Reports->Images
2). Right click Images->Properties->Directory and check if "The designated
directory" is used and "reports\images" is listed.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
1. Yes I have the http://images/48folderopen.jpg from right clicking a image
in reportmanager.
2. The IIS settings are as you describe
You are welcome to contact me on +45 20282851 or on email : hjh@.gbs.dk for a
login to http://rs.gbs.dk
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> First of all, I need to confirm that how do get the following link. Is it
> in report manager when he right click a image->Properties to see the link
> of the image? http://images/48folderopen.jpg
> Secondly, please make sure that 'images' are in the IIS manager the image
> folder:
> 1). Expand IIS server->Web sites->Default Website->Reports->Images
> 2). Right click Images->Properties->Directory and check if "The designated
> directory" is used and "reports\images" is listed.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Henrik,
Looking at the nature of this issue, I am afraid we need more time
researching on this issue and this issue was critical to your business, I
would like to suggest you open an incidnet call with Microsoft Support
Professional through Microsoft Product Support Services. You can contact
Microsoft Product Support directly to discuss additional support options
you may have available, by contacting us at 1-(800)936-5800 or by choosing
one of the options listed at
http://support.microsoft.com/directory/overview.asp
If you'd still like to continue working via the newsgroup, I want to set
your expectations that the issue might take a long time to narrow down.
During the course of troubleshooting, we may redirect you to PSS if
required.
For now, I doubt it might be a IIS issue instead of Reporting Services one
and please let me know the answers for the following questions
1. If you are browsing the Report Manager *Locally* via domain name
(http://rs.gbs.dk), will it shows as expected?
If you are browsing via domain name within the intrannet, will it shows as
expected?
2. Open the Web site property,
Click Advanced Button in Web site identification of Web Site Tab
Select Default in Multiple identities for the Web site, Click Edit...
Let me know whether there is anything in the Host Header value
3. Is it possible for you to post IIS logs here? You could also send it to
me if you think it was critical for your business. My email address was
v-mingqc@.online.microsoft.com (please remove "online", it's only for SPAM,
thanks:-)
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi Henrik,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions/ information I've posted, please don't hesitate to let
me know directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have sent my reponse on your emailaddres v-mingqc@.online.microsoft.com
"removed online" for some weeks ago. Looking forward to your answer.
regards Henrik
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> I am currently standing by for an update from you and would like to know
> how things are going there. Should you have any questions or concerns on
> the recent questions/ information I've posted, please don't hesitate to let
> me know directly. It's my pleasure to be of assistance
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Henrik,
I am sorry that I have never received email from you :-(
May I ask your favor to resend the email?
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
reportmanager from a IIS application outside the lan as a true
webapplication, the reportmanager produce wrong paths for controls. E.x.
http://images/48folderopen.jpg There should have been a domain in front of
/images. I haven't been able to find any parameters in config's to meet this
problem.
Regards
Henrik Juel
GBS A/S
DenmarkHi Henrik,
Thanks for your post.
From your descriptions, I understood that you could not access your Report
Manager via Internet while it's OK for intrannet. Have I understood you?
Correct me if i was wrong.
Based on my scope, it seems you should modify your <ReportServerUrl> Tag
for the remote access. Go look at the Report Manager configuration
file,RSWebApplication.config. There is a UI section
<UI>
<ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
>
</UI>
Change it to
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
or you could find another way in charpter "Deploying a Report Server for
Internet Access" under Topic "Enterprise Deployment Model" in Reporting
Services Books Online.
Last but not the least, make sure you follow the security practices before
you opening the Internet Access:)
Hope this helps and if you have any questions or concerns, don't hesitate
to let me know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
Thanks for your instant answer. And yes you do understand me.
I haved tried the <ReportServerVirtualDirectory> tag in the
RSWebApplication.config file but it didn't made any difference to this
problem. I have read the chapter in the online book as I have read about
this topic in my Wrox book. I was not able to find this issue.
When starting the reportmanager from http://rs.gbs.dk the reportmanager
application do have connection to the reportserver, as it is able to show
folders, but fail to work with fully urls. E.x. the image problem stated
earlier.
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> Thanks for your post.
> From your descriptions, I understood that you could not access your Report
> Manager via Internet while it's OK for intrannet. Have I understood you?
> Correct me if i was wrong.
> Based on my scope, it seems you should modify your <ReportServerUrl> Tag
> for the remote access. Go look at the Report Manager configuration
> file,RSWebApplication.config. There is a UI section
> <UI>
> <ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
> >
> </UI>
> Change it to
> <UI>
> <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
> </UI>
> or you could find another way in charpter "Deploying a Report Server for
> Internet Access" under Topic "Enterprise Deployment Model" in Reporting
> Services Books Online.
> Last but not the least, make sure you follow the security practices before
> you opening the Internet Access:)
> Hope this helps and if you have any questions or concerns, don't hesitate
> to let me know. We are always here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>|||Hi Henrik,
If the Report Manager and Report Server are on the same machine then remove
the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
in the config file - and replace with <ReportServerVirtualDirectory>
Let me know whether this works
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
Both applications are on the same machine.
And I have only the <ReportServerVirtualDirectory> tag in the
rswebapplication.config.
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
I have created a virtual directory in the reportmanager root, which point to
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
where the server originally is installed.
So I belive It doesn't work.
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> If the Report Manager and Report Server are on the same machine then remove
> the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
> in the config file - and replace with <ReportServerVirtualDirectory>
> Let me know whether this works
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
>
>
>
>|||Hi Henrik,
First of all, I need to confirm that how do get the following link. Is it
in report manager when he right click a image->Properties to see the link
of the image? http://images/48folderopen.jpg
Secondly, please make sure that 'images' are in the IIS manager the image
folder:
1). Expand IIS server->Web sites->Default Website->Reports->Images
2). Right click Images->Properties->Directory and check if "The designated
directory" is used and "reports\images" is listed.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hello Michael
1. Yes I have the http://images/48folderopen.jpg from right clicking a image
in reportmanager.
2. The IIS settings are as you describe
You are welcome to contact me on +45 20282851 or on email : hjh@.gbs.dk for a
login to http://rs.gbs.dk
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> First of all, I need to confirm that how do get the following link. Is it
> in report manager when he right click a image->Properties to see the link
> of the image? http://images/48folderopen.jpg
> Secondly, please make sure that 'images' are in the IIS manager the image
> folder:
> 1). Expand IIS server->Web sites->Default Website->Reports->Images
> 2). Right click Images->Properties->Directory and check if "The designated
> directory" is used and "reports\images" is listed.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Henrik,
Looking at the nature of this issue, I am afraid we need more time
researching on this issue and this issue was critical to your business, I
would like to suggest you open an incidnet call with Microsoft Support
Professional through Microsoft Product Support Services. You can contact
Microsoft Product Support directly to discuss additional support options
you may have available, by contacting us at 1-(800)936-5800 or by choosing
one of the options listed at
http://support.microsoft.com/directory/overview.asp
If you'd still like to continue working via the newsgroup, I want to set
your expectations that the issue might take a long time to narrow down.
During the course of troubleshooting, we may redirect you to PSS if
required.
For now, I doubt it might be a IIS issue instead of Reporting Services one
and please let me know the answers for the following questions
1. If you are browsing the Report Manager *Locally* via domain name
(http://rs.gbs.dk), will it shows as expected?
If you are browsing via domain name within the intrannet, will it shows as
expected?
2. Open the Web site property,
Click Advanced Button in Web site identification of Web Site Tab
Select Default in Multiple identities for the Web site, Click Edit...
Let me know whether there is anything in the Host Header value
3. Is it possible for you to post IIS logs here? You could also send it to
me if you think it was critical for your business. My email address was
v-mingqc@.online.microsoft.com (please remove "online", it's only for SPAM,
thanks:-)
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi Henrik,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions/ information I've posted, please don't hesitate to let
me know directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have sent my reponse on your emailaddres v-mingqc@.online.microsoft.com
"removed online" for some weeks ago. Looking forward to your answer.
regards Henrik
""Michael Cheng [MSFT]"" wrote:
> Hi Henrik,
> I am currently standing by for an update from you and would like to know
> how things are going there. Should you have any questions or concerns on
> the recent questions/ information I've posted, please don't hesitate to let
> me know directly. It's my pleasure to be of assistance
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Henrik,
I am sorry that I have never received email from you :-(
May I ask your favor to resend the email?
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
ReportManager and SSL
I have a Reporting Services installation where I first implemented Forms
Authentication. I am now implementing SSL and have run into a problem. I
can access the report server through https://<servername>/reportserver,
howerver I cannot access the report manager using
https://<servername>/reports. I keep getting "The underlying connection was
closed: Could not establish trust relationship with remote server." I have
verified that the <URLRoot> key in the RSReportServer.config file and the
<ReportServerURL> key in the RSWebApplication.config file are in the format
https://<servername>/reportserver. My certificate has also been issued to
<servername>. Does anyone have any additional suggestions on fixing my
report manager problem?
Thank you in advance.Our experience has been that you can't change from non-SSL to SSL in
the same Reporting Services installation and have things work. The
procedure we have come up with is:
On the report server
1) uninstall Reporting Services using the uninstall from the RS
installation itself, not Add/Remove Programs.
2) delete the file with name starting with 1aedd7b5699f3d... at
<root>:\Documents and Settings\<machinename>\ASPNET\Application
Data\Microsoft\Crypto\RSA\<Some SID>
3) In Administrative Tools | Component Services | Component Services |
Computers | My Computer | COM+ Applications | , right-click on each of
IIS-{Default Web Site//Root/ReportServer}
IIS-{Default Web Site//Root/Reports}
and select Properties. Click the Advanced tab and uncheck "Disable
deletion". Delete each item.
4) Delete the Reporting Services databases (and the AdventureWorks
database if you installed it) from SQL Server.
5) Reboot.
6) Make sure your web server certificate is valid and was issued for
EXACTLY the correct machine name, case sensitive. If you are using a
cert from your own Enterprise CA and your CA does not chain up to a
root CA (doesn't have its own valid certificate from a real root CA),
use SelfSSL available at
http://www.microsoft.com/windowsserver2003/iis/downloads/default.mspx
to generate a cert that will work. You should probably use a Fully
Qualified Domain Name rather than a NetBIOS name for the certificate.
7) If the cert is good, reinstall Reporting Services and make sure that
you have checked the SSL box during the installation procedure. If the
installation throws _any_ error during the options-picking phase, exit
the installation, fix the problem, reboot, and start the installation
over again.
If anybody knows a better way to switch from non-SSL to SSL on a report
server please let me know. Some of this procedure may be superstition
but it works. Takes about 15 minutes once you've done it 20 or 30
times.
hth, and genuinely
Highly Obscure
Jim W wrote:
> I have a Reporting Services installation where I first implemented
> Forms Authentication. I am now implementing SSL and have run into a
> problem. I can access the report server through
> https://<servername>/reportserver, howerver I cannot access the
> report manager using https://<servername>/reports. I keep getting
> "The underlying connection was closed: Could not establish trust
> relationship with remote server." I have verified that the <URLRoot>
> key in the RSReportServer.config file and the <ReportServerURL> key
> in the RSWebApplication.config file are in the format
> https://<servername>/reportserver. My certificate has also been
> issued to <servername>. Does anyone have any additional suggestions
> on fixing my report manager problem?
> Thank you in advance.|||this may also be helpful:
http://sqljunkies.com/WebLog/roman/archive/category/370.aspx
Authentication. I am now implementing SSL and have run into a problem. I
can access the report server through https://<servername>/reportserver,
howerver I cannot access the report manager using
https://<servername>/reports. I keep getting "The underlying connection was
closed: Could not establish trust relationship with remote server." I have
verified that the <URLRoot> key in the RSReportServer.config file and the
<ReportServerURL> key in the RSWebApplication.config file are in the format
https://<servername>/reportserver. My certificate has also been issued to
<servername>. Does anyone have any additional suggestions on fixing my
report manager problem?
Thank you in advance.Our experience has been that you can't change from non-SSL to SSL in
the same Reporting Services installation and have things work. The
procedure we have come up with is:
On the report server
1) uninstall Reporting Services using the uninstall from the RS
installation itself, not Add/Remove Programs.
2) delete the file with name starting with 1aedd7b5699f3d... at
<root>:\Documents and Settings\<machinename>\ASPNET\Application
Data\Microsoft\Crypto\RSA\<Some SID>
3) In Administrative Tools | Component Services | Component Services |
Computers | My Computer | COM+ Applications | , right-click on each of
IIS-{Default Web Site//Root/ReportServer}
IIS-{Default Web Site//Root/Reports}
and select Properties. Click the Advanced tab and uncheck "Disable
deletion". Delete each item.
4) Delete the Reporting Services databases (and the AdventureWorks
database if you installed it) from SQL Server.
5) Reboot.
6) Make sure your web server certificate is valid and was issued for
EXACTLY the correct machine name, case sensitive. If you are using a
cert from your own Enterprise CA and your CA does not chain up to a
root CA (doesn't have its own valid certificate from a real root CA),
use SelfSSL available at
http://www.microsoft.com/windowsserver2003/iis/downloads/default.mspx
to generate a cert that will work. You should probably use a Fully
Qualified Domain Name rather than a NetBIOS name for the certificate.
7) If the cert is good, reinstall Reporting Services and make sure that
you have checked the SSL box during the installation procedure. If the
installation throws _any_ error during the options-picking phase, exit
the installation, fix the problem, reboot, and start the installation
over again.
If anybody knows a better way to switch from non-SSL to SSL on a report
server please let me know. Some of this procedure may be superstition
but it works. Takes about 15 minutes once you've done it 20 or 30
times.
hth, and genuinely
Highly Obscure
Jim W wrote:
> I have a Reporting Services installation where I first implemented
> Forms Authentication. I am now implementing SSL and have run into a
> problem. I can access the report server through
> https://<servername>/reportserver, howerver I cannot access the
> report manager using https://<servername>/reports. I keep getting
> "The underlying connection was closed: Could not establish trust
> relationship with remote server." I have verified that the <URLRoot>
> key in the RSReportServer.config file and the <ReportServerURL> key
> in the RSWebApplication.config file are in the format
> https://<servername>/reportserver. My certificate has also been
> issued to <servername>. Does anyone have any additional suggestions
> on fixing my report manager problem?
> Thank you in advance.|||this may also be helpful:
http://sqljunkies.com/WebLog/roman/archive/category/370.aspx
ReportManager and domain name change
Hi,
The fully qualified domain name of the reporting services server has changed
and that caused the Report Manager to stop working. Iâ'm using SQL 2000
Reporting Services on Windows Server 2003 .
I tracked the issue down to /Reports/Pages/Report.aspx page where that page
calls the actual report in a IFRAME and the IFRAME is calling the report with
the old domain name.
I found a configuration setting <UrlRoot> in the C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config config
file that used the old domain name. However, even changing that property to a
new domain name had no effect (tired touching web.configs, bouncing the
website).
Any suggestions greatly appreciated.
Thanks,
AlexFrom an issue I had with something similar on my CRM system here are some
notes passed on to me that I think might help you. I was changing mine from
a fullqualified domain name to a domain.local name but these would still
apply for you as well:
These instructions assume you are using SQL 2000 SP4.
First, on the server where SRS is installed, open the two files
rswebapplication.config at C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and rsreportserver.config at
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
with notepad and search for https://fqdn.yourdomain.com. Once you find this
replace it with https://YourNetBiosServerName.domain.local and save and
close the files.
On the same server, open the registry and modify the following registry
values at HKLM | SOFTWARE | Microsoft | Microsoft SQL Server | 80 |
Reporting Services to replace https://fqdn.yourdomain.com/ReportServer with
https://YourNetBiosServerName.domain.local/ReportServer.
RSVirtualDir - should be
https://YourNetBiosServerName.domain.local/ReportServer
WAVirtualDir - should be https://YourNetBiosServerName.domain.local/Reports
Gary
"alex" <alex@.discussions.microsoft.com> wrote in message
news:2E0195F3-5F67-4196-A119-9CDFC08656DA@.microsoft.com...
> Hi,
> The fully qualified domain name of the reporting services server has
> changed
> and that caused the Report Manager to stop working. I'm using SQL 2000
> Reporting Services on Windows Server 2003 .
> I tracked the issue down to /Reports/Pages/Report.aspx page where that
> page
> calls the actual report in a IFRAME and the IFRAME is calling the report
> with
> the old domain name.
> I found a configuration setting <UrlRoot> in the C:\Program
> Files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
> config
> file that used the old domain name. However, even changing that property
> to a
> new domain name had no effect (tired touching web.configs, bouncing the
> website).
> Any suggestions greatly appreciated.
> Thanks,
> Alex
>
The fully qualified domain name of the reporting services server has changed
and that caused the Report Manager to stop working. Iâ'm using SQL 2000
Reporting Services on Windows Server 2003 .
I tracked the issue down to /Reports/Pages/Report.aspx page where that page
calls the actual report in a IFRAME and the IFRAME is calling the report with
the old domain name.
I found a configuration setting <UrlRoot> in the C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config config
file that used the old domain name. However, even changing that property to a
new domain name had no effect (tired touching web.configs, bouncing the
website).
Any suggestions greatly appreciated.
Thanks,
AlexFrom an issue I had with something similar on my CRM system here are some
notes passed on to me that I think might help you. I was changing mine from
a fullqualified domain name to a domain.local name but these would still
apply for you as well:
These instructions assume you are using SQL 2000 SP4.
First, on the server where SRS is installed, open the two files
rswebapplication.config at C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and rsreportserver.config at
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
with notepad and search for https://fqdn.yourdomain.com. Once you find this
replace it with https://YourNetBiosServerName.domain.local and save and
close the files.
On the same server, open the registry and modify the following registry
values at HKLM | SOFTWARE | Microsoft | Microsoft SQL Server | 80 |
Reporting Services to replace https://fqdn.yourdomain.com/ReportServer with
https://YourNetBiosServerName.domain.local/ReportServer.
RSVirtualDir - should be
https://YourNetBiosServerName.domain.local/ReportServer
WAVirtualDir - should be https://YourNetBiosServerName.domain.local/Reports
Gary
"alex" <alex@.discussions.microsoft.com> wrote in message
news:2E0195F3-5F67-4196-A119-9CDFC08656DA@.microsoft.com...
> Hi,
> The fully qualified domain name of the reporting services server has
> changed
> and that caused the Report Manager to stop working. I'm using SQL 2000
> Reporting Services on Windows Server 2003 .
> I tracked the issue down to /Reports/Pages/Report.aspx page where that
> page
> calls the actual report in a IFRAME and the IFRAME is calling the report
> with
> the old domain name.
> I found a configuration setting <UrlRoot> in the C:\Program
> Files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
> config
> file that used the old domain name. However, even changing that property
> to a
> new domain name had no effect (tired touching web.configs, bouncing the
> website).
> Any suggestions greatly appreciated.
> Thanks,
> Alex
>
Reportmanager (SSL): Unable to Connect to the remote server
Who can help me with SSL and Reporting Services (Reportmanager)?
Reportmanager (SSL): >> Unable to Connect to the remote server
System information:
Server 2003 Std Edition, SQL Server Enterprise, both 64-bit, latest service
packs
Microsoft SQL Server Reporting Services Version 9.00.3042.00
ASP.NET version 2.0.50727
Both Reportmanager (/Reports) and Reportserver (/Reportserver) are working
correctly on http (without SSL) using 'Basic authentication'.
I successfully installed a certificate 'extranet.website.nl' in IIS on the
'Default Web Site'.
With the Reporting Services Configuration Manager, I turned on SSL for
Reporting Services:
- Require Secure Socket Layer (SSL) connections: Yes
- Require for: 3 - All SOAP APIs (also tried other selections)
- Certificate Name: extranet.website.nl
After restarting everything the following happens:
- Reportserver (https://extranet.website.nl/reportserver) is working
correctly.
- Reportmanager (https://extranet.website.nl/reports) gives the following
error:
>> Unable to Connect to the remote server
Extra information:
The certificate is installed on the 'Default Web Site' and displayed on both
'Reports' and 'ReportServer'. Both using the DefaultAppPool.
-- rsreportserver.config --
<Add Key="SecureConnectionLevel" Value="3"/>
...
<UrlRoot>https://extranet.website.nl/reportserver</UrlRoot>
...
<WebServiceAccount>NT Authority\NetworkService</WebS...
...
-- RSWebApplication.config --
<ReportServerUrl>https://extranet.website.nl/ReportServer</Report...
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
I have changed to all possibilities 'Require secure channel (SSL)' and
'Require 128-bit encryption' in IIS on the 'Default Web Site', 'Reports' and
'ReportServer'. Afterwards restarting Reporting Services and IIS.
Who can help me with the solution for the Reportmanager (/Reports)?
>> Unable to Connect to the remote server
Thanks a lot for the working solution...Yes, it's working...
The working solution seemed to be more simple then expected:
(after a lot of trying)
In .../etc/hosts
add:
<local-ip-adres> <servername>
for example:
192.168.1.100 server001|||Directory: C:\WINDOWS\system32\drivers\etc
File: hosts
"Lonny" wrote:
> Can you explain your solution in a bit more detail?
> I am having the same issue with https.
> Where exactly is .../ect/hosts ?
> EggHeadCafe - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
>
Reportmanager (SSL): >> Unable to Connect to the remote server
System information:
Server 2003 Std Edition, SQL Server Enterprise, both 64-bit, latest service
packs
Microsoft SQL Server Reporting Services Version 9.00.3042.00
ASP.NET version 2.0.50727
Both Reportmanager (/Reports) and Reportserver (/Reportserver) are working
correctly on http (without SSL) using 'Basic authentication'.
I successfully installed a certificate 'extranet.website.nl' in IIS on the
'Default Web Site'.
With the Reporting Services Configuration Manager, I turned on SSL for
Reporting Services:
- Require Secure Socket Layer (SSL) connections: Yes
- Require for: 3 - All SOAP APIs (also tried other selections)
- Certificate Name: extranet.website.nl
After restarting everything the following happens:
- Reportserver (https://extranet.website.nl/reportserver) is working
correctly.
- Reportmanager (https://extranet.website.nl/reports) gives the following
error:
>> Unable to Connect to the remote server
Extra information:
The certificate is installed on the 'Default Web Site' and displayed on both
'Reports' and 'ReportServer'. Both using the DefaultAppPool.
-- rsreportserver.config --
<Add Key="SecureConnectionLevel" Value="3"/>
...
<UrlRoot>https://extranet.website.nl/reportserver</UrlRoot>
...
<WebServiceAccount>NT Authority\NetworkService</WebS...
...
-- RSWebApplication.config --
<ReportServerUrl>https://extranet.website.nl/ReportServer</Report...
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
I have changed to all possibilities 'Require secure channel (SSL)' and
'Require 128-bit encryption' in IIS on the 'Default Web Site', 'Reports' and
'ReportServer'. Afterwards restarting Reporting Services and IIS.
Who can help me with the solution for the Reportmanager (/Reports)?
>> Unable to Connect to the remote server
Thanks a lot for the working solution...Yes, it's working...
The working solution seemed to be more simple then expected:
(after a lot of trying)
In .../etc/hosts
add:
<local-ip-adres> <servername>
for example:
192.168.1.100 server001|||Directory: C:\WINDOWS\system32\drivers\etc
File: hosts
"Lonny" wrote:
> Can you explain your solution in a bit more detail?
> I am having the same issue with https.
> Where exactly is .../ect/hosts ?
> EggHeadCafe - .NET Developer Portal of Choice
> http://www.eggheadcafe.com
>
ReportManager - new "Object reference not set to an instance of an object."-error
Hi,
Im having a bit of a problem with reporting services.
First of all, Im running three virtual servers. "MyApp", "ReportServer" and "ReportManager".
In order to have a single sign-on experience, I have authentication configured to Forms in all three web.config-files with the same cookie-name and so forth. I also added a MachineKey to all three web.config files to share the authentication for the virtual directories. (and yes, I use the same machineKey for all three apps)
To login, a user can enter "/MyApp", "/ReportServer", or "/ReportManager" and then I get redirected to "/MyApp/login.aspx" (as that is the setting in the web.config-files).
-
<authentication mode="Forms">
<forms name=".MyApp.Net" loginUrl="https://MyApp/Login.aspx" protection="All" timeout="60" />
</authentication>
-
It works!
The authentication works fine, and I get redirected to the specific directory. MyApp, well, here is the original application, no problems here. The "ReportServer" login works fine too, I get redirected to that directory and the reports I have show-up in a directory-listing type of way...
However...
When I try to go in to the ReportManager I get a nasty error:
-
SQL Server Reporting Services
Error
Object reference not set to an instance of an object.
Home
-
Checking the log-files to see if an error is generated I get the following:
ReportServerWebAPP.log
-
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.2047.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServerWebApp__07_25_2006_15_21_11.log</Path>
<SystemName>MYLOCALDOMAIN</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
<OSVersion>5.2.3790.65536</OSVersion>
</Header>
w3wp!ui!c!2006-07-25-16:37:52:: e ERROR: Object reference not set to an instance of an object.
w3wp!ui!c!2006-07-25-16:37:52:: e ERROR: HTTP status code --> 500
-Details--
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.UI.BasePermissions.ReadPermissions(String[] permissions)
at Microsoft.ReportingServices.UI.Permissions.GetPermissions()
at Microsoft.ReportingServices.UI.Permissions.CurrentUser(String itemPath)
at Microsoft.ReportingServices.UI.FolderPage.Page_Init(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!c!2006-07-25-16:37:52:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
-
ReportServer.log
-
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.2047.00</Product>
<Locale>en-US</Locale>
<TimeZone>W. Europe Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServer__07_25_2006_15_17_42.log</Path>
<SystemName>MYLOCALDOMAIN</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
<OSVersion>5.2.3790.65536</OSVersion>
</Header>
w3wp!webserver!1!2006-07-25-15:17:42:: i INFO: Reporting Web Server started
....
....
w3wp!library!1!07/25/2006-16:37:52:: i INFO: Call to GetPermissions:/
-
Now what?
It seems that there is something wrong with the permissions and that this causes the report manager to behave as expected... but I just cant figure out what..
Other things worth mentioning...
Im using custom authentication, overloading LogonUser etc, pretty much according to this article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
However, that part seems to be working fine, since I can access the "ReportServer"!
Ive also tried different permutations of authentication mode="forms", "windows" and impersonate with no luck.
My RSWenApplication.config looks like this:
-
<UI>
<CustomAuthenticationUI>
<loginUrl>https://MyApp/Login.aspx</loginUrl>
<UseSSL>True</UseSSL>
<PassThroughCookies>
<PassThroughCookie>.MyApp.Net</PassThroughCookie>
</PassThroughCookies>
</CustomAuthenticationUI>
<ReportServerUrl>https://ReportServer</ReportServerUrl>
</UI>
-
One last thing that might be of interest... I use SSL on the webserver, but there is no root-certificate installed since this is only a development machine... this was a problem at first, but then I added this to the Global.asax-file in the "ReportManager"-folder.
-
void Application_AuthenticateRequest(object s, EventArgs e)
{
ServicePointManager.ServerCertificateValidationCallback = delegate(Object obj, X509Certificate certificate, X509Chain chain, SslPolicyErrors errors) { return true; };
}
-
And now I get the "Object reference not set to an instance of an object."-error instead!
Please help me... getting increasingly frustrated...
Hey,
did you look at the other threads on this forum about the problem?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=470075&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=444736&SiteID=1
Maybe they offer a solution!
Grts
|||Hi again,
Yeah, Ive taken a look at both of them and all the pages referenced in those articles... and so forth... still no luck...
Would appriciate any help I can get... been at it for almost a week now and Im starting to loose all hope :-)
Is there for example any place to start looking? Or would I have to tear everything down and start over?
Thanks!
|||A quick look at your config file, but this doesn't look right: https://ReportServer. Is that just a typo?
Subscribe to:
Posts (Atom)