Reporting Service's 2005 upgrade issue

We have completed the Reporting Service's 2005 upgrade (sept ctp) and have
been testing some of the reports. We are finding reports that work just find
on 2000 (our prod. box) are not working properly in 2005. Is anyone else
having any issues? I will try to explain one of the scenarios in which we
have encountered issues:
Ok. The report has two date dropdowns and three other string dropdowns. The
dates are defaulted but the others are not. One of the three other dropdowns
are greyed out until the other two are selected first. The problem is when we
select either of the first two dropdowns, it displays an error page stating
"Value cannot be null. Parameter name: value ". The 2000 version works
correctly.
Any help is appreciated!It sounds like you run into a known issue with datatime parameters in
combination with multi-value parameters when running them in report manager.
The error happens with CTP September. It is fixed in the final RTM release
of SQL Server 2005.
You should basically just take again a backup of your RS 2000 production
server, and then run the upgrade with the SQL Server 2005 RTM release once
it is available.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"clutch" <clutch@.discussions.microsoft.com> wrote in message
news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> have
> been testing some of the reports. We are finding reports that work just
> find
> on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> having any issues? I will try to explain one of the scenarios in which we
> have encountered issues:
> Ok. The report has two date dropdowns and three other string dropdowns.
> The
> dates are defaulted but the others are not. One of the three other
> dropdowns
> are greyed out until the other two are selected first. The problem is when
> we
> select either of the first two dropdowns, it displays an error page
> stating
> "Value cannot be null. Parameter name: value ". The 2000 version works
> correctly.
> Any help is appreciated!|||Thank you Robert!
"Robert Bruckner [MSFT]" wrote:
> It sounds like you run into a known issue with datatime parameters in
> combination with multi-value parameters when running them in report manager.
> The error happens with CTP September. It is fixed in the final RTM release
> of SQL Server 2005.
> You should basically just take again a backup of your RS 2000 production
> server, and then run the upgrade with the SQL Server 2005 RTM release once
> it is available.
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "clutch" <clutch@.discussions.microsoft.com> wrote in message
> news:0A495BC3-1FAE-403B-BF93-156B89C8913F@.microsoft.com...
> > We have completed the Reporting Service's 2005 upgrade (sept ctp) and
> > have
> > been testing some of the reports. We are finding reports that work just
> > find
> > on 2000 (our prod. box) are not working properly in 2005. Is anyone else
> > having any issues? I will try to explain one of the scenarios in which we
> > have encountered issues:
> >
> > Ok. The report has two date dropdowns and three other string dropdowns.
> > The
> > dates are defaulted but the others are not. One of the three other
> > dropdowns
> > are greyed out until the other two are selected first. The problem is when
> > we
> > select either of the first two dropdowns, it displays an error page
> > stating
> > "Value cannot be null. Parameter name: value ". The 2000 version works
> > correctly.
> >
> > Any help is appreciated!
>
>

Reporting Services 2005 requires which SQL Server version?

Very quick question - as our customers have mission critical databases and
will not allow us to upgrade right after Yukon is released, can Reporting
Services 2005 use SQL Server 2000 to hold it's databases? If so then I can
upgrade the non-critical report servers and leave the databases alone for
the moment.
Thanks in advance,
James SnapeJames Snape wrote:
> Very quick question - as our customers have mission critical
databases and
> will not allow us to upgrade right after Yukon is released, can
Reporting
> Services 2005 use SQL Server 2000 to hold it's databases? If so then
I can
> upgrade the non-critical report servers and leave the databases alone
for
> the moment.
> Thanks in advance,
> James Snape
I presume Reporting Services will allow databases to be in SQLServer
2000 because thinking real time most of the operational data will be in
SS 2000 when Yukon is released.
However, The Microsoft guys are the right people to answer this
Question
Anand Sagar|||My understanding is that RS 2005 can use SQL Server 2000 for its databases.
Obviously reporting off of other databases is no problem. My understanding
is also that you will require the SQL Server 2005 license but that the DB
can stay as 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"James Snape" <jim_snape.at.hotmail@.online.nospam> wrote in message
news:%23rJb1d5VFHA.2516@.TK2MSFTNGP10.phx.gbl...
> Very quick question - as our customers have mission critical databases and
> will not allow us to upgrade right after Yukon is released, can Reporting
> Services 2005 use SQL Server 2000 to hold it's databases? If so then I can
> upgrade the non-critical report servers and leave the databases alone for
> the moment.
> Thanks in advance,
> James Snape
>

Reporting Services 2005 beta on SQL Server 2000

We would like to upgrade to Reporting Services to 2005 as soon as it is
released this fall. However, we don't plan to go to SQL Server 2005 for at
least another year. I'm a bit worried about this configuration (RS 2005 on
SQL 2000). Does anyone have any experience running RS 2005 beta on SQL 2000
and would you recommend this setup?We haven't done this ourselves yet, but our plan is to install SQL Server
2005 and RS 2005 on one server, and set the data source for the reports to
our production data on a different box running SQL Server 2000. We do it
with separate servers now except that SQL 2000 is running on both.
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:289D532F-670A-40E4-A8F6-B89B76B934AB@.microsoft.com...
> We would like to upgrade to Reporting Services to 2005 as soon as it is
> released this fall. However, we don't plan to go to SQL Server 2005 for at
> least another year. I'm a bit worried about this configuration (RS 2005 on
> SQL 2000). Does anyone have any experience running RS 2005 beta on SQL
> 2000
> and would you recommend this setup?

Reporting Services 2000, VS2005 and SQL Server 2000

I am running MS SQL 2000 and VS .Net 2005.

Is it possible to run Microsoft Reporting Services 2000 with VS2005 or am I required to upgrade the SQL server and reporting services to 2005 just to produce a few WEB reports ? This would be too costly both in money and time.

I have just finished developing a solution using the version of Crystal Reports which is built into VS 2005. However I now believe that I require costly licenses to deploy the solution on the live WEB server. Can anyone confirm this assumption (in simple terms).

There really does to be a lack of a descent, reasonable cost, solution for generating WEB reports against an MS SQL 2000 database whilst using the VS 2005 development environment. Maybe I am wrong ?

Any suggestions would be appreciated.

Cheers

George

Please help ...

In simple terms, I have VS2005 and am limited to MSSQL 2000 and want to generate some WEB reports. Can I use Reporting Services 2000 services to do this ?

Upgrading to SQL 2005 is NOT an option and I have a large WEB project built using VS2005 (VB).

This now all seems to be so difficult. Any help would be appreciated.

Cheers

George

Reporting Service Install Error 1603

All,
We recently tried to upgrade to the release version of Reporting Services
from Rossetta, unfortunatly the upgrade failed halfway through, and no matter
what i try i cannot get past the point where error 1603 is reported.
I've even tried to uninstall and it says that Reporting services is not
installed, This is on a QA server so I would like to avoid a total rebuild,
If possible.
I've tried all the MS Knowledge base work arounds but still it doesnt work.
I have attached the tail end of the RSMSIO.LOG that show the error
MSI (c) (2C:30): Doing action: PrepareServices
Action start 08:21:40: PrepareServices.
MSI (c) (2C:30): Creating MSIHANDLE (274) of type 790542 for thread 3632
<Func Name='RedirectorCAX'>
Function=PrepareServices
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: PrepareServices
<Func Name='PrepareServices'>
<Func Name='GetServiceAccountProperty'>
<EndFunc Name='GetServiceAccountProperty' Return='T' GetLastError='203'>
<Func Name='SetServiceAccountDialog'>
<EndFunc Name='SetServiceAccountDialog' Return='T' GetLastError='203'>
<EndFunc Name='PrepareServices' Return='0' GetLastError='203'>
<EndFunc Name='RedirectorCAX' Return='0' GetLastError='203'>
DEBUG: Error 2769: Custom Action PrepareServices did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2769. The
arguments are: PrepareServices, 1,
Action ended 08:21:41: PrepareServices. Return value 1.
MSI (c) (2C:30): Doing action: WizardFirst
Action start 08:21:41: WizardFirst.
MSI (c) (2C:30): Creating MSIHANDLE (328) of type 790542 for thread 3632
<Func Name='RedirectorCAX'>
Function=WizardFirst
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: WizardFirst
<Func Name='WizardFirst'>
Action start 08:21:41: WelcomeDlg.
Action 08:21:41: WelcomeDlg. Dialog created
Action start 08:21:42: WizardNext.
Action ended 08:21:47: WizardNext. Return value 1.
Info 2898.DlgTextStyleB, Tahoma, 0
Info 2898.DlgTitleStyleB, Tahoma, 0
Info 2898.FixedStyle, Courier, 0
Action 08:21:47: RegisterUserDlg. Dialog created
Action start 08:21:48: WizardNext.
Action ended 08:21:48: WizardNext. Return value 1.
Action 08:21:48: UpgradeVersionDialog. Dialog created
Action start 08:21:49: SetUpgradeSettingsUIVersion.
Action ended 08:21:50: SetUpgradeSettingsUIVersion. Return value 3.
DEBUG: Error 2896: Executing action SetUpgradeSettingsUIVersion failed.
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2896. The
arguments are: SetUpgradeSettingsUIVersion, ,
Action ended 08:21:50: WelcomeDlg. Return value 3.
<EndFunc Name='WizardFirst' Return='1603' GetLastError='203'>
Gathering darwin properties for failure handling.
<Func Name='DisplayErrorDialog'>
Thankyou in advance for any and all help offered.Hi maybe could you have a look at the following article and check if you
have taken all the required steps.
836064 How to upgrade from Reporting Services Beta 2 to Reporting Services
and
http://support.microsoft.com/?id=836064
Cédric
"Jason Lees" <Jason Lees@.discussions.microsoft.com> wrote in message
news:945180A2-5DEC-4275-998D-23527B53B3FD@.microsoft.com...
> All,
> We recently tried to upgrade to the release version of Reporting Services
> from Rossetta, unfortunatly the upgrade failed halfway through, and no
> matter
> what i try i cannot get past the point where error 1603 is reported.
> I've even tried to uninstall and it says that Reporting services is not
> installed, This is on a QA server so I would like to avoid a total
> rebuild,
> If possible.
> I've tried all the MS Knowledge base work arounds but still it doesnt
> work.
> I have attached the tail end of the RSMSIO.LOG that show the error
> MSI (c) (2C:30): Doing action: PrepareServices
> Action start 08:21:40: PrepareServices.
> MSI (c) (2C:30): Creating MSIHANDLE (274) of type 790542 for thread 3632
> <Func Name='RedirectorCAX'>
> Function=PrepareServices
> <Func Name='SetCAContext'>
> <EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
> Doing Action: PrepareServices
> <Func Name='PrepareServices'>
> <Func Name='GetServiceAccountProperty'>
> <EndFunc Name='GetServiceAccountProperty' Return='T' GetLastError='203'>
> <Func Name='SetServiceAccountDialog'>
> <EndFunc Name='SetServiceAccountDialog' Return='T' GetLastError='203'>
> <EndFunc Name='PrepareServices' Return='0' GetLastError='203'>
> <EndFunc Name='RedirectorCAX' Return='0' GetLastError='203'>
> DEBUG: Error 2769: Custom Action PrepareServices did not close 1
> MSIHANDLEs.
> The installer has encountered an unexpected error installing this package.
> This may indicate a problem with this package. The error code is 2769. The
> arguments are: PrepareServices, 1,
> Action ended 08:21:41: PrepareServices. Return value 1.
> MSI (c) (2C:30): Doing action: WizardFirst
> Action start 08:21:41: WizardFirst.
> MSI (c) (2C:30): Creating MSIHANDLE (328) of type 790542 for thread 3632
> <Func Name='RedirectorCAX'>
> Function=WizardFirst
> <Func Name='SetCAContext'>
> <EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
> Doing Action: WizardFirst
> <Func Name='WizardFirst'>
> Action start 08:21:41: WelcomeDlg.
> Action 08:21:41: WelcomeDlg. Dialog created
> Action start 08:21:42: WizardNext.
> Action ended 08:21:47: WizardNext. Return value 1.
> Info 2898.DlgTextStyleB, Tahoma, 0
> Info 2898.DlgTitleStyleB, Tahoma, 0
> Info 2898.FixedStyle, Courier, 0
> Action 08:21:47: RegisterUserDlg. Dialog created
> Action start 08:21:48: WizardNext.
> Action ended 08:21:48: WizardNext. Return value 1.
> Action 08:21:48: UpgradeVersionDialog. Dialog created
> Action start 08:21:49: SetUpgradeSettingsUIVersion.
> Action ended 08:21:50: SetUpgradeSettingsUIVersion. Return value 3.
> DEBUG: Error 2896: Executing action SetUpgradeSettingsUIVersion failed.
> The installer has encountered an unexpected error installing this package.
> This may indicate a problem with this package. The error code is 2896. The
> arguments are: SetUpgradeSettingsUIVersion, ,
> Action ended 08:21:50: WelcomeDlg. Return value 3.
> <EndFunc Name='WizardFirst' Return='1603' GetLastError='203'>
> Gathering darwin properties for failure handling.
> <Func Name='DisplayErrorDialog'>
> Thankyou in advance for any and all help offered.
>