Showing posts with label production. Show all posts
Showing posts with label production. Show all posts

Friday, March 23, 2012

Report Viewer dlls on web server

I need to get the report viewer files onto my production web box. I know I can run the report view install to get the files registered in the GAL. Unfortunately running an install on a 'productionalized' box will be a big to do for the administrators in my company. Can this issue be resolved simply by copying out the files to the bin directory of the site in question? Are there any pro/cons to doing it this way (other than I'd have to do this for every site that needs reporting).

thanks,

MP

Keep the dlls local to your project by putting them in the bin folder. This should not have any negative effects. I have a report app accessing the dlls way. Cheers!

Friday, March 9, 2012

Report Server website - button presses ignored

I'm seeing a strange problem on my production Reportng Services (SQL 2000)
server.
Some of the website buttons, like OK & CANCEL when attempting to create a
new site-wide Schedule, don't function. No error reported when you press
them, they're just ignored, it's as if the installation failed to complete
properly.
My development server, also running SQL 2000 and Reporting Services, doesn't
have the issue.Have you got activeX disabled?
Are you running sp2?
SimonN wrote:
> I'm seeing a strange problem on my production Reportng Services (SQL 2000)
> server.
> Some of the website buttons, like OK & CANCEL when attempting to create a
> new site-wide Schedule, don't function. No error reported when you press
> them, they're just ignored, it's as if the installation failed to complete
> properly.
> My development server, also running SQL 2000 and Reporting Services, doesn't
> have the issue.|||HI. Tks for the reply.
No ActiveX is not disabled, and client PC is running SP2.
Browsing the two installations from the same client, so i can bring up two
IEs one pointing to an RS website that works and the other to the one that is
faulty.
"SmartbizAustralia" wrote:
> Have you got activeX disabled?
> Are you running sp2?
> SimonN wrote:
> > I'm seeing a strange problem on my production Reportng Services (SQL 2000)
> > server.
> >
> > Some of the website buttons, like OK & CANCEL when attempting to create a
> > new site-wide Schedule, don't function. No error reported when you press
> > them, they're just ignored, it's as if the installation failed to complete
> > properly.
> >
> > My development server, also running SQL 2000 and Reporting Services, doesn't
> > have the issue.
>|||Simon,
Look in the Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\RSWebApplication.config file for a <ReportServerURL>
and <ReportServerExternalURL> config values. Many times these reference the
machine name instead of the URL used to access the reporting services. I've
found if these these entries don't match the domain name in the URL used to
access report manager, many of the buttons simply don't do anything when
clicked.
- Chris
"SimonN" <SimonN@.discussions.microsoft.com> wrote in message
news:63A63397-D966-4A70-8D5A-24AD9054E50B@.microsoft.com...
> I'm seeing a strange problem on my production Reportng Services (SQL 2000)
> server.
> Some of the website buttons, like OK & CANCEL when attempting to create a
> new site-wide Schedule, don't function. No error reported when you press
> them, they're just ignored, it's as if the installation failed to complete
> properly.
> My development server, also running SQL 2000 and Reporting Services,
> doesn't
> have the issue.|||Chris,
Thanks for the reply.
I checked the value of ReportServerURL in the RSWebApplication.config, it's
set to the correct name of the server. I have a DNS alias that user will use
to run reports, but for all administration I'll stick to using the actual
server in the URL.
I don't have an entry for ReportServerExternalURL, but it sounds like this
is a 2005 feature when accessing the Report Server through a firewall. I'm
only running the 2000 version.
Unfortunately, I'm still seeing the same issue even when I browse with the
serve name identified by the ReportServerURL config element.
"Chris Walls" wrote:
> Simon,
> Look in the Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\RSWebApplication.config file for a <ReportServerURL>
> and <ReportServerExternalURL> config values. Many times these reference the
> machine name instead of the URL used to access the reporting services. I've
> found if these these entries don't match the domain name in the URL used to
> access report manager, many of the buttons simply don't do anything when
> clicked.
> - Chris
> "SimonN" <SimonN@.discussions.microsoft.com> wrote in message
> news:63A63397-D966-4A70-8D5A-24AD9054E50B@.microsoft.com...
> > I'm seeing a strange problem on my production Reportng Services (SQL 2000)
> > server.
> >
> > Some of the website buttons, like OK & CANCEL when attempting to create a
> > new site-wide Schedule, don't function. No error reported when you press
> > them, they're just ignored, it's as if the installation failed to complete
> > properly.
> >
> > My development server, also running SQL 2000 and Reporting Services,
> > doesn't
> > have the issue.
>
>

Monday, February 20, 2012

Report Recovery Help ASAP!

Report A has been deployed and works fine and ties out in production. The
design copy of this report in VS has been corrupted. All other backups of
this report have been corrupted. How do I get the rdl. for Report A fixed?In report manager click on the report, then properties tab. Click on Edit
link. Give it a directory on your local PC. Different than where you project
is. Then in your project add an exisiting item to the project. It will copy
it over to the directory with all your other rdl files.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"OriginalStealth" <OriginalStealth@.discussions.microsoft.com> wrote in
message news:DFA101E4-26E6-4D14-BD30-05ECE46A2DF1@.microsoft.com...
> Report A has been deployed and works fine and ties out in production. The
> design copy of this report in VS has been corrupted. All other backups of
> this report have been corrupted. How do I get the rdl. for Report A
> fixed?