Showing posts with label experience. Show all posts
Showing posts with label experience. Show all posts

Tuesday, March 20, 2012

Painful installation of RS 2005 on Win2K

Ok I'm am going through a rather painful experience of installing Reporting Services on:

Windows 2000 SP4

MDAC 2.8

.Net Framework 2.0

IIS 5.0

SQL Server 2005 Developer

I have installed RS 2005 on Windows 2003, and seen it installed on XP no problems. However this is a nightmare.

RS goes ahead and installs - note that there is no Network/Local service option on the service accounts just Local system or the domain account option. I have tried using the Local system and tried using the NT AUTHORITY/SYSTEM.

After the installation I go to the Reporting Services Configuration Tool, where I have crosses on:

- Server Status

- Report Server Virtual Directory

- Report Manager Virtual Directory

- Web Service Identity

- Database Setup

I- nitialization

So I go to report server/manager and click on "New.." on each to create the virtual directories and check "apply default settings" and click "Apply", all goes well

Web Service Identity I cannot change so I go to:

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config

and change the web service account to:

<WebServiceAccount><<MACHINE NAME>>\ASPNET</WebServiceAccount>

When I restart the reporting services service I no longer see a warning in the reporting services log file about the WebServiceAccount

I go back to the Reporting Services Config Tool, where I have crosses on the following:

Web Service Identity

Database Setup

Initialization

The Web Service Identity stays greyed out...

I go to Database Setup:

connect to the server

select the reportingserver database

leave it set as service credentials

Click "Apply"

and I get the most vague of all error messages:

"There was a failure applying your change

A virtual directory must first be created before performing this operation"

What virtual directory, where?

I look in the log files..nothing. I look in the event viewer...and...nothing.

I look on here...

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=628231&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1682492&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=493194&SiteID=1

Either unanswered or there is the one answer but it is not relevant in this case.

Can someone please provide some advice before I lose my sanity?

Thanks in advance

Ok since I got no responses, after trial and error I found that the following process worked....

1. run SQLSERVER2005 setup from the command line with setup SKUUPGRADE=1

2. Install RS

3. open the RS config tool, create the virtual directories for server/manager

4. run rsconfig -c -s <SQLSERVERNAME> -d <<RS DB Name>> -a Windows from the command line (for a service account) see http://msdn2.microsoft.com/en-us/library/ms162837.aspx for more.

5. Edit the rsreportserver.config file add the WebServiceAccount <WebServiceAccount><<MACHINE NAME>>\ASPNET</WebServiceAccount>

6. Add ASPNET to the group SQLServer2005ReportingServicesWebServiceUser$<<INSTANCE_NAME>>

7. Give ASPNET or the above group acess to the RS DB

8. Add administrators as Content Managers via either the browser localhost/reports or in SQL Server Management Studio

9. Reboot

I have no idea why the RS configuration tool does not perform in the same way as the command line rsconfig? But running it from the command line fixes the problem

Monday, March 12, 2012

Paging when PDF is rendered

I have report that generates a person's resume. The resume sections
(experience, education, skills ...) do not page correctly when exported to
PDF or TIFF. Instead of keeping sections together on the same page the
sections is moved to the next page even though there is sufficient space left
at the bottom of the current page.
I would really appreciate any help since this is due next week.Hi Adil,
Did you solve this issue?.
I'm also got stuck with the same problem.
Please help if you have solved this issue.
Thanks,
Ranjith
"Adil" wrote:
> I have report that generates a person's resume. The resume sections
> (experience, education, skills ...) do not page correctly when exported to
> PDF or TIFF. Instead of keeping sections together on the same page the
> sections is moved to the next page even though there is sufficient space left
> at the bottom of the current page.
> I would really appreciate any help since this is due next week.
>|||No solution yet. I was hoping someone from Microsoft could look at this...|||I have the same problem.
Data groups are being put on new pages instead of flowing. "KeepTogether"
property for all data regions is set to "False" but the groups are still
moved to new pages.
In design preview mode the data layout is perfect - until I print preview
or export to pdf - extra pages get added.
I installed SP2 and that solved another problem that I had - the first page
was blank in print preview mode but this problem still persists.
Anyway - sorry I can't help you on this one but I am hoping MS knows that
more than one person is having this problem.
Cheers
"Adil" <Adil@.discussions.microsoft.com> wrote in message
news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> No solution yet. I was hoping someone from Microsoft could look at this...|||Hi,
I got to know that, this behaviour is as per the design. When we have list,
they implicitly set Keep together property to true during the rendering time.
The workaround given by microsoft is to use "Tables" instead of "list" in
the reports.
I believe microsoft people will help us for sure to fix this issue,else we
have no other option to redesign the reports from the scratch using tables
instead of list.
Thanks,
Ranjith
"Tim Powers" wrote:
> I have the same problem.
> Data groups are being put on new pages instead of flowing. "KeepTogether"
> property for all data regions is set to "False" but the groups are still
> moved to new pages.
> In design preview mode the data layout is perfect - until I print preview
> or export to pdf - extra pages get added.
> I installed SP2 and that solved another problem that I had - the first page
> was blank in print preview mode but this problem still persists.
> Anyway - sorry I can't help you on this one but I am hoping MS knows that
> more than one person is having this problem.
> Cheers
>
>
> "Adil" <Adil@.discussions.microsoft.com> wrote in message
> news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> > No solution yet. I was hoping someone from Microsoft could look at this...
>
>|||Thanks - tables work!
I originally used the wizard and to create a group -- the wizard uses lists,
not tables.
Anyway this issue caused me 2 days of work - I couldn't find any
information to solve this problem.
Thanks for the tip!
"Ranjith Prakash" <RanjithPrakash@.discussions.microsoft.com> wrote in
message news:89D8F795-E366-4B74-BB96-BEDC4370809A@.microsoft.com...
> Hi,
> I got to know that, this behaviour is as per the design. When we have
list,
> they implicitly set Keep together property to true during the rendering
time.
> The workaround given by microsoft is to use "Tables" instead of "list" in
> the reports.
> I believe microsoft people will help us for sure to fix this issue,else we
> have no other option to redesign the reports from the scratch using tables
> instead of list.
> Thanks,
> Ranjith
> "Tim Powers" wrote:
> > I have the same problem.
> >
> > Data groups are being put on new pages instead of flowing.
"KeepTogether"
> > property for all data regions is set to "False" but the groups are still
> > moved to new pages.
> >
> > In design preview mode the data layout is perfect - until I print
preview
> > or export to pdf - extra pages get added.
> >
> > I installed SP2 and that solved another problem that I had - the first
page
> > was blank in print preview mode but this problem still persists.
> >
> > Anyway - sorry I can't help you on this one but I am hoping MS knows
that
> > more than one person is having this problem.
> >
> > Cheers
> >
> >
> >
> >
> > "Adil" <Adil@.discussions.microsoft.com> wrote in message
> > news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> > > No solution yet. I was hoping someone from Microsoft could look at
this...
> >
> >
> >