Issue with ReportViewer dll and accessing reports

Question,
I have an external web server that uses the ReportViewer dll to point to a
Report Server located internally - Not visible to the outside world just to
the intranet. I get a page not found error when trying to view a report via
the reportviewer dll. I have a feeling this is being caused because the
serverurl property is set to point to the server inside the firewall. I can
run the web app just fine from the intranet but whenever I try externally I
get that page not found problem. I was under the impression that the Report
Server Dll was an ASP.Net server control and would run on the server but it
seems as if it is somehow tied to the client. The reason I think this is it
seems as if the client is looking for localhost which of course doesnt exist
on the clients end. Any help and or tips would be appreciated.
Thanks,
Scott EguiresHI, Scott:
I have the same issue. I have a external web cluster to host my website. And
I use the reportview web control to embed the report to my website. My report
server is internally. It works ok from inside, but from outside, I get the
result "The page can not be display". I think it can not find the server.
Did you solve your problem finally? And how did you solve it?
Thanks a lot.
-summer
"Scott Eguires" wrote:
> Question,
> I have an external web server that uses the ReportViewer dll to point to a
> Report Server located internally - Not visible to the outside world just to
> the intranet. I get a page not found error when trying to view a report via
> the reportviewer dll. I have a feeling this is being caused because the
> serverurl property is set to point to the server inside the firewall. I can
> run the web app just fine from the intranet but whenever I try externally I
> get that page not found problem. I was under the impression that the Report
> Server Dll was an ASP.Net server control and would run on the server but it
> seems as if it is somehow tied to the client. The reason I think this is it
> seems as if the client is looking for localhost which of course doesnt exist
> on the clients end. Any help and or tips would be appreciated.
> Thanks,
> Scott Eguires|||Yes I did. I wrote my own report viewer control to view the reports
externally without having to pay for an extra SQL Server license. It was a
real pain but it works beautifully and has a fairly nice interface. I still
need to add security to it though.
Scott Eguires
"summer" wrote:
> HI, Scott:
> I have the same issue. I have a external web cluster to host my website. And
> I use the reportview web control to embed the report to my website. My report
> server is internally. It works ok from inside, but from outside, I get the
> result "The page can not be display". I think it can not find the server.
> Did you solve your problem finally? And how did you solve it?
> Thanks a lot.
> -summer
> "Scott Eguires" wrote:
> > Question,
> >
> > I have an external web server that uses the ReportViewer dll to point to a
> > Report Server located internally - Not visible to the outside world just to
> > the intranet. I get a page not found error when trying to view a report via
> > the reportviewer dll. I have a feeling this is being caused because the
> > serverurl property is set to point to the server inside the firewall. I can
> > run the web app just fine from the intranet but whenever I try externally I
> > get that page not found problem. I was under the impression that the Report
> > Server Dll was an ASP.Net server control and would run on the server but it
> > seems as if it is somehow tied to the client. The reason I think this is it
> > seems as if the client is looking for localhost which of course doesnt exist
> > on the clients end. Any help and or tips would be appreciated.
> >
> > Thanks,
> >
> > Scott Eguires|||Do I need an extra SQL license if I only install the Reoprt server on the web
server, and keep the Report database on another machine with already has a
SQL license?
Do you mind to tell me how you build your own report viewer? Did you use SOAP?
Thanks a lot.
"Scott Eguires" wrote:
> Yes I did. I wrote my own report viewer control to view the reports
> externally without having to pay for an extra SQL Server license. It was a
> real pain but it works beautifully and has a fairly nice interface. I still
> need to add security to it though.
> Scott Eguires
> "summer" wrote:
> > HI, Scott:
> >
> > I have the same issue. I have a external web cluster to host my website. And
> > I use the reportview web control to embed the report to my website. My report
> > server is internally. It works ok from inside, but from outside, I get the
> > result "The page can not be display". I think it can not find the server.
> >
> > Did you solve your problem finally? And how did you solve it?
> >
> > Thanks a lot.
> >
> > -summer
> > "Scott Eguires" wrote:
> >
> > > Question,
> > >
> > > I have an external web server that uses the ReportViewer dll to point to a
> > > Report Server located internally - Not visible to the outside world just to
> > > the intranet. I get a page not found error when trying to view a report via
> > > the reportviewer dll. I have a feeling this is being caused because the
> > > serverurl property is set to point to the server inside the firewall. I can
> > > run the web app just fine from the intranet but whenever I try externally I
> > > get that page not found problem. I was under the impression that the Report
> > > Server Dll was an ASP.Net server control and would run on the server but it
> > > seems as if it is somehow tied to the client. The reason I think this is it
> > > seems as if the client is looking for localhost which of course doesnt exist
> > > on the clients end. Any help and or tips would be appreciated.
> > >
> > > Thanks,
> > >
> > > Scott Eguires|||Yes you do need another SQL Server license in this scenario. That is why I
wrote my own Report Manager/Viewer. I can give you more information on
Monday or Tuesday of next week as I am currently out of town on a business
trip. You can email me at scott@.eguires.net for further discussions if you
wish and I can show you what I have done thus far and you can give me your
opinion on it.
Thanks,
Scott Eguires
"summer" wrote:
> Do I need an extra SQL license if I only install the Reoprt server on the web
> server, and keep the Report database on another machine with already has a
> SQL license?
> Do you mind to tell me how you build your own report viewer? Did you use SOAP?
> Thanks a lot.
> "Scott Eguires" wrote:
> > Yes I did. I wrote my own report viewer control to view the reports
> > externally without having to pay for an extra SQL Server license. It was a
> > real pain but it works beautifully and has a fairly nice interface. I still
> > need to add security to it though.
> >
> > Scott Eguires
> >
> > "summer" wrote:
> >
> > > HI, Scott:
> > >
> > > I have the same issue. I have a external web cluster to host my website. And
> > > I use the reportview web control to embed the report to my website. My report
> > > server is internally. It works ok from inside, but from outside, I get the
> > > result "The page can not be display". I think it can not find the server.
> > >
> > > Did you solve your problem finally? And how did you solve it?
> > >
> > > Thanks a lot.
> > >
> > > -summer
> > > "Scott Eguires" wrote:
> > >
> > > > Question,
> > > >
> > > > I have an external web server that uses the ReportViewer dll to point to a
> > > > Report Server located internally - Not visible to the outside world just to
> > > > the intranet. I get a page not found error when trying to view a report via
> > > > the reportviewer dll. I have a feeling this is being caused because the
> > > > serverurl property is set to point to the server inside the firewall. I can
> > > > run the web app just fine from the intranet but whenever I try externally I
> > > > get that page not found problem. I was under the impression that the Report
> > > > Server Dll was an ASP.Net server control and would run on the server but it
> > > > seems as if it is somehow tied to the client. The reason I think this is it
> > > > seems as if the client is looking for localhost which of course doesnt exist
> > > > on the clients end. Any help and or tips would be appreciated.
> > > >
> > > > Thanks,
> > > >
> > > > Scott Eguires

Issue doing Integrated services programming using Microsoft.SqlServer.ManagedDTS.dll

Hi,

I am writing an installer code in C# to deploy the SSIS package.

I want to use Microsoft.SqlServer.ManagedDTS.dll for it.

It is mentioned in few articles available online that Microsoft.SqlServer.ManagedDTS.dll ships with SQL Server 2005.

I searched on our database server but could not get it.

Anyone having idea on this please help.

HV

Don't try and install SSIS by hand, it is not a good idea It is not supposed to be a redistributable component. There are a lot more assemblies that just that one for SSIS.

Since SSIS requires a full SQL Server license, why not use the regular SQL setup to do this for you. You can choose which servers you want.

If you have installed SSIS on your server then it will certainly be in the GAC, but it may not be on the file system outside of this, unless you installed the tools, in which case it is - C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

|||Another question to ask: Is SSIS installed on this SQL Server box? A lot of SQL 2005 servers will be set up by their DBAs to not have any unnecessary components installed, and SSIS sometimes falls into this category.|||

Hi,

Thank you Darren.

SSIS is installed on the machine.

I checked the following folder :- C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

but dll is not available.

Which tool installation delivers Microsoft.SqlServer.ManagedDts.dll?

Please let me know.

HV

|||

Hi,

Thank you Mathew.

SSIS is installed on the machine.

I checked the following folder :- C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

but it's not available.

HV

|||

Hi,

I picked the Microsoft.SQLServer.ManagedDTS.dll from following folder:

C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\9.0.242.0__89845dcd8080cc91>

Similarly picked Microsoft.SqlServer.DTSRuntimeWrap.dll also.

I added it as reference in my .NET application.

When I execute the program I get below error:

Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154.

Any Clue?

How to get the RunningPackages information back to a client PC?

HV

|||

If you want running packages information, why not just use the MS tools?

Do you have SSIS tools installed on the local machine that hosts the program? The error indicates that Microsoft.SqlServer.DTSRuntimeWrap is not installed on the local PC?

|||

No SSIS is not installed on the machine which hosts program.

But that is my requirement , I want to deploy SSIS package remotely.

I have installed Microsoft.SQLServer.DTSRuntimeWrap.dll in GAC.

Let me know if there is a way out to use it on a machine where SSIS is not installed.

HV

|||

SSIS is not installed you say, and you get an error that says in cannot find a COM component. Do you think there may be a connection?

I refer you to my original post, apart from saying that a manual install was a silly idea, I also pointed out "There are a lot more assemblies that just that one for SSIS."

As a start point that DLL is just a wrapper to the COM library that does the work, the name hints at that, and the error proves that it is trying to use a COM DLL that is not there, a COM DLL with a ProgID of {E44847F1-FD8C-4251-B5DA-B04BB22E236E} perhaps. As I said before there are lots of DLLs involved in SSIS not just one, so use a proper install.

What you are asking for a not a supported scenario, you may be violating your license agreements if not careful, and at any rate will be a very complicated task to try and reverse engineer the requirements, and very slow if you cannot track a missing COM DLL down yourself.

If you think this is wrong, post feedback to MS (http://connect.microsoft.com) telling them why you think you should have some redistribuatable support, but in the mean-time you will need to run one of the MS installs to get this to work.

Why do you not want to use a MS install?