|
|
Up |
  |
Author: MoffitarMoffitar Date: Sep 3, 2008 09:38
Hi All,
I have a relatively simple question. I have a Windows 2003 R2/SP2 (v.
4035) Server that is running SQL Server 2005 Reporting Services,
Standard Edition. The developers require it to be upgraded to the
Enterprise version because they require specific functionality (the
"unlimited drilldown" feature) that the Standard edition does not
have.
This is to be an in-place "edition" upgrade. I googled the subject
and determined all I would need to do is run the setup wizard and it
would simply unlock the Enterprise functionality. I noted I would
need to run the wizard using the SKUUPGRADE=1 command line option
(bonus tip: this tag is case-sensitive). However, upon running setup,
it apparently didn't detect that I have SSRS installed, because it
only offered to install/upgrade the Client Tools, SSMS, and
Connectivity components.
I cannot continue with the wizard unless I pick one of the above.
there is no option to upgrade SSRS.
Maybe somebody's seen this before?
|
| Show full article (1.78Kb) |
| 5 Comments |
|
  |
Author: Aaron Bertrand [SQL Server MVP]Aaron Bertrand [SQL Server MVP] Date: Sep 3, 2008 10:56
> Hi All,
> I have a relatively simple question. I have a Windows 2003 R2/SP2 (v.
> 4035) Server that is running SQL Server 2005 Reporting Services,
> Standard Edition. The developers require it to be...
|
| Show full article (2.41Kb) |
| no comments |
|
  |
Author: Ekrem ÖnsoyEkrem Önsoy Date: Sep 3, 2008 11:18
You did not show us the command you used for command prompt installation,
however did you try something like the following?
start /wait setup.exe /qn INSTANCENAME= UPGRADE=RS_Server
SKUUPGRADE=1
That "Evaluation copy: 0 days left" is a remarkable message. Are you sure
your SQL Server Instance isn't an Evaluation Edition? Can you check it using
"SELECT SERVERPROPERTY('edition')" command? Because an expired evaluation
edition instance can not be upgraded, in a situation like this, you need to
reinstall it from scratch. However I remember this rule is for Database
Instance. I'm not sure if this is also the same for the other services like
Reporting Service, but I guess it must be the same... Just a note.
--
Ekrem Önsoy
"Moffitar" gmail.com> wrote in message
news:bc25aa4f-d14d-4f0f-8391-d47fb61d44c2@l33g2000pri.googlegroups.com...
> Hi All,
> I have a relatively simple question. I have a Windows 2003 R2/SP2...
|
| Show full article (2.76Kb) |
| no comments |
|
  |
Author: MoffitarMoffitar Date: Sep 3, 2008 11:46
Yes, I have read both of these KB articles. I am holding on to hope
that I won't have to rip-and-replace. Although it is a test server,
there would be a lot of customization to repeat.
Thanks Aaron.
On Sep 3, 9:56 am, "Aaron Bertrand [SQL Server MVP]"
wrote:
|
| Show full article (2.84Kb) |
| no comments |
|
  |
Author: MoffitarMoffitar Date: Sep 3, 2008 11:56
Thanks Ekram.
I don't remember the exact command parameters I used, but I am certain
I tried your example below. When installing in "quiet" mode, the
dialog simply disappeared and an event appeared in the event log
stating the installation was successful. However, I determined that
nothing had been upgraded, so it was a bogus message.
Removing the /qn tag, I saw that even though I specified RS_Server for
upgrade, it still did not detect it.
I am wondering if there is merit in this theory:
1. My server is running ONLY the SSRS services.
2. SSMS is not installed.
3. SSRS is up and working, but the setup wizard is not detecting it.
4. Since the setup wizard is offering to install SSMS and other
"shared" components, could this be a prerequisite for upgrading?
Maybe it is looking for a certain library or resource that is only
available when SSMS or one of the other components is installed.
5. There is no constraint in my installing extra components/features.
The person who came before me assumed we didn't need any of the other
stuff so left it out.
|
| Show full article (4.07Kb) |
| no comments |
|
  |
Author: Ekrem ÖnsoyEkrem Önsoy Date: Sep 5, 2008 06:42
I should set up a test machine and try to reproduce this problem. However,
there is no any available test machine currently =(
I'll try it out as soon as I find an available test machine on my test
server.
--
Ekrem Önsoy
"Moffitar" gmail.com> wrote in message
news:fb6b8d0d-bcce-4c55-8bb2-baae1ce25ac9@s20g2000prd.googlegroups.com...
Thanks Ekram.
I don't remember the exact command parameters I used, but I am certain
I tried your example below. When installing in "quiet" mode, the
dialog simply disappeared and an event appeared in the event log
stating the installation was successful. However, I determined that
nothing had been upgraded, so it was a bogus message.
Removing the /qn tag, I saw that even though I specified RS_Server for
upgrade, it still did not detect it.
I am wondering if there is merit in this theory:
|
| Show full article (4.42Kb) |
| no comments |
|
RELATED THREADS |
  |
|
|
|