Re: SKUUPGRADE - Stand ard to Developer?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks Ekrem, that did the trick. You've just saved me £££££ or a whole load
of time and hassle while I re-installed.

Regs,

felix

"Ekrem Önsoy" wrote:

Hello Firestarter,

An upgrade path from SQL Server 2005 Standard Edition to Developer Edition
is an available one.

However, I see that there is a mistake in your command. In the INSTANCENAME,
you are supposed to type only name of the instance which is going to be
upgraded. In your case, it should have been "SQL2K5". In this case, you are
not supposed to add the computer name in front of the instance name.

For example:
D:\SQL Server x86\Servers>setup.exe ADDLOCAL=SQL_Engine
INSTANCENAME=SQL2k5 UPGRADE=SQL_Engine SKUUPGRADE=1 /qb

This would work I believe.

--
Ekrem Önsoy



"Firestarter" <Firestarter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2F4833E8-C896-45CC-8309-02693F601830@xxxxxxxxxxxxxxxx
Hi,
I have have discovered that we standard edition of SQL installed here,
which
should have been Developer Edtions. I read that running setup with the
SKUUPGRADE=1 parameter would allow me change the edition with out a full
re-install.
So I ran this command:
D:\SQL Server x86\Servers>setup.exe ADDLOCAL=SQL_Engine
INSTANCENAME=WXP-14531\S
QL2k5 UPGRADE=SQL_Engine SKUUPGRADE=1 /qb
The setup process ran for a while, and then came back and said :
Cannot find a product with instance name WXP-14531\SQL2k5 for upgrade.



Error Code: 28011
MSI (s) (A4!EC) [11:48:17:546]: Product: Microsoft SQL Server 2005 --
Error
28011. SQL Server Setup cannot perform the upgrade because the component
is
not installed on the computer. To proceed, verify that the component to be
upgraded is currently installed, and that the component to be upgraded is
specified in the ADDLOCAL property. For more information, see Running
Setup
from the Command Prompt in SQL Server Books Online.

Error 28011. SQL Server Setup cannot perform the upgrade because the
component is not installed on the computer. To proceed, verify that the
component to be upgraded is currently installed, and that the component to
be
upgraded is specified in the ADDLOCAL property. For more information, see
Running Setup from the Command Prompt in SQL Server Books Online.

Baiscally, saying I havent got an edition on it that can be upgraded. Am I
trying something that cant be done?

Thanks for any help.



.

Relevant Pages

  • Re: Sharepoint Upgrade to SQL Server Halts at Setup is Preparing to Copy Files
    ... associated SQL Agents/dependant services and then start the upgrade or 2) ... Once the other instances are stopped see if the setup continues.. ... > We already have SQL Server installed on our server prior to this upgrade, ...
    (microsoft.public.windows.server.sbs)
  • Re: How to Install Tools on Other Nodes in a Cluster
    ... I tried that, and it said that I had to use Add/Remove Programs to change the setup, and that's when the problems started. ... When it was originally set up, the tools were only installed on the active node, which I understand is the normal way the installation works. ... To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, ... For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. ...
    (microsoft.public.sqlserver.server)
  • Re: tools not installed but setup thinks they are
    ... Reason: Your upgrade is blocked. ... Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books ... and selected "install to local hard drive" for everything, ...
    (microsoft.public.sqlserver.setup)
  • Re: Upgrading MSDE 2000 to SQL 2000 Standered
    ... We could do this by simply running the SQL Server standard edtion setup ... To upgrade a SQL Server 2000 installation to a different edition of SQL ...
    (microsoft.public.sqlserver.msde)
  • Re: Connecting remotely through VPN
    ... Reason: Your upgrade is blocked. ... Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books ... information about edition upgrades, see the Version and Edition Upgrades ... I think that your SQL Browser Service did not work well. ...
    (microsoft.public.sqlserver.connect)